The Emory Libraries implemented a second-generation preservation infrastructure in 2019 utilizing Hyrax 3, Fedora 4 and AWS, following a requirements gathering phase that included developing a preservation policy and a review of preservation community best practices. This presentation describes our solution design including locally-defined entities such as preservation workflows and events and FileSet expansion to support derivative files. We will also address implementation lessons learned while leveraging existing Samvera functionality and building new features to bridge gaps between existing framework components. The 'Related URL' below links to a video recording of the session. The video has closed captioning. and A presentation given at Samvera Connect 2020 On-line described thus
"what are we going to do about the cloud?" If only we had some kind of animal, recently retrofitted with Wings, that could live up there natively. Fear not, Hyraxes do that. This presentation tackles the what, why, and how of cloud native Samvera. What is the community doing and what are solution bundles supporting? Why should you be interested? Why should you contribute? How can you (yes, i'm looking at you developers, operations folks, repository managers, bosses) benefit? How can your repository make its home among the clouds? The 'Related URL' below links to a video recording of the session. The video has closed captioning., I know what you're asking, and A presentation given at Samvera Connect 2020 On-line described thus
This talk will outline the Surfliner code base, describe the GitLab monolithic source repository, and discuss the reasons behind choosing this model of source control management. It will include background on the systems and workflows used by the UC San Diego and UC Santa Barbara teams that make managing and working productively with a single repository feasible, in addition to a psychomachia-style discussion of the advantages and trade-offs of this approach. The 'Related URL' below links to a video recording of the session. The video has closed captioning. and A presentation given at Samvera Connect 2020 On-line described thus
A presentation given at Samvera Connect 2020 On-line described thus and After trying to navigate deployment, configuration, performance, and scaling issues of several different image servers and support infrastructure (Cantaloupe, Aware, Riiif, nginx, and SquidCache, to name a few), we decided to see if we could build something less general/configurable but far more suited to our use case and runtime environment. serverless-iiif started out as a bare bones, proof-of-concept demonstration of how a scalable, high-performance IIIF image server could be implemented in a small, inexpensive AWS Lambda function. Just over a year later, the project serves as the basis for high-volume IIIF services running in production at Northwestern University, Princeton University, the University of Notre Dame, and the Royal Pavilion & Museums, Brighton & Hove. This presentation will cover the project from its beginnings (as a small demo repository carved out of Northwestern's cloud repository infrastructure), through a number of forks, merges, performance enhancements, deployment improvements, and into production. We will also include performance benchmarks, current production stats, and some thoughts on future work. The 'Related URL' below links to a video recording of the session. The video has closed captioning.
Keyword:
Cloud services, Connect 2020, International Image Interoperability Framework (IIIF), and Samvera
Subject:
Samvera Community
Creator:
Silverton, Edward, Klein, Michael B, Hartzler, Jonathan, and Pendragon, Trey
Contributor:
Northwestern University Libraries, University of Notre Dame, Mnemoscene, and Princeton University Library
A presentation given at Samvera Connect 2020 On-line (originally titled 'Cloud storage service uploads for a Valkyrie repository') and described thus and This presentation aims to outline and discuss attempts throughout 2019 and 2020 to integrate an early pre-release of the BrowseEverything 2.0 component for supporting Google Drive file uploads into a Samvera repository. While this shall be restricted in scope for cases which were specific to the Princeton University Library and a Valkyrie-based repository Figgy, the hope is to encourage discussions regarding obstacles which were encountered and to aim to generalize the solutions which were discovered in this integration. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording.
Keyword:
Cloud services, Architecture, Samvera, Valkyrie, and Connect 2020
A presentation at Hydra Connect 2016 described thus and Join us for a technical overview of the Hydra-in-a-Box hosted platform where we will detail how we're using Amazon cloud services and how we've evolved Hydra and Fedora to use them effectively. We will discuss how we've architected the traditional Hydra stack to be highly available, scalable, auto-deployed, and cloud friendly. This is an audio recording of the session.
Keyword:
Hydra, Cloud services, Hydra in a Box, and Connect 2016
Northwestern University Libraries is currently running Samvera applications in production. Three of these are developed, maintained, and managed by the Repository & Digital Curation workgroup, * Arch, an Institutional Repository, based on Hyrax 2.4.1 * AVR, Northwestern's audiovisual repository, based on Avalon 6.3 * DONUT, the staff-facing ingest interface for the digital object repository, based on Hyrax 2.4.1 In developing and deploying these applications, we have encountered (and mostly overcome) numerous stumbling blocks relating to performance, scalability, customization, and assumptions about the deployment environment and infrastructure on which the apps will run. While we have found it possible to shoehorn the Samvera stack (as it exists today) into our Amazon Web Services cloud-based deployment environment, we have also started to investigate the rewards and compromises involved in taking a cloud-first approach to our next generation of tools. We have identified several basic tenets for this approach so far, * If AWS offers a native Software-as-a-Service (SaaS) solution for a particular problem, use it (e.g., choose ElasticSearch/Cloud Search over Solr) * Avoid virtual server instances that run 24x7 waiting for requests/work * Do not assume there is a local filesystem to work with * Optimize startup time so that units of work can be spawned and killed as needed * Constantly assess and reassess every unit of work for scalability, repeatability, and idempotence * Keep data portable and code adaptable, but don't over-stress about vendor lock-in In this presentation, members of the Repository Development & Administration Team will present on lessons learned from 7 years of working with Samvera, Avalon, and Hyrax, what the future holds for our next round of in-house development, and the opportunities & compromises our cloud-first approach creates regarding our use of and contributions to the larger Samvera community., and A presentation at Samvera Virtual Connect 2019 described thus
Keyword:
Cloud services, Samvera, and Virtual Connect 2019
Subject:
Samvera Community
Creator:
Klein, Michael B
Contributor:
Quinn, Brendan, Schober, David, Arling, Adam, Shaw, Karen, and Northwestern University
Over the past two years, Northwestern University Libraries has moved its repository infrastructure and applications to Amazon Web Services. Our initial solution, presented at Samvera Connect 2017, involved AWS CloudFormation, several different deployment platforms, and a lot of manual intervention. In our second phase, we have adopted a fully automated build/configure/deploy system to stand up Fedora, Solr, PostgreSQL, Redis, a Cantaloupe IIIF server, an Avalon Media System instance, a secure CloudFront streaming media distribution, and two Hyrax applications using Terraform, Docker, AWS Elastic Beanstalk, and a whole bunch of homegrown tools and hacks. This presentation will provide an overview of our current system, and hopefully jumpstart some discussions of how these tools can be adopted, standardized, and reused among other members of the Samvera community. A video recording of this session is available at the 'Related URL' below., A presentation given at Samvera Connect 2018, originally titled "My Life in Ops, and Docker, Terraform, AWS, and Learning As We Go", described thus
//github.com/upenn-libraries/guardian) * A report on the reusability of these components to quickly develop Ruby-based integrations with Amazon Glacier in other applications * Challenges faced while integrating asynchronous storage with our Samvera repository * Considerations for developing a disaster recovery plan dealing with large-scale data loss and recovery A video recording of this session is available at the 'Related URL' below., A presentation given at Samvera Connect 2018 described thus, * Fundamental concepts of managing repository objects as Glacier archives * Best practices followed at Penn Libraries for efficient, affordable transfer and retrieval interactions with Glacier * A dive into the stronghold gem, developed at Penn Libraries, which provides a simple interface for interacting with Glacier (https, //github.com/upenn-libraries/stronghold) * Demonstration of Penn's workflow for running synchronous transfer of objects to Glacier using guardian, a set of Ruby scripts serving as the orchestration layer (https, and This session details work done at the University of Pennsylvania to incorporate Amazon Glacier as a third-copy backup storage location for objects in our repository using a series of components that were developed as generalized tools that can be integrated into any Ruby-based application to manage object copies in Glacier. This session will cover
Keyword:
Cloud services, Repository, Connect 2018, and Samvera
Subject:
Samvera Community
Creator:
Lynch, Katherine
Contributor:
University of Utah and University of Pennsylvania Libraries
