Page History

...

1. OCFL
   1. Points to clarify
      1. Mapping between Fedora resources and OCFL Storage Root and OCFL Objects
         1. How does Fedora persist to OCFL
         2. How does an existing OCFL hierarchy map into Fedora (no current use case provided)
      2. Cross-referencing between OCFL Objects (including linking to files within OCFL Objects)
      3. OCFL identifiers: Fedora URLs? internal URIs?
      4. Decoupling LDP containment from OCFL Object path?
      5. Creating OCFL versions
      6. External content handling
   2. OCFL Tooling: What is the MVP for initial testing?
      1. Mock OCFL for prototyping
      2. OCFL client API
   3. Performance considerations
      1. Many members scenario
2. Fedora 2019 architecture
   1. Refactoring away from ModeShape by implementing:
      
      1. fcrepo-kernel-modeshape (JCR interfaces)?
      2. fcrepo-kernel-api?

      3. fcrepo-http-api?

         Expand

         fcrepo-auth-common classes: 19 lines: 1697 total fcrepo-auth-webac classes: 14 lines: 4652 total fcrepo-event-serialization classes: 8 lines: 724 total fcrepo-http-api classes: 51 lines: 18908 total fcrepo-http-commons classes: 131 lines: 10162 total fcrepo-integration-ldp classes: 1 lines: 180 fcrepo-integration-rdf classes: 15 lines: 1293 total fcrepo-jms classes: 13 lines: 1090 total fcrepo-kernel-api classes: 90 lines: 5666 total fcrepo-kernel-modeshape classes: 174 lines: 27319 total fcrepo-webapp classes: 4 lines: 731 total fcrepo4 classes: 520 lines: 72422 total

         
         

   2. Layers of abstraction
      1. Persistence (OCFL client API <=> fcrepo-kernel-api)
      2. Query API
3. Migrations
   1. Fedora 3? → 4 → 5 → 6
   2. transparent migration for 5 → 6
   3. Retaining URIs
   4. Transforming F3 FOXML into OCFL (review migration-utils)
4. Persistent identifiers
5. API + Plus
   
   1. Object validation
   2. Configurable health checks
   3. Transactions?

...