A combined slide deck of the short reports from Interest and Working Groups at Hydra Connect 2015. Archivists Interest Group Digital Preservation Interest Group Geospatial Interest Group Hydra GIS Data Modeling Working Group Metadata Working Group Page Turner Interest/Working Group Service Management Interest Group User Experience Interest Group Web Presence Interest Group
This will be a half-day, hands-on workshop covering data modeling primarily in RDF. We hope to bring a diverse group of Hydra community members together to learn, discuss, and build out examples that will inform Hydra community best practices for data modeling. This modeling work will be taught in the context of helping Hydra and Fedora development, metadata, and interoperability efforts. We will discuss how model uses a number of standards, and demo the different ways to represent models. We will compare and contract data modeling with metadata standards/profiles. We will walk through modeling efforts around PCDM and its place in our work and community - this workshop will not focus on PCDM alone (this is not a PCDM or RDF workshop). We want this workshop to bring together, develop and engage a larger corps of data modelers in the Hydrasphere. and A workshop delivered at Hydra Connect 2016, described thus
A presentation given at Connect 2017 described thus and With so many Samvera metadataists managing similar objects and collections, can we get a handle on the metadata we have and what we share with the community? This session will introduce the idea behind the Documentation Project from the Samvera Metadata Interest Group and will consider what we're saying about our objects, how we're expressing it, and how best to move this work forward to provide suitable context for what we do or don't want our MAPS to look like as we document our work within Samvera.
A presentation given at Connect 2017 described thus, it’s not fun to have an ingest fail overnight and spend the morning tracking down why. Programmatically testing and validating digital object metadata prior to ingest helps us avoid these failures. The metadata itself is managed by Git and stored in GitHub, Several years ago UCSB incorporated Git/GitHub and JIRA into our metadata management and batch ingest workflows. Since then we’ve looked at repurposing other development tools to provide lightweight and automated solutions to problems we often face. One is that we rely primarily on batch ingests when adding content to our Samvera repository. As a result it’s especially important for the metadata to be error-free, and this allows us to run automated checks against any changes using Jenkins and some custom libraries we’ve written for validating CSV and MODS metadata. In this session, we will provide an overall of our current ingest preparation workflow and the tools we are using, and will discuss some of the benefits that have come out of this collaborative effort.
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
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 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.
A lightning talk at Samvera Virtual Connect 2018 described thus and Avalon Media System is working towards a release to integrate with Hyrax in support of time-based media formats. This includes creating a Work type to support the needs of audio and video formats and provide an upgrade path for those who have been using Avalon in it’s previous releases as a standalone Samvera product. Join us for a look at the new Audiovisual Work type, specifically how we’re transitioning descriptive metadata from MODS XML to RDF. A video recording of this session is available at the 'Related URL' below.
A lightning talk at Samvera Virtual Connect 2019 described thus and For metadata specialists, creating metadata profiles, system requirements, and accompanying documentation often feels like a game of whack-a-mole. Current practices and technologies also mean comparing your profiles with another institutions’ is an enormous hassle. To address this problem, developers and metadatists came together to create the machine-readable metadata modeling (M3) specification. This presentation will offer some history and use cases for the specification, an update on its current status, and where to learn more.
A lightning talk at Samvera Virtual Connect 2019 described thus and Avalon Media System is upgrading it's UI component for handling structural metadata editing for an audio or visual work. The user can select and organize timespans in an AV work by manually typing bounding times and titles, or by interacting with a visual representation of the waveform. Technologies used are Peak.js and ReactJS.
A presentation given at the London School of Economics and Political Science on 22nd November 2012. The meeting brought together a number of institutions from the UK (and some from Europe more widely) interested in the potential of Hydra. The presentation was one of a number describing the then current use of Hydra in the UK.
The Royal Library was very fast to adapt the emerging web technologies in the mid 1990’s. The web was used as an integrated part of digitization projects, resulting in a number of specially tailored web sites for various types of content, manuscripts, images, literary texts, journal articles, etc. Each project and type of material would typically result in its own data model, metadata format, workflow, and a database/repository that was tightly coupled with the web application. In later years, as the throughput on the digitization production lines has increased, more automated ways of dissemination have been developed. However this has not been able to fundamentally replace the tendency to building silos around different types of content. Being both national and university library, we can expect that in the future accessioned material will largely be born digital. In order to handle this situation, we have decided to start implementing an integrated digital library infrastructure, covering all aspects of digital collection building and management. The assumptions are that some metadata will be shared between all types of digital materials, and that the main steps in a digital object life-cycle will be common for all object types. In my presentation I am going to show how we are building a technical infrastructure in support of this, using building blocks such as Hydra, Fedora Commons, Solr, and Blacklight. I will also be touching on the organizational side of the project, focusing on the challenges to both IT people and collections staff in this process of change., and A presentation to the EOD Conference held at the National Library of Technology, Prague, Czech Republic, 17-18 October 2013. Abstract