2020.02.12 Community Meeting

Call-in Details

• 4pm BST / 11am EDT / 8am PDT
• https://lyrasis.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. Andrew Woods
2. Mike Lynch
3. Ben Cail
4. Steve Liu
5. Andrew Hankinson
6. Peter Winckles
7. David Wilcox
8. Rosalyn Metz

Agenda

1. Community updates (introductions, updates, implementations, plans, etc)
2. AWS and OCFL - Demo by @pwinckles
3. PASIG Madrid, May 19-21... who is attending?
4. Review of previous action items
5. Releasing 1.0
   1. Requirements to release 1.0
   2. Status of validators
   3. Open 1.0 Spec Issues
      • Path issues (issue-407, issue-411, issue-413)
6. Next community meeting: March 11, 2020 (second Wednesday of the month)

Notes

1. Introductions and Updates
   • University of Technology Sydney provided some details of their OCFL implementation
   • node.js with OCFL
   • data publications repo
   • GitHub
     • https://github.com/uts-eresearch/ocfl-js
     • https://github.com/UTS-eResearch/ocfl-nginx
   • Other resources
     • https://www.npmjs.com/package/ocfl
     • https://researchobject.github.io/ro-crate/
   • Observations having worked with the OCFL specification
     • Guidance on storage paths would be helpful, i.e. 'extensions'
   • Mike would be willing to demo on a future call
2. S3 demo
   • AWS S3 has issues with eventual consistency and locking
     • Therefore, ocfl-java uses a local RDBMS for locking
   • Current inventory is in DB
   • DB is auto-populated, lazy-loading
   • Tool (ocfl-java) still in-progress
     • Performance issues around large files yet to be fully resolved
     • Currently no caching, all retrievals coming from S3
3. PASIG
   • Anyone attending?
     • Andrew W
     • Rosy

Audio recording

• 2020-02-12.mp4

New Action Items

Previous Action Items

• Neil: Add language specific to extensions, specifically layouts and parameterization. ext-issue-2
• Who??: Add language to spec to warn users about problematic characters/sequences - issue-407