2019.08.14 Community Meeting

Call-in Details

• 11am ET
• 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. Andrew Hankinson
3. Aaron Birkland
4. Ben Cail
5. Julian Morley
6. Neil Jefferies
7. Peter Winckles
8. Steve Liu

Agenda

1. Community updates (introductions, updates, implementations, plans, etc)
2. Feedback on Beta Release
3. 1.0 release criteria
   • Open issues
   • Validator
   • Test fixtures
   • Institutional backing
4. Unprovisioned issue
5. Potential RFC approach
   • ..As exemplified by recommendations towards ocfl_layout.json issue-351
6. Upcoming Editorial face-to-face meeting
7. Next meeting: Wednesday, Sept 11th @11am ET

Notes

Open discussion about local work

Peter W. -- Java implementation of OCFL spec; basic implementation of writing to local filesystem. -- Observations:

1. Clarify the blake2b algorithm
2. Addressing the file layout within the file root; will require manual configuration
3. Additional fixity information makes it cumbersome to use; hard to map the fixity information back to the files due to the need to flip the keys and values.

Andrew W. -- Fedora; next major release is being designed, sprints are coming. Parallel effort for moving Fedora 3 to Fedora 6.

Migration-utils project now set up to write OCFL content directly to disk; would like to compare interactions between different libraries.

Beta Release Feedback

No feedback.

1.0 Release Criteria

Not much work on Test Fixtures yet. Looking pretty good for institutional backing.

Validator page looks good ; question about whether the list will grow. Validator and Test Suite are probably the biggest blocker to 1.0

Open issues:

• Neil has an open pull request to address #348
• Will simplify the prescriptive nature of the open PR.
• Hex stickers: Maybe?

Decided: blake2b-512 is an acceptable clarification

• Peter W. to create pull-request

RFC proposal (Aaron Birkland)

URIs that can be used and cited.

• can be used to solidify community recommendations
• can be a formalized externalization of parts of the spec

Reservations around adding an ocfl-rfc repo to the OCFL GitHub org:

• What is the process for reviewing / maintaining?
• Who will have oversight / responsibility?

What's the next step for the proposal?

• Aaron B. to open an issue on the OCFL spec proposing the RFC process.

Action: Andrew W. will create a bare RFC repo after checking with the editors.

Editors Meeting in Stanford 2-3 October.

Next meeting: 11 September

Audio recording

• 2019-08-14.mp3

Action Items

• Andrew Woods to create Bare RFC Repo after checking about process w/ editors
• Aaron Birkland will create an issue in the spec repo for the RFC process
• Peter W. will submit a pull request with the proposed change for blake2b-512.

Previous Action Items

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