Samvera Community Wiki
Metadata Call 2026-04-28
Time: 2:00pm-3:00pm Eastern / 1-2 pm Central / 11 am-12 pm Pacific
Call-In Info: Join our Cloud HD Video Meeting
Community Notes: Samvera Metadata Interest Group Meeting: 2026 Rolling Minutes
2026-04-28
Moderator(s): Emma Beck
Notetaker: community support
Attendees:
@Heather Greer Klein
@Annamarie Klose (Ohio State University)
@Rachel Howard (University of Louisville)
@Benjamin Riesenberg
@Emma Beck (University of Louisville)
@Anna Goslen (UNC-Chapel Hill)
@Morgan McKeehan (she/her/hers), Oregon State University Libraries & Press
@Sarah Cogley (University at Buffalo)
@Christine Peterson (CPC)
@Nick Steinwachs (Notch8)
Agenda:
Samvera updates
Roadmaps alignment group
Slight change in the name to Samvera Roadmaps Working Group Samvera Roadmaps Working Group
Name change clarifies that this group aligns work with the roadmaps but also creates the roadmaps
They are still tracking and timelining work on the various Samvera projects). The most recent meeting discussion was about FITS hosting changes.
SPARQL to RDF with Benjamin Riesenberg
A lot of work was done prior to Benjamin’s arrival to integrate RDF into Oregon Digital, such as requiring URIs
Benjamin learning what is custom to Oregon Digital and what is common to Hyrax
Able to export n-triples as a repository administrator, however showing a turtle serialization in this demo
RDF from Oregon Digital not quite ready to be published. Have to do some processing first.
Can also transform RDF with SPARQL using SPARQL CONSTRUCT, not just query
Benjamin also using Python rdflib for processing
Filtering out administrative fields, creating more concise descriptions
Fixing data types & language tags, for example, dates typed as strings, descriptions not tagged with language
Not currently publishing data, but assessing what would need to be done if wanted to publish
Is Oregon Digital unique in being able to export RDF? Is it because Fedora 4 stores it?
Sub-collections
Is anyone using this? Is it searchable?
From Eleni: amigos has a library that heavily uses sub-collections and doesn't like that you can't out-of-the-box search all the works that are contained in their various sub-collections without needing to be directly within that one specific sub-collection. The workaround I've been told is to make the works also searchable at the top-level collection but that seems like a lot of duplicate extra work. I made a github issue about it:
Misleading help text when searching for results in nested collections · Issue #2862 · samvera/hyku IU uses sub-collections (unit-level collections contain collections with all of the works we are organizing) but searching doesn't start off restrictable to a sub-collection - you have to go to that collection landing page and then search or conduct an overall search and then use facets to narrow down to a particular collection.
OSU is using sub-collections depending on the collection and curator
Achieves this through nesting the sub-collections, similar from what Layfette is doing
Not the best when looking at it in the collection facets
In blacklight
UofL would like for it to be easier to share sub-collections with their largest collection
Tufts uses sub-collections as an organizational feature
On the public facing side it helps to facet by the sub-collection
Follow-up from prior meeting
So many of us are using AI for accessibility. What is the quality level though?
Sarah Cogley at Buffalo has a lightning talk at OpenRepositories about the AI rubric they have done
Open discussion