A presentation at Samvera Connect 2019, originally titled "Creating a new Carolina Digital Repository, customizations and change", described thus, and In June 2019, the University of North Carolina at Chapel Hill University Libraries Software Development and Repository Services departments launched the new Carolina Digital Repository (CDR) platform, built on Hyrax. The new repository houses scholarly materials in support of UNC’s Open Access policy and supports many existing workflows and use cases such as student papers, OA books, and datasets. In this presentation we will describe existing and new use cases and show how we customized Hyrax to meet those needs. We will also share lessons learned and future plans for the CDR.
Keyword:
Repository, Samvera, Customization, and Connect 2019
Join us for an update on Avalon metadata in Hyrax. The Avalon Media System is an open source system for managing and providing access to collections of digital audio and video. The project is led by the libraries of Indiana University Bloomington and Northwestern University and is funded in part by grants from the Institute of Museum and Library Services and the Andrew W. Mellon Foundation. We are working to incorporate Avalon descriptive, technical, and structural metadata into Hyrax, the open-source repository front end from the Samvera Community, creating an AudiovisualWork that can be added to Hyrax as a gem alongside other work types (like GenericWork and Image). We will share our progress so far, including mappings for bibliographic import functionality and how things look different between Avalon 6 and Avalon in Hyrax. Avalon in Hyrax will also be available as a standalone Hyrax application so we are both letting the Hyrax in and letting the Avalon out! Come see how these two critters are getting along! and A presentation at Samvera Connect 2019 described thus
Keyword:
Hyrax, Metadata, Avalon, Samvera, and Connect 2019
A lightning fast overview of free or cheap, cool and useful Ruby and Rails web sites, blogs, podcasts, videos, and users groups for new and not-so-new Hydra developers. I'll talk fast, but don't worry, I'll post the links on-line before the talk. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
Wings, the project to move Hyrax to Valkyrie, has been underway for most of this year. What does this transition mean for your existing Hyrax application? How should you account for it in your future planning? How can you take advantage of this work today? This presentation will address these questions for a general community audience. and A presentation at Samvera Connect 2019 described thus
A combined slide pack of a number of lightning talks given by Interest and Working Groups at Samvera Connect 2018. A video recording of this session is available at the 'Related URL' below.
Keyword:
Interest and Working Groups, Lightning talk, Connect 2018, and Samvera
Subject:
Samvera Community
Creator:
Hyrax Batch Import-Export Working Group, CONTENTdm Migration Working Group, Core Components Maintenance Working Group, Geopredicates Working Group, and Geospatial Interest Group
Many institutions need to import, export, and migrate data in bulk, and the ability to do this easily should be a fundamental service offered by any repository. For Hyrax, there are a range of home-grown and community solutions focused on specific use cases but there are no easily reusable community solutions. That’s starting to change and we’d like to talk about our specific experience building ‘Bulkrax’ and ‘Zizia’, two bulk import-export engines for Hyrax. This talk will outline the current status of our two projects, covering the design and approach taken, alongside features such as OAI-PMH import, and CSV import and export. We'll also talk about where Bulkrax and Zizia are going in the near future. We’ll show how each can be adopted, configured, and extended to meet local use cases, and how these projects are meeting the requirements set out by 2018’s ‘Batch Import-Export Working Group’. We’ll also discuss how best to move forward as a community around this issue, This will mean developing not only software but also shared community practice for managing the flow of bulk metadata from legacy systems and digitization projects into Samvera repositories., and A presentation at Samvera Connect 2019 described thus
A brief walk through on concerns related to monitoring and alerting a production Hydra stack. An recording of this session is available at the 'Related URL' below. Unfortunately, although it is technically a video, the slides do not show on the recording. and A lightning talk presentation at Hydra Connect 2016, described thus
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
When the Library of Congress was recently attacked, we noticed an important part of our workflow ground to a halt - XML schema validation had failed. We've developed a gem that allows for schema mirroring and offline validation/rspec testing, which we hope might be of use to others. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, 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
The One-to-Many (OtM) Grant, funded by the Mellon Foundation, is working to provide a model for how local repositories, like Hyrax, interact with Distributed Digital Preservation (DDP) services (i.e., Chronopolis, AP Trust, LOCKSS, etc). This presentation will offer an overview of the grant's goals, an update on the specifications under development, and a call to action for implementation. and A presentation at Samvera Connect 2019 described thus
Since 2014, partners from Indiana University Bloomington (IUB) and Indiana University Purdue University Indianapolis (IUPUI) Libraries have been collaboratively developing new Samvera-based software to manage and deliver page turning digital objects. In 2018, conversations with Enterprise Scholarly Systems (ESS), a partnership between IUB Libraries, IUPUI Libraries, and University Information Technology Services (UITS), expanded our project's scope. This presentation will highlight our development efforts, now known as the ESS Images project or ESSI. In the past year, the ESSI team has developed numerous improvements to the Hyrax digital repository software. These improvements include the ability to order, structure, and label pages within an item, replicating features available in the Pages Online service launched in 2017. Additionally, the project has implemented optical character recognition search in a community-accepted way, building upon components of the IMLS-funded Samvera Newspaper Works application. We will also discuss upcoming improvements for our existing image collections. In these collections, images often have wildly different metadata profiles from each other. Our recent work has aimed to incorporate a model for flexible metadata developed by the Samvera Machine-readable Metadata Modeling Specification (M3) Working Group within Hyrax. We will be discussing the output of this work as well. and A presentation at Samvera Connect 2019 described thus
The Boston Public Library has long been a Fedora 3 Commons system and we are heavily invested in that backend. After waiting to see how Fedora 4 Commons develops and with some recent internal debate, our "next gen" repository solution is going in a different direction. This will be a (perhaps) controversial talk as to why and how we came to this conclusion. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
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
As most Hyrax adopters know, Hyrax offers a basic set of metadata properties that it assigns to each new work type. Most adopters will extend that set, to a greater or lesser degree, adding new properties, defining vocabularies and terms lists, and setting other constraints and requirements. Adding new metadata is a complicated process in Hyrax, and there are various ways in which developers have worked to streamline things (eg. scooby snacks, dog biscuits and archetypes). But before we even get to customising a Hyrax application, metadata librarians and developers must collaborate on specifying the metadata requirements. With no community machine-readable approach to defining those requirements, misunderstandings are common, and can be costly. With a machine-readable specification for metadata, metadata librarians could accurately specify requirements and developers could validate and codify those into applications. That’s where the Machine-readable Metadata Modeling Specification (M3) steps in. The specification is the output of the M3 Working Group and is nearing its version 1.0 release. This presentation will provide a walkthrough of the specification, show how to construct and validate a new M3 profile, and illustrate the benefits of M3 for both metadata specialists and developers. and A presentation at Samvera Connect 2019 described thus
A lightning talk presentation at Hydra Connect 2016, described thus and Hydra applications can interact with a number of backing services (Fedora, Solr, Redis, job runners, etc). Using Docker to run these services locally can potentially simplify the development environment and reduce on-boarding time. A video of this session is available at the 'Related URL' below.