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