A recording of a presentation at Samvera Connect 2018 described thus and Panelists from Duke University, Indiana University, and the University of Michigan will share their experience of developing a Research Data Repository based on Hyrax 2. They will discuss what worked out-of-the-box, what was customized, future directions, lessons learned to date from working together, and contributing back to the Hyrax community. Institutions’ efforts include data migration, accessibility testing, branding, community outreach, curation workflows, and overcoming the challenges associated with large datasets. A video recording of this session is available at the 'Related URL' below.
Keyword:
Hyrax, Research data management, Repository, Connect 2018, and Samvera
Subject:
Samvera Community
Creator:
Freiheit, Fritz, Downey, Moira, Jaffer, Nabeela, Sexton, Will, and Dunn, Jon
A recording of a presentation at Samvera Connect 2018 described thus, prototyping a core component of our new architecture to be horizontally scalable, designing a new architecture for our digital library with a wide ranging set of requirements and users, Stanford University Library has a robust digital library system called the Stanford Digital Repository. This repository holds a little under 500 TB of materials in preservation, and a little less than that for online access, from our cultural heritage digitization efforts and institutional repository outputs. These materials are managed across 90+ codebases serving a variety of functions from self-deposit web applications, to a nearly 10 year old parallel processing framework, to a digital repository assets publication mechanism leading into our Blacklight, Spotlight, and Geoblacklight applications - among other services and needs. At the core of this system is a Fedora 3 store. With Fedora 3 now end-of-lifed, and our system suffering from limited to no horizontal scalability options, we’re revisiting our system and architecture. We are writing it from the start with a goal to have data-forward, distributed microservices and some event-driven processing components. TACO, our new core management API, is the heart of this new architecture, and is currently being developed as a prototype. This talk will walk through the process of analysing our current system via a dataflows analysis, then planning how to create ‘seams’ in our current system to migrate towards our new system in an evolutionary fashion instead of a turn-key migration. A video recording of this session is available at the 'Related URL' below., and seeing where community technologies like Hyrax, Blacklight, and IIIF will connect
Keyword:
Workflow, Architecture, Repository, Connect 2018, and Samvera
Subject:
Samvera Community
Creator:
Frost, Hannah and Harlow, Christina
Contributor:
Stanford University Libraries and University of Utah
//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
This presentation aims to explore the possible integration of Samvera digital object repositories with additional web services using message brokers. There have been cases in which it is necessary to synchronize content updates between repositories and additional library systems such as library catalogs or digital exhibit publishing software. Within this context, developers may benefit by exploring architectural pattern in which a dedicated message broker receives asynchronous notifications of repository content updates, new ingestions, and deletions. In response to having received these messages, the broker may then broadcast these events to other listening library systems. The library systems then may reindex or update their own content accordingly. A conceptual overview of this architectural pattern shall be provided, followed by an overview of an implementation local to the systems within the Princeton University Library (synchronizing content between implementations of Valkyrie and Spotlight using RabbitMQ). The outcome of this presentation would be to identify other Samvera adopters who may also be utilizing message brokers, with the ultimate aim of determining whether or not this approach would be beneficial to a larger number of community members. A video recording of this session is available at the 'Related URL' below. and A presentation given at Samvera Connect 2018 described thus
Keyword:
Repository, Connect 2018, and Samvera
Subject:
Samvera Community
Creator:
Griffin, James
Contributor:
University of Utah and Princeton University Library