2021-03-12 Partner Call

Code of Conduct

We want Samvera Community to be a fun, informative, engaging event for all our partners and participants. We've got a few strategies to help make this happen:

If you have any questions or concerns, please feel free to reach out to community helpers. 

• Samvera Code of Conduct and Anti-Harassment Policy

• Samvera Participation Guide 

Date

Mar 12, 2021

Facilitator: @Heather Greer Klein

Note Taker: @Esmé Cowles

Attendees

@Heather Greer Klein

@Robin Lindley Ruggaber

@Rosalyn Metz

@Nabeela Jaffer

@Brian McBride

@Chris Awre

@Karen Cariani

@Glen Horton (Deactivated)

@Alicia Morris (Deactivated)

@Stuart Kenny

@Nora Zimmerman

Adam Malantonio

@Simeon Warner (first 30 mins only)

Agenda and Notes

1. Any other items for the agenda?  
   
   

2. Lafayette Digital Repository demo - Nora Egloff & Adam Malantonio, Lafayette College
   
   

3. Overview of fiscal sponsor change recommendation, Samvera Bylaws change vote with Q&A (Heather Greer Klein, Rosalyn Metz)

4. Fundraising and Finance Committee plans
   
   

5. Current calls to action from the Samvera Community Asks page

   1. Call for presentations, Virtual Connect 2021

   2. Call for participation, Spring Developer Congress

6. Anything to raise with the Steering Group (standing item)

7. Date of next call: April 9th, 2021 - “Meadow” cloud based digital collections and asset management repository - Northwestern University

   1. Spring 2021 Partner Meeting, April 12 - 13

8. Notetaker for next call:

Notes

1. Fiscal sponsorship recommendation

   1. Finances were part of the decision, but also legal implications because the different options had different legal status

   2. Would partner contributions change? No, they would stay the same. Fiscal sponsor fees would be absorbed into existing operating budget.

   3. OASIS looks very hands-off, do we think they will encourage or facilitate engagement with other OASIS projects? We think they would be open to that. They mostly host standards now. So Samvera is a slightly different direction for them, and they've been open to our ideas and suggestions so far.

   4. Are there implications for Lyrasis' participation in Hyku? We've talked to them and we don't think it will impact that.

   5. What's the latest status? We'd like to wrap up voting by the deadline on Tuesday. We've received 15 positive votes so far, please reach out to @Heather Greer Klein or Samvera Steering if you haven't voted and have any questions. The next step is taking our application to the OASIS board of directors.

   6. One other point: there is no default option here — if we didn't move forward with OASIS, we'd need to make some other decision, because even staying with Lyrasis would mean significant changes.

2. Demo of Lafayette Digital Repository, @Nora Zimmerman and @Anna Malantonio

   1. Lafayette has finished migrating two separate systems to their new repository and had public launch.

   2. Had two different platforms and wanted to consolidate to make it more managable:

      1. https://ldr.lafayette.edu (DSpace) for typical IR content, dating back to 2012

      2. https://digital.lafayette.edu (Islandora) for digital collections

   3. Single interface for all content types: https://ldr.lafayette.edu/, key features:

      1. Based on Hyrax developed by a sole developer (Adam)

      2. One of the main collections is newspapers going back to 1870

      3. Single-sign-on integration

      4. Gallery view for collection browsing (with nested collections)

      5. Metadata enhancement and remediation (previously each collection had its own metadata model in separate metadata management system, some collections going back 20+ years)

         1. Used Questioning Authority to help remediate metadata

         2. Implemented Duke's Humanized EDTF gem for human-readable date ranges

   4. Hyrax enhancements

      1. Contextual search results (user searches to get to item, then need to search within an object to find the term in multi-page documents)

      2. Added Getty TGN for more coverage (Manchuria wasn't in GeoNames!)

      3. Handle.net permalinks, now all content has citable permalinks

      4. IIIF integration with UV viewer

      5. DPLA integration, harvested using OAI-PMH, served by the blacklight_oai_provider gem

   5. Source code on Github: https://github.com/LafayetteCollegeLibraries/spot

3. Fundraising and Finance Committee plans

   1. Slight changes in the process: most financial matters would be handled by Steering, but we would create a fundraising subgroup

4. Current calls to action from the Samvera Community Asks page

   1. Update your information in the list of in-production Samvera repositories, and add an interesting item from your collections so it can be added to the map

   2. Call for presentations, Virtual Connect 2021

   3. Call for participation, Spring Developer Congress

   4. Spring 2021 Partner Meeting, April 12 - 13 - add any topics you'd like to discuss to the unordered agenda

5. Standing Item: Any issues to raise with Samvera Steering?

6. Notetaker for next call: Next meeting is Partner Meeting

   1. @Hannah Frost