A presentation at Samvera Connect 2019 described thus and Although it feels like we just migrated from CONTENTdm to Hydra/Fedora 3, it's time to adjust course back to Hyrax! Oregon Digital's Metadata Team will talk about strategies and challenges with metadata preparation, remediation before migration begins and mapping updates. The Migration Team will talk about the gem we're building, hyrax-migrator, to allow us to migrate over 465,000 assets (files and metadata). We’ll cover the design and implementation of the gem which supports migrating assets both locally (for dev and testing) and remotely (for production, on AWS S3), and share our progress with a batch of about 1000 ‘seed data’ assets, as well as our goals for scaling up in the coming months.
Keyword:
Metadata, Migration, Samvera, and Connect 2019
Subject:
Samvera Community
Creator:
Wick, Ryan, Sato, Linda, Key, Cara, and Ramirez, Gregorio Luis
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
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