2025-06-12 Partner Call

Facilitator: @Heather Greer Klein

Note Taker: @Nicholas Mark Homenda

Attendees

• @Nick Steinwachs

• @Nicholas Mark Homenda

• @Heather Greer Klein

• @dmoles

• @Karen Cariani

• @Chris Awre

• @John Weise

• @Alberto Martinez

• @Christine Peterson

• @Annamarie Klose

• @david.schober

• @Kirsten Leonard

• @Jill Morris

Agenda & Notes

1. Additions to the agenda?
   
   

2. Samvera Europe meeting recap

   1. 50/50 current/potential Samvera users

   2. University of Leeds: ePrints users, IIIF, Fedora, want to keep up with Samvera

   3. Lancaster Digital Collections: joint shared repository (with Manchester) originally developed at Cambridge, interested in Hyrax

   4. Discussion about bot attacks and mitigation strategies

   5. Updates from Oxford, Durham, CoSector

   6. Fostering dialogue about developing repositories

   7. John Kunze: ARK identifiers

   8. Lots from IIIF conference, too

      1. Morphosource

      2. Lots of other users we had no idea about!

      3. Question about research data use

         1. Some, but not primary focus of IIIF

         2. Concern about stability of domain-based repositories, folks may be turning to institutional data repositories in the future

      4. Opportunity (esp. for Hyrax and Hyku) to become preferred IIIF repository

         1. More than a manifest for a work

         2. Collections, search results, annotations

      5. Common issues with open source communities (growth of IIIF, navigating the community)
         
         

3. Discussion: Developer recruitment and making the case for recruiting remote developers

   1. If you employ a digital library developer or developers, are they in remote positions, or is the expectation that they relocate to live near the institution?

   2. If your developers work remotely, can they live anywhere in the U.S., and if so, are you aware what institutional structures or precedents are in place that make this possible?

   3. Notch8 has an instance of a developer moving to another country

   4. PALNI has developers living in multiple states

   5. Would be helpful to have additional information about the developer time and staffing requirements needed that can be shared with decision-makers - what it takes to stand up a repository, continue to develop on a repository.

   6. Could better document amount of developer effort needed for each platform

   7. Trouble retaining Ruby/Rails developers needed to sustain Hyrax at an institution

   8. Importance of teams vs. lone wolves for support and retention

   9. Aligned organizations could form soft teams. Samvera could offer structure for this. “all of this seems like an opportunity for Samvera to bridge a gap… I wonder about Samvera-related services WRT to teams, farming out work”

   10. Notch8 proposes: onboarding adopter “buddy” system.

       1. Michigan has a similar system: one in related department, another is a “culture buddy”
          
          

4. Other Updates: 

   1. Sign up to present or facilitate a topic (5 - 30 minutes) at a 2025 Partner call - see list of ideas on the page

      1. Next month: Paul Walk, COAR Notify work

   2. Samvera Connect 2025 Mexico City Call for Proposals open

      1. https://samveraconnect2025.sched.com/

   3. October Developer Training Camp - seats still available! Tuition is free in exchange for one 2-week Samvera Community sprint

   4. Recruiting for a Hyrax Tech Lead for 2026

      1. Daniel and Randall are cycling off at the end of 2025

   5. Hyku 7 Upgrade Community Fundraising - several institutions looking into contributions

   6. Fedora 6 performance testing

      1. Reach out the @Nicholas Mark Homenda
         
         

Anything for the Samvera Board? (Standing item) 
Date of next call: July 10, 2025 Notetaker for next call: @Chris Awre