Samvera Data Mapper Working Group

Scope & Objectives

This group will work towards generating a Minimum Viable Product (MVP) repository solution which enables the use of multiple disparate storage backends for both files and metadata using the Data Mapper pattern, as a proof-of-concept for improving the flexibility of the Samvera architecture. In doing so, it will broaden the potential adoption base and provide the ability to compare pros/cons of various configurations for each institution. This group will attempt a solution which:

1) Enables persistence of metadata into at least two different backends (one being Fedora.)

2) Enables persistence of binary resources (files) into at least two different backends (one being Fedora.)

3) Reduces the dependence of Samvera's front-end on inter-community gems, preferring solutions with a larger adoption.

4) Provides a suite of tests for creating further backends without altering the front-end business logic.

Assuming success, the group will build a list of strategies for implementing this code in the core Samvera infrastructure.

Deliverables & Timeframe

1. Generate an MVP repository which can persist to two or more backends.
   1. Agree upon a representative set of features necessary for confidence that this strategy will work in the core of Samvera.
   2. Participate in scheduled week-long development efforts for development.
   3. Recognize and document differences between persistence backends and the impact of use cases on our requirements for each.
2. On Success
   1. Generate a document of recommendations on how to implement the code in the core of the Samvera stack.
   2. Found here: Hyrax Implementation Recommendations
3. On Failure
   1. Generate documentation on what failed, why, and potential next steps.

The group can begin in early May 2017. The group will be sunset by November 2017, with a report during Samvera Connect.

Meeting Times & Communication Channels

• Meetings: Every Thursday at 11:00 AM PST. Hangout link:

  https://hangouts.google.com/hangouts/_/event/cvo9a7tp415gnra6o1sahrobp3k?hl=en&authuser=0

• Meetings, meeting minutes, deliverables, and milestones will be announced on samvera-partners@googlegroups.com, samvera-community@googlegroups.com, and samvera-tech@googlegroups.com.
• Until such time as it's determined that a dedicated channel should be created, communication will occur in the #dev channel of the Project Hydra Slack.
• Code will be committed to https://github.com/samvera-labs/valkyrie

Members

Note that to be a member of a Working Group, you must have have a CLA in place if you are committing code and you must consent to release documentation under a Creative Commons Attribution-Share Alike 3.0 Unported License.

• Trey Pendragon, facilitator (Princeton University Library)
• cb (Stanford University Libraries)
• Stuart Kenny (Trinity College Dublin)
• cmharlow (Cornell / Stanford University Libraries)
• Brendan Quinn (Northwestern University Libraries)
• Carrick Rogers (Unlicensed) (Northwestern University Libraries)
• csyversen (Northwestern University Libraries)
• Noah Botimer (University of Michigan)
• Joe Atzberger (Stanford)
• James Griffin (Princeton University Library)
• your name here (your institution here)
  
• (No limit, if full please add to bottom.)

Community Sprint Reports

• July 2017 Community Sprint

Resources

• https://github.com/samvera-labs/valkyrie
  
• https://github.com/samvera-labs/valkyrie/wiki/Frequently-Asked-Questions
• Hyrax Implementation Recommendations
• Data Mapper Working Group Retrospective

Meeting Notes

1. Running Notes: https://docs.google.com/document/d/1BeKVY5t5vrX7JNuDSMJz1MpEz09Poe0X1h02Y1gUFAg/edit