Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. What is "auto-versioning"?
    1. On close of Fedora transaction an OCFL version is created – this happens regardless of whether or not auto-versioning is enabled
    2. Auto-versioning on: Fedora tag automatically created for every OCFL version
    3. Auto-versioning off: No Fedora tag created
    4. Absent a tag file that describes Fedora versions, OCFL versions are exposed
    5. Counter-prop: No auto-versioning. All Fedora versions must be manual.
    6. Cannot support tagging old OCFL versions with Fedora versions
    7. Concerns about exposing OCFL versions through Fedora APIs – don't want Fedora to be tied to OCFL
    8. How does this work when importing from old versions of Fedora?
      1. Fedora 4 & 5: can the versions be replayed?
      2. Fedora 4 → 5: Export 4, run transform, Import 5
      3. Fedora 5 → 6: Export 5, run transform that produces OCFL, point Fedora 6 to OCFL
      4. Fedora 3 → 6: Conversion of Fedora 3 files on disk to OCFL, point Fedora 6 to OCFL
  2. Transactions
    1. Transactions at the object level are do-able, but across multiple objects is trickier. May not need to implement multi object transactions.
    2. Bound to an archival group. Don't allow multi object transactions across different archival groups.
    3. Transaction endpoint exposed for every OCFL object
    4. Cannot make changes to objects out of scope of original transaction.
    5. How do you open a transaction for a new OCFL object?
      1. Create an empty object, open a transaction, update object, close transaction – would not remove the empty object on rollback
    6. Why limit transactions to just one object?
      1. Multi-object OCFL transactions are hard to implement
    7. Something in the import/export group for mapping to archival groups

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

...