2023.12.07 Editors Meeting

Call-in

See invite

(* indicates the notetaker)

Create the OCFL Community Agenda 2023-12-13
Discussion about our own institution's use of OCFL
- Emory is working with Samvera to get Hyrax + Valkyrie out the door (i.e., addressing failing tests) so we can start to focus on Fedora 6 and Hyrax.
- Cornell is sunsetting their old instance of Fedora 3, hoping to move to OCFL by the end of next year.
- Harvard has an RFP out for replacing their preservation system, OCFL was mentioned in the RFP, decision in January.
Review Milestone for V2 (defer to next meeting)
- Are all the tickets that need to be in the milestone in the milestone
- Consider updating the tags for the tickets
Discussion on the final list of use-cases to be considered in v2.
- Use cases
  - Issue #46 Collapsing OCFL Object Versions
  - Issue #45 OCFL as a formal standard
  - Issue #42 Support physical file-level deletion
  - Issue #43 Defining a repository from peer storage roots
  - Issue #39 Distributed Storage of objects and components
  - Issue #44 OCFL Object Forking
  - Issue #33 Package per version storage
  - Issue #14 Flagging file loss/corruption
  - Issue #47 External identifiers in place of digests
  - Issue #48 Large inventory.json files
- Determine next steps for the final list of use-cases; Consider prioritizing use cases based on votes, maybe not all of them are necessary to focus on for version 2.
- Add to the agenda for next editors meeting.

Rosalyn to draft communication about the outcomes of the editors meeting; also create "voting" comment text
Neil to submit a PR to address #626
Andrew to follow up on #642
Zimeon to follow up on #632