...
- Bulk upload
- Structured ingest: images/metadata, via filesystem?
- Dynamic scalability (storage and response time)
- Cloud storage
- Basic query
- Backup / restore
- disaster recovery
- Multi-tenancy
- Binary fixity
- storing fixity
- comparing stored with computed
- Object validation
- fixity of children, based on type
- log results
- Auto health checks
- Index of all resources
- Configurable frequency
- report/log
- Migration
- URIs must remain unchanged from 4 → 5 → 6
- Atomic version of multiple requests
- Version on-demand?
- Transactions?
- Durable identifiers
- Non-URL IDs?
- ARKs?, DOIs
- IIIF integration
Topics
- OCFL
- Points to clarify
- Mapping between Fedora resources and OCFL Storage Root and OCFL Objects
- How does Fedora persist to OCFL
- How does an existing OCFL hierarchy map into Fedora
- Cross-referencing between OCFL Objects (including linking to files withing OCFL Objects)
- Creating OCFL versions
- External content handling
- Mapping between Fedora resources and OCFL Storage Root and OCFL Objects
- OCFL Tooling: What is the MVP for initial testing?
- Mock OCFL for prototyping
- OCFL client API
- Performance considerations
- Many members scenario
- Points to clarify
- Fedora 2019 architecture
- Refactoring away from fcrepo-kernel-modeshape
- Query API
- Migrations
- Fedora 3? → 4 → 5 → 6
- Retaining URIs
- Transforming F3 FOXML into OCFL (review migration-utils)
- Identifiers
- Decoupling LDP containment from URL?
- Persistent identifiers
- API + Plus
- Object validation
- Configurable health checks
- Transactions?
...