Samvera Tech Call 2025-07-30

Samvera Tech Call 2025-07-30


Meeting Logistics:

Agenda (meeting notes below)

  • Continuation of support conversation from Slack: Jamen McGranahan seeking guidance connecting Sirenia-based app to external F6 with existing data (via a non-samvera migration path?) @Randall Floyd

  • Bitnami helm charts changes



Moderator: @Daniel Pierce

Notetaker: @Randall Floyd

Attendees:

  • @Tracy McCormick

  • Jamen McGranahan

  • Brad Watson

  • Shana Moore

  • Rob Kaufman

  • Nic Don Stanton-Roark

  • Sarah Proctor




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 copy.

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

        1. Space: Samvera

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

      4. Select 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. Click Publish. 




Notes

  1. Randall/Jamen: Using data originally from Islandora/Fedora 3 and migrated to Fedora 6 (using Fedora tooling?) in Hyrax?

    1. Hyrax has its own metadata format and requirements, probably won’t understand the existing data.

    2. It is possible to create a custom migration tool that can convert objects to Hyrax works.

    3. Rob: Having tooling to help migrate applications stuck in Fedora 3 to current Hyrax would be useful to the community.

      1. Potential for community sprint around this?

  2. Rob: Tests passing on hyrax flex metadata PR.

    1. Fixed gnarly timing issue that might be cause of flaky specs on main

    2. Based near attributes interfering with reform code that modifies *_attributes fields, affected by code loading order.

    3. Skipping default behavior in based near module so that the desired behavior is the only option

    4. Long term fix is to not use *_attributes for the field name in cases like these.

  3. Solr 9 PR has fix for pcdm membership solr query

  4. La Rita opened a PR to fix creating a work in a collection via its dashboard show page.

  5. Bitnami’s container images will soon no longer be updated. Rob will post more about this in Slack.