//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