Samvera Community Wiki
Metadata Call 2026-03-24
Time: 2:00pm-3:00pm Eastern / 1-2 pm Central / 11 am-12 pm Pacific
Community Notes: https://docs.google.com/document/d/1G8wmi9R3q1uHatQLa3JfmlVr1-laTO5vgYzUZz-B7QU/edit?tab=t.0
2026-03-24
Moderator(s): Annamarie Klose
Notetaker: Emma Beck
Attendees:
@Emma Beck (University of Louisville)
@Rachel Howard(University of Louisville)
@Nic Don Stanton-Roark (PALs)
@Benjamin Riesenberg (U. of Oregon)
Steve McDonald (Tufts University)
@Sarah Proctor (Notch8)
@Sarah Cogley (University at Buffalo)
@Anna Goslen (UNC-Chapel Hill)
@Annamarie Klose (Ohio State University)
@Nick Steinwachs (Notch8)
@Morgan McKeehan
@Jessica McMillen
Agenda:
Samvera updates
Samvera Virtual Connect 2026 CFP, https://samvera.atlassian.net/wiki/spaces/samvera/pages/3811377153/Samvera+Virtual+Connect+2026
Hyku 7 was released today!
Sample CSV template importer from bulkrax updates
Talk to Nic Don if you want access to a testing site
Samvera sprint going on
Flexible metadata is in Hyrax
From the Hyrax docs: Hyrax v5.3 and later includes flexible metadata functionality that allows administrators to configure metadata schemas through the UI using M3 (Machine-readable Metadata Modeling) profiles. This feature is disabled by default and must be explicitly enabled.
Community sprint, https://samvera.atlassian.net/wiki/spaces/samvera/pages/3716579329/Community+Sprint+Event+March+23rd+-+27th+2026
Presentation from Oregon Digital (Oregon State & University of Oregon) - custom metadata, RDF
Slides are at: tinyurl.com/20260324-odmd
165 total metadata fields for Hyrax works (153 for generic/9 document/3 image)
Not sure how they stack up against others
Most fields take text but many take URIs
35 source vocabularies, allowable sources vary by field
Future work - RDF? Linked Open Data (LOD)
Strong in linked, want to build out the other two
Might want to make some changes before exposing it publicly
Identifying the URIs used most common
Minting URIs for local CV
Oregon Digital has both Oregon State and University of Oregon - both archival and non-archival (government agencies, departmental works, IR, etc)
Facets remain constant through collections
Subject also pulls from keyword
keywords - textile collection, such as using materials as a field in a non-controlled way but to retain the information and help it be searchable
Have the ability to build a user collection - default in Hyrax
Tombstone button
Saving a record but removing access to a url - often happens around rights issues
Digital preservation policy related
isPartOf information for parent/child relationships.
“Share this” url -
Whats the organizational staffing model? Somewhat informal, staff at both institutions work on development, staff at OSU and UO works on their own collections, different working groups for Oregon Digital bridging between, Metadata working group meets regularly
Open discussion