2019.10.09 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. Joseph Rhoads
3. Steve Liu
4. Peter Winckles
5. Rosalyn Metz
6. Andrew Hankinson

Agenda

1. Community updates (introductions, updates, implementations, plans, etc)
2. Update on Editors F2F Meeting.
   • Issues closed at meeting
   • Extensions
     • ocfl_layout.json patterns?
   • Releasing 1.0
     • Open pull-requests:
       • Updates implementation notes #391
       • Fix digest choices in JSON Schema #395
     • Open 1.0 issues
     • Validator
3. Next community meeting: Nov 13, 2019 (second Wednesday of the month)

Notes

Any updates?

• Nope.

Editorial meeting review:

• 2 day event

• worked through open issues

• reviewed issues closed during the editorial meeting

• fleshed out the details of the 'extensions' functionality (aka RFCs)

  • community can collaborate around patterns of use
  • review of digest algorithms extensions
  • different OCFL filesystem layouts, e.g., pairtree or variants of pairtree.

• question: How do the changes to the OCFL spec about keys v. URIs affect the query parameters on the URL.

• action for the editors: consider how the extensions will work in light of the layout extension, wrt actionable machine code and extra parameters beyond just the key.

• roadmap to release:

  • overview of validator
  • 2 pull requests to review
  • new issues
    • deposit directory is outside of OCFL.

• link to remaining open issues

  • most are around the validator

• new logo!

• potential release before next community meeting.

• question about how to read OCFL objects, and if there are libraries around.

  • Java and Go libraries handle both read and write.
  • different environments will require different specifications and technologies, so the read and write requirements will be diverse.

Audio recording

• 2019-10-09.mp3

Action Items

Previous Action Items

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