2025.01.16 Community Meeting

Call-in Details

• Thursday, January 16th, 12pm EDT / 9am PDT / 5pm GMT / Friday, January 17th, 4am AEDT (Convert to your time zone)
• Zoom Link: https://emory.zoom.us/j/98034472848?pwd=U6eMrOyE58EecHBdTUoufGAahDqT3q.1&from=addon

Attendees

1. Neil Jefferies (OPF)
2. Andrew Woods (Harvard)
3. Jurgen Enge (Basel)
4. Arran Griffith (Fedora)
5. Seth Shaw (Arizona)
6. Dan Field (Fedora)
7. Becky Andresen (Wisconsin-Madison)
8. Jaime Carrascal (Ludwig-Maxamillion, Munich)
9. Alex (unaffiliated)
10. Leona Fearon (NL Ireland)

Agenda

1. Welcome and Introductions

   • Seth - keeping up to date because they don't have a DP approach currently but have an interest in OCFL (also Islandora)
   • Jaime - Fedora users
   • Alex - archivist with a music library
   • Leona - NLI are looking at a new DP system so interested in learning about OCFL

2. Version 2 Discussion

   • Requirements for release of version two.

     Before releasing OCFL Version 2, we will meet the following criteria:
     
     Tool Implementation: 
        At least two tools (validators, libraries, etc.) must implement three of the four new features, 
        ensuring every feature is implemented at least once within tools.
     Updated Fixtures and Validators: 
        All fixtures, validators, and error messages must address the new features in the specification.
     Community Feedback: 
        We will give each alpha and beta release phase at least six months to gather and incorporate 
        community feedback. For comparison, OCFL 1.0's alpha (0.1) and beta (0.3) releases lasted approximately nine 
        and thirteen months, respectively.
     

   • Features:
     1. Flagging Features at the Storage Root
        • Application Profiles #50
     2. Tombstones
        • Flagging file loss/corruption #14
        • Support physical file-level deletion #42
        • Collapsing OCFL Object Versions #46
     3. Package Per Version
        • Package per version storage #33
     4. Content Linking (Object Forking)
        • OCFL Object Forking #44

• Some discussion of what implementation requirements meant - in practice an implementation and a validation would suffice.
• Maybe we should poll on the order in which we work on features - to reflect community priorities
  • JE keen on Package per version - which makes sense since Tombstoning will be dependent on it
  • Feature Flagging will also be important for partial implementations
• Some discussion of pain points - excessive versioning generates a lot of use cases
• OCFL Java is critical but dev has moved on - Fedora considering adoption
  • Arran to schedule an OCFL Java implementers meeting
• What is an OCFL Implementation - there is nothing "official". Maybe there should be.

Recording

• Recording

New Action Items

• your action item here

Previous Action Items

• your action item here