Northwestern University hosted Samvera Connect 2017 (Connect’s Planning Wiki Page). Harsh P, LaRita R, Justin G, Jeremy F, Rick J, and Don B attended. Following the 3.5 day conference was 1.5 days of partner meetings (agenda and minutes).
- Internal DLT Team Meeting
- 2017-11-14 DIS Department Meeting
- 2017-11-20 Sprint Planning / Retrospective document
- Jeremy will join in the chartering of the Core Components Working Group; In some way we’ll participate
- Jeremy will begin chartering a “Permissions Refactor Working Group” with a goal to prototype a system for permission enforcement and grants.
- Harsh will draft a definition list of testing terms, draft an email, discuss, and promote document.
- Justin and Erin F of Stanford will draft an AWS Lambda best practices document and promote to the community.
- Justin will propose “Container Interest Group” with a goal of establishing and leveraging community best practices. This is dependent on Jeremy proposing the Permissions Refactor Working Group and moving through that charter process.
- Justin and Harsh will follow-up on why other institutions transitioned from CloudFormation to TerraForm.
- DLT will reconcile the community timeline with internal timelines for the Mellon Grant, Curate migration to Hyrax, and Hyrax adoption of Valkyrie.
Notre Dame’s Participation and Facilitation
- Panel participation for Samvera and AWS
- Lightning Talk on permission refactoring
- Lightning Talk on “What I learned from working with students and how it’s positively changed our team”
- Panel facilitation What Should We Be Testing
- Design discussion on proposed permission refactoring (building on previous notes)
- Presented poster on Team Composition and Projects
ND’s DLT team members believe that we should incorporate our system adminstrators (ESU) into the Samvera community.
Other institutions are leveraging Docker, but this is an ad-hoc community effort. There are some minor changes we could submit to core gems to make container work easier.
This conference brought up distinction between Digital Collections (library digitization efforts) and Institutional Repository (capturing scholarly output), and the differentiation between these systems. I believe we should be pivoting CurateND’s effort to deliver on Digital Collections services.
The governance groups began adapting Apache governance model’s nouns and verbs. This was an organic result as we were describing processes, and does not reflect that we are adopting the Apache governance model.
There is repeated interest and curiosity in migrating Fedora 3 applications to Hyrax, while still leveraging Fedora 3. The pain point in migrating to Hyrax appears to be both an application migration and a data migration. The Hyrax w/ Fedora 3 migration path reduces one major moving part. We plan to explore that.
IIIF has reached a saturation and maturation point.
Hyrax has externally facing APIs, though they are not adequately documented. We will want to further explore this. I see Archivo and Zotero integration in the routes. I also know we can GET JSON-LD (
.jsonld), N-Triples (
.nt), and Turtle (
.ttl) responses .
Efforts of Other Institutions
Princeton (via Figgy) and Lafayette are leveraging Samvera tools for book digitization workflows.
Other institutions, in particular Stanford, have years of experience in AWS. They are moving away from CloudFormation to TerraForm. What were they experiencing that we have not or are not yet experiencing?
Documentation matters. It is a means towards greater inclusion; Thank you to an expert developer for drawing attention to this. It helps people orient to the project and the community.
University of Michigan created a GLOBUS connector in their Hyrax application to allow a repository user to asynchronously download a set of files to a GLOBUS location. This work was inspired by Notre Dame’s work on Bendo and it’s treatment of URLs and byte ranges.
University of Pennsylvannia has a similar storage topology as Notre Dame, there may be future alignment and conversations.
Discussion of Hyrax roadmap, spending, governance models, accessibility testing, documentation effort, and breakout session for roadmapping and resourcing.
- Call for a working group to identify a community funded position (Technical Manager or Community Manager) by next partners meeting in March 2018.
- Breaking into smaller groups we discussed the goals and actions for governance, roadmapping, and resourcing the core components, solution bundles, and the overall community (Session Breakout Notes).
- Roadmap for Hyrax identified v3.0 for Valkyrie integration (currently on v2.0 release).
- We (at ND) believe we can simplify application migration by creating a Fedora 3 Valkyrie adapter. Ben Armintor (of Columbia University) said we may be able to collaborate on that implementation.
- Core Components working group is forming (as of 2017-11-14 working on charter)