Samvera Partners Call
Friday, August 12th, 2022
11:30 am | Eastern Daylight Time (New York, GMT-05:00) | 1 hr
Join Zoom Meeting Link:
Join by phone
Dial by your location
+1 646 931 3860 US
+1 646 558 8656 US (New York)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
Meeting ID: 819 7331 3501
Find your local number: https://us06web.zoom.us/u/kkbAJ584n
Code of Conduct
We want Samvera Community to be a fun, informative, engaging event for all our partners and participants.
We encourage everyone to apply the Samvera community principles of openness, inquiry, and respect in their interactions at the event.
Please review the Code of Conduct and Anti-Harassment Policy.
If you have any questions or concerns, please feel free to reach out to community helpers.
Facilitator: Heather Greer Klein
Note Taker: Esmé Cowles
Karen Cariani (late, sorry)
Simeon Warner (last 30 mins)
Agenda & Notes
Any other items for the agenda?
Presentation: Marijane White from Oregon Health and Science University, re-presenting from 2022 Virtual Connect “So you think you want to self-host Samvera: A how-not-to-do-it guide”
Video forthcoming: https://www.youtube.com/watch?v=67ZsKW6y99M
Marijane is the Data and Research Engagement Librarian at OHSU, with a strong technology background as a semantic modeler/ontologist, content manager, tech writer, software tester/QA
Implemented Hyrax with the intention of consolidating ETDs, digitized books, images, and datasets. Started with ETDs as a first step.
Hired DCE to implement Hyrax for ETDs, deployed in early 2018. Migrated Bepress content and launched in January 2019.
Some staff departures, and hired (then) Notch8 to upgrade the system in summer 2019.
They have a system with limited scope they have little control over. Wanted a system to handle multiple types of content, and have more control.
Messy and missing metadata, wanted authority control.
Wanted dashboards for stats and configuration, but need to do this on the command line.
Updating is a bigger challenge than expected, want smooth, frequent updates.
Some limits that led to the current situation
Divided attention, limited budget, hard deadline.
Few options available in the market, no developers on staff (hiring freeze)
Gaps in planning and understanding
Didn’t have developers on staff, or plans long-term maintenance
Didn’t understand how limited the implementation was
Didn’t understand how facets would work, that back-end interfaces were accessible
Wound up using the system for more than ETDs, expected existing staff to cover gaps
Didn’t have plans for supporting additional content types, authority control, or long-term maintenance
Mismatch between staff strengths and Samvera
More of a go fast/go alone type, lots of workarounds, different deployment approaches
Struggled to engage with community
Conceptualized the repository as a catalog, expected metadata records to be the first-class (objects instead of Works)
How could Samvera community help?
A lot of things have happened to make the situation better today (Hyku, Bulkrax, Allinson Flex)
Hyrax documentation could use a lot of love
“Anything is possible” thinking is only true if you have the resources to do it yourself
What’s next? Did a big requirements analysis, came down to close call between Ubiquity and Tind (https://www.tind.io/)
Can you share your requirements spreadsheet? Want to check with colleagues, but expect to share this.
Do you think consortial approaches scale better to make open source adoption more workable? Yes, and we have some consortial systems. But a shared repository isn’t coming fast enough for us.
It’s challenging to know what the requirements are at the beginning of a project, and things can get more complex as you dig into the details. Having good guidance on what’s achievable would be good, maybe a flow chart asking what resources you have and suggesting what options might work for you.
Partner meeting poll results, discussion about when to meet in person again
Results point to better availability for Spring 2023
Will consult with partners to find the best time
Ithaka S+R Report on Digital Preservation – opportunity for questions/discussion
Heather encouraged them to encourage DuraCloud or other preservation-focused services instead of Samvera
Some of the statements about e.g., finances were very sweeping generalization that don’t seem accurate in all cases
Hard to make apple-to-apples comparisons between for-profit and non-profit orgs
Know Ithaka reports are widely read and respected, want to make sure everyone has the opportunity to ask questions about Samvera in this area
Would encourage a written response to this report, more than just this conversation or answering questions in various venues, published sources get more exposure than e.g. a blog post
Digital preservation is a set of activities, most of which aren’t even related to software (e.g., funding, staffing, organizational commitment, etc.), which aren’t represented in the report. The report seems to view preservation as something a single system can just do, but we see it as a far more complex area where a multi-faceted strategy makes more sense than expecting any single system to be a silver bullet
Feel like there is a general lack of knowledge about how to evaluate non-profits, which could be a good presentation topic
Heather on vacation next week August 15-19
Interest Group for Conference Management and Planning Charter – coming soon
Register for free for Samvera Connect Online 2022
Hyrax-Valkyrization Community Sprint September 6th - 16th
Please consider helping to staff this effort. Issues and testing are being organized by Julie, Daniel, and a volunteer from SoftServ. Testing and dev roles.
Anything for the Samvera Board? (Standing item)
Date of next call: September 9th, Repository demo from University of Hull
Notetaker for September call: