A presentation given at the Open Repositories conference in 2015 held in Indianapolis, described thus, Fedora, Hydra, Solr, and Blacklight. Called “Ichabod,” this tool has allowed us to ingest, normalize, and enrich metadata from diverse systems of record and make it consumable by our main discovery tool, which is powered by the Ex-Libris product Primo. We developed Ichabod using the Agile methodology and involving developers from three distinct NYU Libraries groups. The software will lay the groundwork for future innovation in the areas of metadata management and discovery for repository content. The relationships we established have already made it possible for a similar collaboration arrangement on two other projects, with more to come in the future., and From DSpace to Drupal, NYU has a variety of systems to ingest and display curated digital content. To make this content discoverable centrally, we developed a tool for metadata ingest, transformation, and discovery based on a popular open-source software stack
Keyword:
Metadata, Workflow, Architecture, Hydra, Open Repositories 2015, Blacklight, Digital collections, Fedora, and Solr
Subject:
Hydra Project
Creator:
Pechekhonova, Ekaterina, Harper, Corey, Kassel, Carol, and Lovins, Daniel
Using Git and GitHub for managing metadata (no new data models, we promise)This session is proposed as a two-part workshop, A workshop given at Samvera Connect 2017 described thus, and The first will cover a modified version of the ‘Version Control with Git’ Software Carpentry lesson, tailored for a non-developer audience, with more focus on metadata. This is typically taught as a half-day (3 hour) workshop.The second part will focus on the use of Git and GitHub in the context of the metadata workflow. We will present examples and strategies, taken from recent work by UC Santa Barbara and UC San Diego, of version control, pull requests, and automated hooks and integrations as they relate to moving metadata through a workflow and into our repositories. In addition to these demonstrations, we hope to spend a good percentage of the time available in discussion with other interested institutions and how we might leverage our collective experience to make getting our metadata into our repositories easier, more consistent, and maybe even more fun!
Keyword:
Workshop, Metadata, Connect 2017, and Samvera
Subject:
Samvera Community
Creator:
Rissmeyer, Chrissy, Critchlow, Matthew, and Dunn, Alex
Contributor:
University of California San Diego Library and University of California Santa Barbara Library
Using Hydra to manage and present cultural heritage resources raises a set of interesting challenges that are beyond the scope of the traditional institutional repository. These include more complex data models, elaborate and varied workflows, richer descriptive metadata, support for more and varied controlled vocabularies, the requirement to manage larger objects comprised of larger files and multiple derivatives, support for IIIF, and a desire for richer viewing environments in general. In this presentation we will discuss these challenges and highlight examples and implementations that have gone ‘beyond the repository’. An audio recording of the session is available for download below. and A presentation at Hydra Connect 2016 described thus
Keyword:
International Image Interoperability Framework (IIIF), Connect 2016, Workflow, Hydra, and Metadata
Subject:
Hydra Project
Creator:
Allinson, Julie and Stroop, Jon
Contributor:
Princeton University Library and University of York
Between 2018 and 2019, Jisc funded an effort to refresh the SWORD repository deposit protocol, with modern repository use cases in mind, especially around data repositories. As a result we produced a draft specification, extensively reviewed by a large number of the repositories community, including those from the Samvera and Fedora communities. In 2019, NII provided funding to produce a reference implementation, and we have been working to prove that the specification is implementable and viable. That work concluded in July 2020 with the release of a client library and a server library in Python. Now the SWORDv3 team is looking outward to the rest of the repositories community, looking to engage them in development for their platforms, and to enable novel integrations. This presentation will introduce the spec for those that are not familiar, and describe the technical and community-building work that is ongoing, and call for engagement by the Samvera technical community in working with SWORDv3. The YouTube 'Related URL' below links to a recording of the presentation with closed captioning. and A presentation at Samvera Connect 2020 On-line described thus
Keyword:
Samvera, SWORD, Protocol, Connect 2020, and Metadata
The Emory Libraries implemented a second-generation preservation infrastructure in 2019 utilizing Hyrax 3, Fedora 4 and AWS, following a requirements gathering phase that included developing a preservation policy and a review of preservation community best practices. This presentation describes our solution design including locally-defined entities such as preservation workflows and events and FileSet expansion to support derivative files. We will also address implementation lessons learned while leveraging existing Samvera functionality and building new features to bridge gaps between existing framework components. The 'Related URL' below links to a video recording of the session. The video has closed captioning. and A presentation given at Samvera Connect 2020 On-line described thus
Heavily inspired by QA, "Authoritex" is a Hex package for querying any controlled vocabulary or set of authority terms that NUL developed for use within our Elixir ecosystem. We'll go through quick overview of Authoritex and how it fits into our repository ingest application "Meadow" and our broader strategy for handling controlled terms and authorities. The 'Related URL' below links to a video recording of the session. The video has closed captioning. and A lightning talk (seven minute) presentation given at Samvera Connect 2020 On-line described thus
A lightning talk (seven minute) presentation given at Samvera Connect 2020 On-line described thus and Update on recent and coming work for the Bulkrax gem. The 'Related URL' below links to a video recording of the session. The video has closed captioning.
Keyword:
Metadata, Connect 2020, Samvera, and Import/export
In May 2018, UNC Libraries purchased a report from 1Science which listed 47,000 articles authored by UNC researchers. Although the vendor characterized the report as an out-of-the-box tool designed to fill an institutional repository, we found that it would take significant work to make it usable for UNC’s Hyrax-based institutional repository, the Carolina Digital Repository (CDR). In this presentation, we will discuss the issues that we identified, including scripting errors, inconsistent metadata and rights concerns. We will describe the plans and processes to fix these issues and to adapt the metadata for our repository. Additionally, we will address best practices for uploads and future plans. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording. and A lightning talk (seven minute) presentation given at Samvera Connect 2020 On-line described thus
Keyword:
Metadata, Lightning talk, Connect 2020, and Samvera
A presentation given at Samvera Connect 2020 On-line described thus and Figgy is Princeton University Library’s staff-facing repository management application. This presentation will share screenshots, user stories, and technical overviews of all the forms, magic buttons, storage integrations, drag-and-drop targets, rake tasks, and directory watchers that Figgy provides to support the different workflows our users have for ingesting content. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording.
Keyword:
Metadata, Workflow, Connect 2020, Migration, Archives, Samvera, and Digitization
one size would not fit all for our campus archives, library, and museum, and community needs above all. In this presentation, team members will talk about the past two years of experimentation, development, and conversation around how to connect our community to our cultural heritage collections through multiple integrations, both human and technological. At a high-level, we’ll discuss our technical architecture that uses legacy applications like ArchivesSpace, an aging Fedora repository, and a decades-old museum database together with the IIIF framework and open-source GatsbyJS. And perhaps more importantly, we’ll outline the cross-departmental team structure that has developers talking to museum curators, library cataloguers, archivists, and everyone in between. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording., The University of Notre Dame has taken a modular approach to building a new digital collections platform-integrating existing applications and connecting the people that manage and use them across the library, archives, and art museum. We began with two assumptions, and A presentation given at Samvera Connect 2020 On-line described thus
Keyword:
Architecture, Samvera, Workflow, Connect 2020, Metadata, and Digital collections
A presentation given at Samvera Connect 2020 On-line described thus and Princeton University Library’s digital projects and initiatives were seriously disrupted by COVID-19. Digitization of materials for projects and forthcoming exhibitions came to an unexpected halt at the same time as patrons and staff were separated from physical objects and library spaces. Necessity, however, provided an opportunity to reassess digital projects and how staff members interact with and contribute to our repository (Figgy). We focused on the creation of workflows and documentation for new contributors who would be working in the repository, helping them enhance existing digital objects with OCR, item level organization, structural metadata, page labeling, and IIIF display attributes. We describe how we were able to use Figgy and unexpectedly-available staff time to make more effective research tools and provide a better user experience for patrons and staff working with our digital collections. Such enhancements add immense value to our collections as well as to our applications, and the work can be done effectively by a wide range of staff from different departments with variable skill sets. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording.
Keyword:
Metadata, Workflow, Connect 2020, Digitization, Samvera, Exhibits, and Vendors
Elixir, Phoenix, React, GraphQL, PostgreSQL, Elasticsearch, Amazon Web Services, Docker and Terraform. This presentation will focus on describing why we chose this path and the decisions and tradeoffs we've made along the way, along with a brief demonstration of our current state. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording., Northwestern University Libraries has been building a "green field" digital repository application since June 2019, code-named "Meadow". Our goal in building Meadow is to provide an internal tool to ingest, modify and publish digital resources to an API that drives our user-facing digital collections frontend. Meadow's development roadmap has focused on complementing NUL's existing production workflows and implementing best practices in digital preservation in a cloud-based environment. Meadow is built with a several languages, tools, and frameworks including, and A presentation given at Samvera Connect 2020 On-line described thus
Keyword:
Architecture, Samvera, Workflow, Connect 2020, Metadata, and Preservation
A set of very brief (3 minute) presentations given at Samvera Connect 2020 On-line updating the Community on the work of some of its Interest and Working Groups. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording.
Keyword:
Interest and Working Groups, Hyrax, Metadata, Connect 2020, Samvera, Controlled vocabulary, Marketing, User experience, and Repository management
Subject:
Samvera Community
Creator:
Egloff, Nora, Goslen, Anna, Awre, Christopher L, Hardesty, Juliet L, Jaffer, Nabeela, and Arling, Adam
Contributor:
Samvera Controlled Vocabulary Decision Tree Working Group, Samvera Metadata Interest Group, Samvera Marketing Working Group, Repository Managers' Interest Group, Hyrax 3.0 Metadata Application Profile Documentation Working Group, and Samvera UI Interest Group
Slides from an on-line workshop given at Samvera Connect 2020 On-line described thus and *Overview of the M3 schema *Requirements and Installation for Allinson Flex *Overview of Allinson Flex usage *Constraints and next steps discussion Allinson Flex brings on the fly user editable M3 metadata schemas to Hyrax and repositories built with similar components. We'll dive deep into what the M3 schema is and how it is structured, how Allinson Flex works today and what our plans for the future bring. Workshop will be divided into 2 parts. Part 1 will be a feature overview and discussion / dive into how M3 schemas are laid out. Part 2 will be a hands on installation and configuration of the Allinson Flex tools and a code dive into certain features.
Keyword:
Workshop, Hyrax, Metadata, Connect 2020, Samvera, and Community
Component Maintenance WG - James Griffin BrowseEverything IG - James Griffin Metadata IG - Anna Goslen Hyrax v3.0 Metadata Application Profile Documentation Review WG - Nora Egloff Repository Management IG - Moira Downey Infrastructure WG - Michael Klein Newspapers IG - Eben English Hyrax Maintenance WG - Tom Johnson Geo Predicates WG - John Huck The video recording of this segment is available at the 'Related URL' below. and Working and Interest Group Updates
Keyword:
Geodata, Newspapers, Screencast, Interest and Working Groups, Virtual Connect 2020, Repository Management, Hyrax, Samvera, and Metadata
Subject:
Samvera Community
Creator:
Egloff, Nora, Klein, Michael B, Goslen, Anna, Johnson, Tom, Griffin, James, Huck, John, Downey, Moira, and English, Eben
A presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus and Avalon Media System requires support for complex structure and modular descriptive metadata management. Use cases and examples will examine options for Avalon in Fedora such as the RDF data model in Fedora 4, static XML datastreams, and external data stores to determine which path best fits structural and descriptive metadata needs for time-based media.
Keyword:
Fedora, Avalon, Hydra, Open Repositories 2015, Metadata, and Resource Description Framework (RDF)
Indiana University Bloomington Libraries is involved in two new projects to digitize and store content and related metadata. Each of these projects presents unique challenges. We want to use the same technology stack for both, however, so we are choosing Fedora as a storage mechanism, with Hydra-based Sufia as a repository front end. We will discuss our decision, show advantages of this Hydra/Fedora framework, and discuss advantages of moving to Fedora 4. We will also contrast this framework with the way we might have approached these projects in the past with previous versions of Fedora and before Sufia or Hydra were options. and A presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus
Keyword:
Fedora, Digital collections, Hydra, Archives, Open Repositories 2015, Sufia, and Metadata
A presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus, provide an update on progress to date, At the University of Alberta Libraries we are currently developing a Digital Asset Management System (‘Hydra North’, built on Hydra and Fedora 4) to bring all of our digital assets into one platform for discovery, access and preservation. The metadata underlying these repositories has been created according to many standards (DC, MODS, EAD, etc.) and varies in level of fullness and overall quality. We find ourselves at a ‘metadata crossroads’ as we attempt to bring this disparate metadata together. We see a solution in a move to RDF and the application of the principles of linked data. In this presentation we will discuss some of the initial questions we asked ourselves as we tried to fully grasp what the move to RDF and linked data would mean for our existing metadata, provide concrete examples of the thought processes and workflows involved in moving from existing non-RDF metadata to RDF, based on the principles of linked data, outline some of the decisions we made along the way, and why, and what the impact has been, and reflect on lessons learned and outline next steps.
Keyword:
Metadata, Resource Description Framework (RDF), Hydra, Open Repositories 2015, and Fedora
At the Digital Collections and Archives (DCA) at Tufts University we have designed, built, and integrated our archival collection management system and repository’s administrative interface to facilitate ingesting archival objects into our Fedora based repository. This 24x7 session briefly explores the assumptions and functional requirements we have used to guide this development work. The DCA’s unique position as an archives that is one of the key stakeholders and users of the Tufts institutional repository has enabled us to meet this integration challenge. The session describes how the integration of our archival collection management system and our repository relies on the ability to flexibly move metadata from one system to another. and A lightning talk given at the Open Repositories conference in 2015 held in Indianapolis described thus
Keyword:
Case study, Digital collections, Hydra, Repository, Archives, Open Repositories 2015, Lightning talk, and Metadata
In the past year, the major groundwork has been laid for repository systems to support ORCID identifiers. DSpace, Hydra, and EPrints all have support for storing and managing ORCIDs. However, we are still in the early stages of ORCID adoption. Only a small fraction of repository content is annotated with ORCIDs, and most end-users have not yet realized any benefit from the features based on ORCID. This panel will bring together representatives of major repository systems to relate the current status of ORCID implementations, discuss plans for future work, and identify shared goals and challenges. The panelists will discuss how ORCID support provides practical benefits both to repository staff and end-users, with a focus on features that exist now or will exist in the next year. and Slides from a panel session given at the Open Repositories conference in 2015 held in Indianapolis described thus
Keyword:
Metadata, DSpace, Hydra, Open Repositories 2015, and ORCID
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
Keyword:
Blacklight, Fedora, Architecture, Hydra, Metadata, and Solr
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.
Keyword:
Fedora, Architecture, Hydra, Repository, Content models, and Metadata
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.
Keyword:
Metadata, Lightning talk, Virtual Connect 2019, Avalon, Samvera, and User experience
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.
Keyword:
Samvera, Virtual Connect 2019, Lightning talk, and Metadata
Subject:
Samvera Community
Creator:
Tillman, Ruth Kitchin and Hutt, Arwen
Contributor:
Penn State University and University of California San Diego Library
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.
Keyword:
Avalon, Samvera, Virtual Connect 2018, Lightning talk, Hyrax, and Metadata
Subject:
Avalon Media System and Samvera Community
Creator:
Hardesty, Juliet L and Young, Jennifer
Contributor:
Indiana University, University of Utah, and Northwestern University
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
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.
Keyword:
Metadata, Connect 2017, Samvera, and Import/export
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.
Keyword:
Interest and Working Groups, Metadata, and Connect 2017
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
Keyword:
Resource Description Framework (RDF), Connect 2016, Hydra, Portland Common Data Model (PCDM), Metadata, and Workshop
Subject:
Hydra Project
Creator:
Matienzo, Mark, Harlow, Christina, Johnson, Tom, and Hardesty, Juliet L
Tiernan, Peter, Kenny, Stuart, and Cassidy, Kathryn
Contributor:
Trinity College Dublin, European Regional Development Fund, Higher Education Authority, Ireland, Department of Jobs, Enterprise and Innovation, Ireland, and Ireland's EU Structural Funds Programmes 2007-2013
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
Keyword:
Interest and Working Groups, Connect 2015, Metadata, Preservation, Service management, Archives, User experience, Geodata, and Hydra
Subject:
Hydra Project
Creator:
Hwse, Patricia, Awre, Christopher L, Green, Richard A, Goldman, Ben, Estlund, Karen, Hardy, Darren, Cramer, Tom, and Ramsey, Ellen C
