Versions Compared

Key

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

...

  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 (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
        1. fcrepo-auth-common
          1. classes: 19
          2. lines: 1697 total
        2. fcrepo-auth-webac
          1. classes: 14
          2. lines: 4652 total
        3. fcrepo-event-serialization
          1. classes: 8
          2. lines: 724 total
        4. fcrepo-http-api
          1. classes: 51
          2. lines: 18908 total
        5. fcrepo-http-commons
          1. classes: 131
          2. lines: 10162 total
        6. fcrepo-integration-ldp
          1. classes: 1
          2. lines: 180
        7. fcrepo-integration-rdf
          1. classes: 15
          2. lines: 1293 total
        8. fcrepo-jms
          1. classes: 13
          2. lines: 1090 total
        9. fcrepo-kernel-api
          1. classes: 90
          2. lines: 5666 total
        10. fcrepo-kernel-modeshape
          1. classes: 174
          2. lines: 27319 total
        11. fcrepo-webapp
          1. classes: 4
          2. lines: 731 total
        12. fcrepo4
          1. classes: 520
          2. 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. Retaining URIs
    3. Transforming F3 FOXML into OCFL (review migration-utils)
    Identifiers
    1. Decoupling LDP containment from URL?
  4. Persistent identifiers
  5. API + Plus
    1. Object validation
    2. Configurable health checks
    3. Transactions?

Development topics

  1. Limiting Fedora dependency on Modeshape to fcrepo-kernel-modeshape
  2. Re-implementing Fedora persistence for OCFL
    1. fcrepo-kernel-api?
      1. Fedora dependencies on JCR and Modeshape
    2. fcrepo-http-api?
  3. Mocking OCFL client
  4. OCFL Go library

Agenda

Call-in: https://duraspace.zoom.us/my/fedora

Tuesday - 2019-02-26

TimeTopic


Breakfast

9am

...

Stand-up

  • Context setting
  • Objectives for the week

...



9:30amAgenda creation from above "Topics"





4pmDaily debrief


Dinner

7pmImplementation


Wednesday - 2019-02-27

TimeTopic


Breakfast

9am

...

Stand-up







4pm

...

Daily debrief


Dinner

7pm


Thursday - 2019-02-28

TimeTopic


Breakfast

9am

...

Stand-up







4pm

...

Daily debrief


Dinner

7pm