...

1. Announcements:
   
   1. Good, well attended meeting in Switzerland. Interest in Fedora 6.
2. Value prop of using Valkyrie with/without Fedora
   1. Fedora 4 & 5 about standardization
      1. Some performance issues
   2. Fedora 6 adding more preservation minded features
      1. Transparent, human-readable filesystem
      2. Rebuildability from FS
   3. Why better to use Fedora over Preservica?
      1. Preservica not active storage
   4. Fedora offers standard middleware integrations: notifications, robust api
3. Definition of Fedora rebuild
   1. Ability to recreate everything needed to run Fedora based on the files on disk (Daniel's exact words should be added here)
4. Support unversioned content?
   1. Some use Fedora to author content over a period of time. They want to version when the content is ready and not have a version of every change.
      1. Clean version set
      2. Reduce bloat on disk
   2. Fedora currently offers the ability to mutate objects and create fixed versions. In OCFL, everything is immutable. How to reconcile this, and maintain Fedora functionality.
      1. Store everything in OCFL and make version logical structures on top of this
      2. Store only immutable content in OCFL
         1. Mutable content stored within OCFL's 'deposit' directory
         2. Fedora maintains mutable content
      3. Automatically periodically "flush" staged changes to OCFL
         1. OCFL versions would not be meaningful – requires logical versions
   3. There's a possibility that an object could never have a version. Is this okay?
   4. Auto-versioning should be toggle-able
   5. Islandora controls versioning – auto-versioning would be off by default
   6. Where does unversioned content live?
      1. OCFL 'deposit' directory is intended for short-lived version creation and not long-term storage
      2. OCFL 'deposit' directory space is out of spec and is up to the individual library to use it as it will
   7. Currently, you can delete version markers, but this is not possible if you store version markers in OCFL. Perhaps store version markers outside of OCFL?
      1. All changes stored in OCFL
      2. Fedora managed version file that maps OCFL versions to logical versions. This mapping is outside of the OCFL object.

Actions

•  Aaron Birkland  to look explore notion of OCFL client with database as authoritative metadata source + asynchronous writing of the inventory.json file
•  Peter Eichman   and maybe Ben Pennell to make recommendations re transaction side car specification.
•  Andrew Woods will look into java 11 transition

...