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.
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 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 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.
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
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.
Working and Interest Group Updates Code of Conduct WG - Jessica Hilt Contribution Model WG - Robin Ruggaber Roadmap Council - Rob Kaufman Marketing WG - Chris Awre Controlled Vocabularies Decision Tree WG - Julie Hardesty Hyrax Permissions WG - Jeremy Friesen The video recording of this segment is available at the 'Related URL' below.