A lightning talk (seven minute) presentation given at Samvera Connect 2020 On-line described thus and The Controlled Vocabulary (CV) Decision Tree is meant to provide guidance for selecting and using controlled vocabularies behind descriptive metadata fields. This guidance is useful within Hyrax and other software incorporating metadata fields that could benefit from controlled terms for consistency and accuracy. We will share the decision tree for selecting and modifying controlled vocabularies and the accompanying list of controlled vocabularies that we hope to collaboratively grow. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording.
Keyword:
Interest and Working Groups, Lightning talk, Connect 2020, Samvera, and Controlled vocabulary
A presentation at Samvera Connect 2020 described thus and Update on recent and coming work for the Hyrax repository-building engine. The 'Related URL' below links to the start of this presentation in the YouTube recording of the day's events.
A lightning talk at Samvera Virtual Connect 2019 described thus and What if the Hyrax web application were to support and include, by default, controlled vocabularies from marginalized communities? Currently Hyrax supplies a default set of descriptive metadata fields for describing uploaded objects. This set of fields includes Keyword (a required field) and Subject (an optional field). Neither of these fields are controlled by a vocabulary of terms upon install. The Questioning Authority (QA) gem exists as an option to configure and apply controlled vocabularies for use with fields such as these in Hyrax. While QA can be configured to work with nearly any vocabulary, the current vocabularies offered through the gem when it is installed include LCSH/NAF/GFT/MPT/DGT, FAST, Geonames, MeSH, Agrovoc, DBPedia, NALT, and Getty (AAT, TGN, ULAN). These are widely used mainstream sources for topical subject and genre description but also tend to reflect the current dominant mainstream power structure in the United States (white, male, straight, able-bodied, middle-class, Christian, Anglo). Should we increase the list of vocabularies available, by default, in the QA gem? Should we go beyond that and enable vocabulary choices on the default Subject and Keyword Hyrax fields? This lightning talk will discuss these questions and consider vocabulary options that would provide more inclusive descriptive capabilities.
Keyword:
Controlled vocabulary, Samvera, Virtual Connect 2019, Lightning talk, and Hyrax
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
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 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
A presentation given at Connect 2017 described thus and Presentation on a gem for Hyrax models and authorities, which provides a central place for creating models for different types of works. Each new model draws on a central pot of properties to declare the set of properties needed to fully describe the particular work. The gem already exists and has sample models for journal article, thesis and more. In this presentation we will work through the process of defining a new model and then using that model in a Hyrax application. The idea behind the gem is to make it easier for developers to deploy new models, and provide a place for metadata folks to jointly define re-usable models.
Keyword:
Hyrax, Connect 2017, and Samvera
Subject:
Samvera Community
Creator:
Hardesty, Juliet L and Allinson, Julie
Contributor:
CoSector, University of London and Indiana University