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.
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: volunteer needed!
Attendees
Your name here!
@Robin Lindley Ruggaber
@Thomas Scherz
@david.schober
@Jon Dunn
@Jessica Hilt
@Nicholas Mark Homenda
@Esmé Cowles
@Hannah Frost
@Rosalyn Metz
@Alicia 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
Any other items for the agenda?
Nothing added
Demo from Northwestern University: Serverless API for IIIF
@karen.didrickson and @Mat Jordan presenting
as=iiif
all data returned as IIIFCurrent: dcapi was a simple opensearch proxy, and iiif was static manifests, no collections, and regeneration problem
New Solution: restful api, what if all things were iiif, including search, what if iiif powered more things than just a viewer
All iiif is just a serialization
implemented using AWS SAM, and serialized using lambdas.
1mil requests at 20 ms is ~.04
as much as possible front end is all iiif
any response from the api can be returned as a IIIF including search results as collections, items, etc
we’re not delivering canvases in collection
all of a work and metadata are IIIF and “related items” are also IIIF
all the metadata for a page is included in the IIIF manifest not two separate requests
large responses: chunked response and next page is itself a collection at the end scales well
bloom, clover, and serverless iiif are in either labs or core
Q what do you do with things like facets
Not everything fits into a manifest
we are using a “see also” for the full pipeline
we’re using iiif as our primary datasource for UI components
Search results are powered by a normal elasticsearch
Digital Collections Next.js
GitHub - nulib/dc-nextjs: Northwestern University Libraries Digital Collections built in Next.js
Digital Collections API v2
GitHub - nulib/dc-api-v2: API providing access to the rich collections of the Northwestern University Libraries
Bloom IIIF
GitHub - samvera-labs/bloom-iiif: (Deprecated) Please see https://samvera-labs.github.io/clover-iiif/docs/slider. Formerly: IIIF Presentation API Collection items React.js component that renders a horizontal slider.
Clover IIIF
GitHub - samvera-labs/clover-iiif: Extensible IIIF front-end toolkit and Manifest viewer. Accessible. Composable. Open Source.
Nectar IIIF
GitHub - samvera-labs/nectar-iiif: (Deprecated) Please see https://samvera-labs.github.io/clover-iiif. IIIF Presentation API 3.0 property fluent HTML5 primitives library for React.js
Serverless IIIF
GitHub - samvera/serverless-iiif: IIIF Image API 2.1 & 3.0 server in an AWS Serverless Application
Nurax testing instances – upcoming changes
Hyrax Maintenance Working Group is adding responsibility for maintaining these testing instances
DCE has asked not to be responsible for hosting
HMWG would take on responsibility, looking for expertise in DevOps. There’s an opportunity to take a different approach to how these are running.
Samvera Comm. AWS instance
What from the existing NURAX instances are folks relying on
DATA not to be migrated (proposed)
Users will be migrated (proposed)
Components Maintenance proposals
Product Owner requested for the following projects:
hydra-derivatives
iiif-manifest @karen.didrickson
ldp
questioning_authority
Maintenance Hours Pledge for 2023
Do we need to do anything differently for 2023?
Pledge is live, lots of things can count. Congresses, POs, Maintenance WG, Testing
Ruby releases and prepping our tech for whatever that may bring
no deadline for pledges, always open
Adding on late is always welcome
Hyrax Maintenance Working Group needs volunteers – see 2023 sprint
last year we did a lot of pre-work before folks were ready. This helped folks feel productive
Other Updates:
2023 Samvera Board elected members:
Jeremy Friesen, Senior Lead Software Engineer at Software Services by Scientist.com
Jessica Hilt, Manager of Applications Development, University of California San Diego (she’s really cool)
Kirsten Leonard, Executive Director, Private Academic Library Network of Indiana (PALNI), Hyku for Consortia Project
David Schober, Northwestern University Library Repository and Digital Curation Product Manager and Development Team Lead
Developer Congress January 23rd -27th – Hyrax Maintenance WG is leading, but all technologies welcome to use this time for community effort
New Ruby release
Hyrax Valkyrization development work
HMWG leading this, but anything is open.
Samvera for Non-Developers Workshop January 5th, 2023
Will be recorded and cut into chunks for the youtube page
Samvera Connect 2023 – Heather looking for potential host Partners. No longer need to take on financial responsibility to host!
We’re at a point where we do not need them to take on the financial responsibility
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