Page History

...

1. Bulk upload
   • Structured ingest: images/metadata, via filesystem?
2. Dynamic scalability (storage and response time)
3. Cloud storage
4. Basic query
5. Backup / restore
   • disaster recovery
6. Multi-tenancy
7. Binary fixity
   • storing fixity
   • comparing stored with computed
8. Object validation
   • fixity of children, based on type
   • log results
9. Auto health checks
   • Index of all resources
   • Configurable frequency
   • report/log
10. Migration
    1. URIs must remain unchanged from 4 → 5 → 6
11. Atomic version of multiple requests
    • Version on-demand?
    • Transactions?
12. Durable identifiers
    • Non-URL IDs?
    • ARKs?, DOIs
13. IIIF integration

Topics

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
      2. Cross-referencing between OCFL Objects (including linking to files withing OCFL Objects)
      3. Creating OCFL versions
      4. 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 fcrepo-kernel-modeshape
   2. Query API
3. Migrations
   1. Fedora 3? → 4 → 5 → 6
   2. Retaining URIs
   3. Transforming F3 FOXML into OCFL (review migration-utils)
4. Identifiers
   1. Decoupling LDP containment from URL?
   2. Persistent identifiers
5. API + Plus
   1. Object validation
   2. Configurable health checks
   3. Transactions?

...