/
Samvera Tech Call 2026-04-29

Samvera Community Wiki

Samvera Tech Call 2026-04-29

Meeting Logistics

  • Time: 9:00am PT / Noon ET

  • Zoom Meeting URL: https://iu.zoom.us/j/87635137325?pwd=YhVGftEpANzAwgk84swAyF53edj31x.1
    (link will launch Zoom client – if you do not have Zoom, expand the instructions below)

  • Moderator: @Nicholas Mark Homenda (subbing for @Daniel Pierce )

  • Notetaker:  @April Rieger

Agenda Items

(Meeting notes below)

Attendees

  • @Tracy McCormick

  • @Shana Moore

  • @April Rieger

  • @Randy Kuehn

  • @Sarah Proctor

  • @Nic Don Stanton-Roark

  • @Christine Peterson

  • @Randall Floyd

  • @Rob Kaufman

  • @Mark Bussey

Meeting Process

  1. Standing pre-agenda items (moderator)

    1. Welcome

      • "Welcome everyone, please add your name to the Attendees list. If you are unable to do so, please let us know, and someone will add you. To any newcomers, welcome, and please feel free to ask questions. Likewise for all attendees. We strive for an open and accessible conversation around Samvera technology."

    2. Call for new agenda items

  2. Follow Agenda from above (facilitated by moderator) and record notes in Notes section below (note taker)

  3. Standing post-agenda items (moderator)

    1. Call for next moderator and note taker (moderator)

      1. Moderator:

      2. Notetaker:

    2. Samvera help follow-up (moderator)

    3. Pull request review (moderator)

      1. Recent Samvera PR list

  4. Post-meeting action (note taker)

    1. After call, this week's notetaker should create the agenda for the next call:

      1. Open template agenda titled "Samvera Tech Call XXXX-XX-XX"

      2. Click on ... in the top right corner, and select Make a copy.

      3. Popup will open for location. It should contain:

        1. Space: Samvera

        2. Parent page: (Verify value is current year)

      4. Select Make a copy. New page should be created.

      5. Modify the title to remove Copy of, update it with the next date, add moderator, notetaker, and any carry-over agenda info.

      6. Click Publish. 

Meeting Notes

PR Review

General PR queue:

https://github.com/pulls?q=is%3Aopen+is%3Apr+user%3Asamvera+sort%3Aupdated-desc

  • No additional discussion requested by the community

  • No blockers identified

 

Key PRs:

Hyrax PR 7421

https://github.com/samvera/hyrax/pull/7421

  • Rob and Shana discussed

  • Rob will review and respond

 

Bulkrax PRs by Rob

https://github.com/samvera/bulkrax/pull/1186

https://github.com/samvera/bulkrax/pull/1189

 

Additional PR on Rob's radar

https://github.com/samvera/hyrax/pull/7418

 

Discussion

Redirect Field and Metadata Schema

  • A redirect attribute was added to the metadata schema

  • Controlled by a feature flag

  • Should not display unless enabled

  • If enabled it should be included in the schema regardless of other metadata settings

 

M3 Profile and Flex Schema Strategy

  • Using flex schema means implementers manage special use fields

  • Example sort by created date requires defining that field

  • This is the current practice

 

Redirect vs Permalink

  • Mark asked how redirect relates to existing permanent URL fields

  • Rob explained

    • Works will have a canonical URL based on NOID

    • Redirects and slugs sit on top of that

    • Used for human readable or legacy URLs

    • Slugs are a subset of redirects

 

Direction

  • Notch8 is working to make redirects a core feature

  • Need to avoid breaking existing slug or redirect implementations

  • Allow a smooth upgrade path

 

Metadata Strategy

Mark's view

  • Keep metadata profiles minimal

  • Features should only work if required metadata exists

  • Avoid forcing metadata requirements to reduce resistance

 

Rob's view

  • Flex schema gives full control to metadata librarians

  • Important because librarians have strong preferences

 

Shana and LaRita input

  • Need both feature flags and Hyrax configuration

  • Feature flags control UI and tenant behavior

  • Hyrax config controls backend behavior

 

Redirect Defaults and Global Config

  • If no redirect exists default is empty array

  • Possible approach

    • Define global default URL patterns like work/id or collection/id

    • Avoid needing to populate each record manually

 

Migration and Adoption

  • Need a path for institutions like Adventist and Louisville

  • Likely involves Bulkrax updates and metadata changes

 

Ideas

  • Provide migration guidance

  • Possibly add a shim for backward compatibility

 

Next Steps

  • Rob will meet with Randy to review implementation once beta is ready

  • Ensure compatibility with existing systems

  • Validate integration approach

 

Action Items

Rob

  • Review Hyrax PR 7421

  • Review PR 7418

  • Meet with Randy once beta version is ready for their use-case and testing

 

Group

Continue discussion on metadata flexibility and redirect design

 

Next Meeting

  • Moderator April

  • Notes Rob