2018.11.14 Community Meeting

Call-in Details

• 11am ET
• https://duraspace.zoom.us/my/vivo1
• or Telephone:
  • US: +1 669 900 6833 or +1 646 876 9923
  • Canada: +1 647 558 0588
  • Australia: +61 (0) 2 8015 2088
  • United Kingdom: +44 (0) 20 3695 0088
  • Meeting ID: 812 835 3771
  • International numbers available: https://zoom.us/u/MO73B

Attendees

• Andrew Hankinson (Bodleian Libraries, University of Oxford)
• Andrew Woods (Duraspace)
• Courtney Mumma (Deputy Director, Texas Digital Library)
• Joshua Westgard (Digital Programs, University of Maryland Libraries)
• Brian McBride (Head of Digital Infrastructure Development, University of Utah)
• Doron Shalvi
• Michelle Paolillo (Cornell University)
• Tom Wrobel (Bodleian Libraries, University of Oxford)
• Neil Jefferies (Bodleian Libraries, University of Oxford)

Regrets

• Julian Morley
• Rosalyn Metz
• Simeon Warner

Agenda

1. Introductions and statements of interest
2. Community input on Alpha
   • Questioning mixed use of file paths and digests
   • Describe significance of user field
   • Digest suggestions from v0.1
   • Support for empty directories (v0.1 feedback)
   • Bagit Example
   • Logical organisation of OCFL storage root
   • Do we really want to retain type = Object and Version with plain JSON?
   • Add inventory schema to Storage Root?
   • Logical file paths - directory separators
   • Normative opinions on filesystem features
   • Review introduction to spec
3. Comments on Implementation Notes?
4. Steps to Beta

Notes

Introductions

• Courtney Mumma: Hosting content from across the state of Texas. ASK: Might consider an 'elevator pitch' to help frame and explain OCFL.
• Josh Westgard: Help navigate future migrations; treat collections as "mostly stable" so we can treat them in a way that takes advantage of their stability.
• Brian McBride: Sustainability and data modelling in repositories, common storage between different applications; coalescing a common specification.
• Michelle Paolillo: Cornell is rebuilding long-in-the-tooth systems. Likes the idea of rebuildability and 'tripping over data and reconstructing a repo'.
• Tom Wrobel: Rebuildability has been key in previous migrations
• Doron Shalvi: Heavy Fedora 3 user; organized files for preservation & access that made sense to them. Sees OCFL as an attempt to move to something standard. Sees benefits for applications in Access and values transparency on the disk. How do we organize and serve up derivative content meant for public consumption.
• Andrew H.: OCFL is going to be useful for preservation and access copies.

Issues

1. Digests:
   • Confirmation that folks are satisfied with reducing the MUST to a SHOULD for digests:

   OCFL Objects should use sha512 by default.

2. Empty directories:
   • How are people handling these?
   • .keep was a good way of handling this
   • Need to reach out to Justin Littman about experiences re: adding data where there was none.
3. Logical Issue of OCFL Storage Root
   • Tom: Interested in machine-readable forms of Storage Hierarchy layout
   • Interest in being able to validate structure of OCFL filesystem
   • Nice to record/configure that pattern
   • Would like to have a client be able to map a UID to an object
   • Map json.uri to local registry of patterns
4. Roadmap
   • Moving towards Beta now
   • Targeting early 2019 for 1.0 release

Audio recording

• 2018-11-14.mp3

Action Items