2019.05.08 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

1. Doron Shalvi
2. Jennifer Gilbert
3. Steve Liu
4. Josh Westgard
5. Peter Eichman
6. Bethany Seeger
7. Xin Wang
8. TA Nguyen
9. Ben Cail
10. Neil Jefferies
11. Noah Botimer
12. Aaron Birkland
13. David Wilcox
14. Simeon Warner
15. Calvin Xu
16. Yanru Bi
17. Andrew Woods

Agenda

1. Community updates
2. Beta updates
   • Who has a backward compatibility use case?
   • Unresolved Beta issues
3. Next meeting: Wednesday, Jun 12th @11am ET - reschedule due to Open Repositories?

Notes

Audio recording

• 2019-05-08.mp3

Pre-agenda

1. NLM: How OCFL can be used in a preservation and access architecture
   • Where an organization has both concerns (preservation and access)
   • Oxford is planning on this
     • IIIF over OCFL
     • Read-only dissemination
   • Brown: ID to filesystem mapping for IIIF?
     • Path in OCFL is the ID
   • NLM use cases
     • Preservation master in separate volume
     • Access copies in another volume
     • Potentially distributed OCFL could help
   • Stanford has separate master and access copies
     • OCFL to be used for the preservation system
   • Michigan
     • New dark repo, will be using OCFL
     • Will be developing a Ruby Gem
     • Terminology issues
       • "OCFL Object" is a bit long and ...conflicting
   • External / Distributed content
     • OCFL does not require content to be colocated
       • Manifests could allow for distributed addressing
       • Version 2 of the OCFL spec
     • How much effort do institutions need to put towards moving content?
     • Cornell is planning on OCFL replication

Community updates

1. CNI Presentation
2. Oxford update
   • Redesigning archive/repo
     • Currently Samvera / Fedora
     • Designing to include to OCFL
   • Details around locking / transaction being handled at the application-level
3. JHU OCFL library
   • Working with Tom Wrobel at Oxford
     • Oxford has shown excellent ingest performance with the OCFL library
4. NLM
   • Planning on OCFL hacking
   • Python library could use some poking
   • https://github.com/OCFL/spec/wiki/Implementations

The Road to Beta

• https://github.com/OCFL/spec/milestone/2
• Beta release after three minor issues
  • One substantive issue between here and a beta release
• Interest in layering OCFL over a Moab structure
• Julian to write up proposal and example

Action Items

• [] ...

Previous Action Items

• Neil to contact NDSA group regarding openness of preservation storage in the "Levels of Preservation"