Call-in

https://duraspace.zoom.us/my/vivo1

Attendees

• Andrew Woods (DuraSpace) *
• Julian Morley (Stanford)
• Rosy Metz (Emory)
• Simeon Warner (Cornell)
• Andrew Hankinson (Bodleian Libraries)
• Neil Jefferies (Bodleian Libraries)

(* indicates the notetaker)

Agenda

1. Review of action items
2. Re-opening issues that have been closed due to being out-of-scope for v1.0
3. Working towards a 1.0 release (open issues )

Notes

Review action items

1. Simeon to review previously closed use cases
2. Rosy (Wed/Thurs Stanford agenda):
   • Mon/Tues: Preservation API
   • Wed/Thurs: OCFL Editors
   • Cleaning up v1 - plan to release v1 after meeting?
     • Need a validator
       • Starting points:
         • https://github.com/zimeon/ocfl-py/blob/master/ocfl-validate.py
         • https://github.com/ahankinson/ocfl-old/blob/master/libocfl/validate.go
       • How to support multiple languages?
         • Potentially write in GoLang (compiles static binaries, async processing)
       • Process: validator runs over an OCFL Storage Root
       • Hire out developer for validator?
     • Test suite and fixture objects
       • Fixtures to validate the validator
       • Rules for all "MUST"s, "SHOULD"s, etc
       • ACTION: A.H. to extract out the "MUST"s from spec into validation rules
         • https://github.com/OCFL/spec/wiki/OCFL-Validators
   • Focus on v2
   • Go through use cases that have been re-opened
3. Julian: not present
4. Neil: action still outstanding
   • PR to be less prescriptive

Review issues

1. Add note about empty directories in object stores - 322
   • Addressed by .keep suggestion?
   • https://ocfl.io/0.3/implementation-notes/#empty-directories
   • closed
2. Advice on ocfl_layout.json contents - 351
   • abirkland and tomwrobel to create wiki page
   • Wiki page to be a light-weight registry of community-sourced layouts
3. Consider reference implementation documentation - 332
   • Should emerge from community experience
   • Removed from 1.0 milestone, removed "editorial" label
4. Clarify how to extend algorithm choices - 292
   • Removed from 1.0 milestone, added "deferred" label

Misc

1. Review "deferred" label
   • Change name to "proposed-v2"?
2. Specification of validator error codes and messages - 144
   • Simeon to close

Actions

• Andrew H. to extract out the "MUST"s from spec into validation rules

Previous Actions

• Zimeon: troll through use cases and find closed ones that should have been deferred.
• Rosalyn: start an agenda for the face to face meeting
• Julian: take our thoughts back to Stanford for discussion for digital preservation meeting
• Neil: clean up PR #362 based on the conversation
• Julian: consider what a guidance document of the OCFL stack (on the wiki) would look like