/
Samvera Tech Call 2025-07-23

Samvera Tech Call 2025-07-23

Meeting Logistics:

Agenda (meeting notes below)



Moderator: @Randall Floyd

Notetaker: @Chris Colvard

Attendees:

  • @Daniel Pierce

  • @Heather Greer Klein

  • @Sarah Proctor

  • Randy (Kuehn?)



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. Lots of time spent processing responses from fedora

    1. Valkyrie Fedora adapter resource query cache: GitHub - samvera/valkyrie at resource_cache @Daniel Pierce

    2. In-memory cache of built object with fedora etag

    3. Subsequent requests will send etag to fedora and use cached object if not changed

    4. Fedora 5 container in Valkyrie spec tests not starting properly and not responding

    5. Over request cycle about 50% speedup

    6. Daniel will talk with Fedora and Valkyrie folks about moving this forward

  2. VisibilityCopyJob and InheritPermissionsJob have large overlap and take a long time to process

    1. Lots of time spent walking work membership

    2. Experiment to combine functions of long-running jobs for visibility copy to reduce Fedora requests (related to above ^^): Combining ACL and visibility to prevent duplicative reads from Fedora · samvera/hyrax@c8eabd6

    3. Cuts processing time in about half for changing a work’s visibility

    4. Solr Indexer batch processor work by @Rob Kaufman similarly should help by reducing duplicate work being done by the system

      1. Might not speed things up by clock time but reduce system strain

  3. PRs needing reviews:

    1. UV upgrade

  4. Next Meeting: 7/30/2025

    1. Moderator: @Daniel Pierce

    2. Notetaker: @Randall Floyd