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 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
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.
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.
Keyword:
Marketing, Screencast, Interest and Working Groups, Code of Conduct, Virtual Connect 2020, Samvera, Roadmap, Permissions, Contribution Model, and Controlled vocabulary
Subject:
Samvera Community
Creator:
Hilt, Jessica, Hardesty, Juliet L, Ruggaber, Robin, Kaufman, Rob, Awre, Christopher L, and Friesen, Jeremy
What does it mean to be a Hydra Partner? What does the Hydra community expect of Partners? What should Partners expect of the rest of the community? Join us to discuss expectations, contributions and the advantages of Partnership. and An audio recording (of mixed quality) of a panel session at Hydra Connect 2016 described thus
Migrating a Fedora 3-based Hydra repository to Fedora 4 can be a major undertaking. This panel will bring together representatives from multiple institutions that either are planning for, are in the midst of, or have completed such a migration. Depending on where they are in the migration process, panelists will talk about their plans for migration, techniques used or expected to be used, obstacles anticipated or encountered, how problems were addressed, and migration outcomes. It is hoped that the presentations and discussion will be useful to other Hydra sites planning such a migration. A video of this session is available at the 'Related URL' below. and A presentation given at Hydra Connect 2016 described thus
Keyword:
Fedora, Connect 2016, Hydra, and Migration
Subject:
Hydra Project
Creator:
Coble, Jim, Wead, Adam, Hardesty, Juliet L, and Friscia, Mike
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 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
