You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Time/Place

Time: 11:00am Eastern Time (US)

Please see calendar invite for Zoom link.

Attendees

  1. Andrew Woods
  2. David Wilcox
  3. Danny Bernstein
  4. Thomas Bernhart
  5. Jon Dunn
  6. Raman Ganguly
  7. Scott Prater
  8. Ben Pennell
  9. Peter Winckles
  10. Jennifer Gilbert
  11. Doron Shalvi
  12. Jared Whiklo
  13. Robin Lindley Ruggaber

Agenda

Open development questions

  1. To what extent should Fedora 6 support vanilla OCFL? i.e:
    1. Do we value Fedora being able to run on top of vanilla OCFL? - in a read-only fashion? in a read/write fashion?
    2. Do we value a post-Fedora OCFL that is not peppered with Fedora-specific system metadata?

Use cases

  1. As a systems integrator, I would like a simple GET/PUT HTTP server over OCFL
  2. As a Fedora 3 repository manager, I would like to export my content as vanilla OCFL
  3. As a repository manager, I would like to bring my vanilla OCFL into Fedora
  4. As a digital preservationist, I would like to keep the OCFL created by Fedora but stop using Fedora

Context

  1. In order for Fedora to manage repository content, Fedora-specific system metadata is required (caveat for vanilla OCFL)
  2. Although it is meaningful and self-describing, there is some stakeholder concern around including content in an OCFL object that is in addition to what the user provided
  3. Currently, Fedora segregates this system metadata into its own directory (".fcrepo/") within the OCFL object
    1. What system metadata are we exactly talking about?

      # all Fedora resources have:
      "parent":"info:fedora/new",
      "id":"info:fedora/new/child",
      "interactionModel":"http://www.w3.org/ns/ldp#BasicContainer",
      "createdDate":"2020-04-21T16:52:42.757566Z",
      "lastModifiedDate":"2020-04-21T16:52:42.757566Z",
      "createdBy":"",
      "createdDate":"",
      "stateToken":"A1FAFA3B80B37AD8C1B0CC519ABD30A2",
      "archivalGroup":false,
      "objectRoot":true
      
      # binaries also have:
      ...
      "filename":"notes.txt",
      "mimeType":"text/plain",
      "contentSize":282,
      "digests":[],
      ...
      
      # external content also has:
      ...
      "externalUrl":,
      "externalHandling":
      ...
    2. Structure and location of Fedora system metadata in an OCFL object

      test-object
          ├── 0=ocfl_object_1.0
          ├── inventory.json
          ├── inventory.json.sha512
          ├── v1
          │   ├── inventory.json
          │   ├── inventory.json.sha512
          │   └── content
          │       ├── .fcrepo
          │       │   └── test-object.json
          │       └── test-object.nt
          ├── v2
          │   ├── inventory.json
          │   ├── inventory.json.sha512
          │   └── content
          │       └── .fcrepo
          │           ├── empty-txt-description.json
          │           └── empty-txt.json
          ├── v3
          │   ├── inventory.json
          │   ├── inventory.json.sha512
          │   └── content
          │       ├── .fcrepo
          │       │   ├── bar.xml-description.json
          │       │   └── bar.xml.json
          │       └── foo
          │           └── bar.xml
          └── v4
              ├── inventory.json
              ├── inventory.json.sha512
              └── content
                  ├── .fcrepo
                  │   ├── image.tiff-description.json
                  │   └── image.tiff.json
                  └── image.tiff
      
      

Notes



Action Items 

  • Type your task here, using "@" to assign to a user and "//" to select a due date
  • No labels