2022-12-09 Partner Call




Samvera Partners Call

Friday, December 9th, 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
Passcode: 603236
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.

  1. We encourage everyone to apply the Samvera community principles of openness, inquiry, and respect in their interactions at the event.

  2. 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: volunteer needed!


  • Your name here!

  • @Robin Lindley Ruggaber

  • @Thomas Scherz

  • @david.schober

  • @Jon Dunn

  • @Jessica Hilt

  • @Nicholas Mark Homenda

  • @Esmé Cowles

  • @Hannah Frost

  • @Rosalyn Metz

  • @Alicia M. Morris

  • @Kevin Kochanski

  • @Emily Lynema

  • @Chris Awre

  • @Mat Jordan

  • @Alberto Martinez

  • @Simeon Warner

  • @Rob Kaufman

  • @Jim Halliday

  • @Kirsten Leonard

  • @Franny Gaede

  • @Brian McBride

Agenda & Notes

  1. Any other items for the agenda? 

    1. Nothing added

  2. Demo from Northwestern University: Serverless API for IIIF

    1. https://youtu.be/rgWsgdVB858

    2. @karen.didrickson and @Mat Jordan presenting

    3. as=iiif all data returned as IIIF

    4. Current: dcapi was a simple opensearch proxy, and iiif was static manifests, no collections, and regeneration problem

    5. New Solution: restful api, what if all things were iiif, including search, what if iiif powered more things than just a viewer

    6. All iiif is just a serialization

    7. implemented using AWS SAM, and serialized using lambdas.

    8. 1mil requests at 20 ms is ~.04

    9. as much as possible front end is all iiif

    10. any response from the api can be returned as a IIIF including search results as collections, items, etc

    11. we’re not delivering canvases in collection

    12. all of a work and metadata are IIIF and “related items” are also IIIF

    13. all the metadata for a page is included in the IIIF manifest not two separate requests

    14. large responses: chunked response and next page is itself a collection at the end scales well

    15. bloom, clover, and serverless iiif are in either labs or core

    16. Q what do you do with things like facets

      1. Not everything fits into a manifest

      2. we are using a “see also” for the full pipeline

      3. we’re using iiif as our primary datasource for UI components

      4. Search results are powered by a normal elasticsearch

      5. Digital Collections Next.js
        Digital Collections API v2
        Bloom IIIF
        Clover IIIF
        Nectar IIIF
        Serverless IIIF

  3. Nurax testing instances – upcoming changes

    1. Hyrax Maintenance Working Group is adding responsibility for maintaining these testing instances

    2. DCE has asked not to be responsible for hosting

    3. HMWG would take on responsibility, looking for expertise in DevOps. There’s an opportunity to take a different approach to how these are running.

    4. Samvera Comm. AWS instance

    5. What from the existing NURAX instances are folks relying on

      1. DATA not to be migrated (proposed)

      2. Users will be migrated (proposed)

  4. Components Maintenance proposals

    1. Product Owner requested for the following projects:


      iiif-manifest @karen.didrickson



  5. Maintenance Hours Pledge for 2023

    1. Do we need to do anything differently for 2023?

      1. Pledge is live, lots of things can count. Congresses, POs, Maintenance WG, Testing

      2. Ruby releases and prepping our tech for whatever that may bring

      3. no deadline for pledges, always open

      4. Adding on late is always welcome

    2. Hyrax Maintenance Working Group needs volunteers – see 2023 sprint

      1. last year we did a lot of pre-work before folks were ready. This helped folks feel productive

  6. Other Updates:

    1. 2023 Samvera Board elected members:

      1. Jeremy Friesen, Senior Lead Software Engineer at Software Services by Scientist.com

      2. Jessica Hilt, Manager of Applications Development, University of California San Diego (she’s really cool)

      3. Kirsten Leonard, Executive Director, Private Academic Library Network of Indiana (PALNI), Hyku for Consortia Project

      4. David Schober, Northwestern University Library Repository and Digital Curation Product Manager and Development Team Lead

    2. Sign up for 2023 Partner Call Demos

    3. Developer Congress January 23rd -27th – Hyrax Maintenance WG is leading, but all technologies welcome to use this time for community effort

      1. New Ruby release

      2. Hyrax Valkyrization development work

      3. HMWG leading this, but anything is open.

    4. Samvera for Non-Developers Workshop January 5th, 2023

      1. Will be recorded and cut into chunks for the youtube page

    5. Samvera Connect 2023 – Heather looking for potential host Partners. No longer need to take on financial responsibility to host!

      1. We’re at a point where we do not need them to take on the financial responsibility

      2. Q: Would a host need to underwrite a hotel block? Samvera could underwrite.

Anything for the Samvera Board? (Standing item)

Date of next call: January 13th

Notetaker: @david.schober