Versions Compared

Old Version 4

changes.mady.by.user Bethany Seeger

Saved on

compared with

New Version 5

changes.mady.by.user Danny Bernstein

Saved on

Key

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

...

  1. Driving principles:
    1. Minimizing change to the user via the API
    2. OCFL-isms not bleeding into Fedora API
    3. Rebuildability
    4. Compliance with OCFL
    5. Retain URLs of migrated Fedora resources
    6. Performance
    7. Reducing complexity of implementation

Fedora - OCFL Mapping

Opt-in model

  1. Fedora resources may be created with an optional "archive" interaction model provided via headers.  

  2. New resources created via POST or PUT to the archive will be LDP contained by the archive and will be stored within the OCFL object representing that archive.

  3. If a resource is created without the "archive" model, new resources created via POST or PUT will be LDP contained by the archive, but will be stored as separate OCFL objects.

Notes/Implications

  1. At creation time, you establish what you want and then stay in that model. Changing the model would require additional migration tooling.
  2. Requires 3 interaction approaches: atom (implicit), archive, part (implicit)


Fixity service


Transaction service

...