Candidate Features for Fedora 4.x

Section

Column Advanced Tables - Table Plus enableSorting false   b3,4,5Batch batch      Policydriven StoragexlabelsSelf-healing Storagex Clustering Performance clustering  Alpha  Beta 4.0 Currently Supported Features Design Core Non-core Alpha Beta 4.0 Use Cases AuthN/Z design   x   b1,3,4,6,7,9 Expand title Authorization Use Cases Content by Label showLabels false max 20 showSpace false labels uc-authz Backup design x   b2,3 Expand title Backup Use Cases Content by Label showLabels false showSpace false labels uc-backup Clustering   x   x b5,6,10 Consistent deployment REST-API support against master node Content Modeling - Structural   x     b7,8 Expand title Content Modeling Use Cases Content by Label showLabels false showSpace false labels uc-content-modeling Managed External Datastreams     x   b2,4,6,7,8,10 Expand title External Storage Use Cases Content by Label showLabels false showSpace false labels uc-storage-external Store/Deliver Large Files design x     b2,4,6,7,8,10 Expand title Large Files Use Cases Content by Label showLabels false showSpace false labels uc-large-files Search design   x   b4,8,9 Expand title Search Use Cases Content by Label showLabels false showSpace false labels uc-search Transactions   x   x   Expand title Transactions Use Cases Content by Label showLabels false showSpace false labels uc-txns Triplestore design   x   b2,4 Expand title Triplestore Use Cases Content by Label showLabels false showSpace false labels uc-triplestore Versioning   x     b7,8,9 Expand title Versioning Use Cases Content by Label showLabels false showSpace false labels uc-versioning Non-Functional: Easy Deployment           Non-Functional: Performance - Single-node          Expand title Performance Use Cases Content by Label showLabels false showSpace false labels uc-performance                 Post-4.0 Priority 1 Features Design Core Non-core Alpha Beta  4.0 Use Cases 3 to 4 Upgrade design   x     Expand title F3 to F4 Upgrade Use Cases Content by Label showLabels false showSpace false labels uc-3to4-upgrade Asynchronous storage APIAudit Service design x        Expand title Async Storage Audit Service Use Cases Content by Label showLabels false showSpace false labels uc-audit Asynchronous storage -async  Batch Operations   API design x   x b9   Expand title Async Storage Use Cases Content by Label showLabels false showSpace false labels uc- Content Modeling - Services and Validation storage-async     Asynchronous storage Implementation    x     Expand title Content Modeling (extended) Asynchronous Storage Use Cases Content by Label showLabels false showSpace false labels uc-contentstorage-modeling-extasync LDP- Paging design   x   b1,2   Expand title Policy-Driven Storage Use Cases Content by Label showLabels false showSpace false uc-storage-policy Relationships API  x Web Access Control      x     API Partitioning     x                         Non-Functional: Performance - Clustered       Post-4.0 Priority 2 Features Design Core Non-core 4.0   Batch Operations   x     Expand title Batch Use Cases Content by Label showLabels false showSpace false labels uc- batch       CMIS     x     Post-4.0 Priority 2 Features Design Core Non-core Content Modeling - Services and Validation       Asynchronous storage Implementation   x         Expand title Asynchronous Storage Content Modeling (extended) Use Cases Content by Label showLabels false showSpace false labels uc-content-storage-async CMIS     x x       modeling-ext Disseminator-like Functionality     x       Expand title Object Services Use Cases Content by Label showLabels false showSpace false labels uc-object-services Human-readable Filesystem Storage     x   b9     Metrics x   x     Expand title Audit Use Cases Content by Label showLabels false showSpace false labels uc-audit Multi-tenancy   x         Expand title Multi-tenancy Use Cases Content by Label showLabels false showSpace false labels uc-multi-tenancy OAI-PMH design   x     ORCID Support     ORCID Supportx     Policy-driven Storage design x     Expand title Policy-Driven Storage Use Cases Content by Label showLabels false showSpace false labels uc-storage-policy Relationships API   x      WebDAV Self-healing Storage     x     WebDAV     x     Non-Functional: Performance - Clustered         Expand title Clustering Performance Use Cases Content by Label showLabels false showSpace false labels uc-clustering               Previously Un-prioritized Features Design Core Non-core Alpha Beta   4.0 Use Cases Admin UI     x     Expand title Admin UI Use Cases Content by Label showLabels false showSpace false labels uc-admin-ui Content API   x      Expand title Content API Use Cases Content by Label showLabels false showSpace false labels uc-content-api Identifiers   x       Expand title Identifier Use Cases Content by Label showLabels false showSpace false labels uc-identifiers Large-Scale Content   x       Expand title Large-Scale Content Use Cases Content by Label showLabels false showSpace false labels uc-scale-content

4.0 Beta (July - December 2013)

Beta must address fundamental set of requirements, including:

• Authorization
• Policy-driven storage and asynchronous storage systems
• Durability
• Performance for large scale ingest
• Auditing
• On-the-fly configuration

During this phase, the project team will also work closely with several early adopter institutions to ensure Fedora 4 supports their needs.

...

...

...

Select a platform for Fedora 4 development. 

Define Success Criteria for Fedora 4, particularly:

...

...

Develop and validate features around Fedora 3.x pain points, including:

• Horizontal scale-out

• High Availability

• Web-friendly APIs 

At the end of this phase, the project team should deliver an alpha-level prototype of Fedora 4. This prototype should demonstrate the core Fedora 4 principles, API design, and support for the hybrid use case. In addition, Hydra and Islandora should have functional builds that work against the Fedora 4 API. 

At Open Repositories 2013, the software should be in a state that external developers can successfully install the software and provide meaningful feedback about additional user stories and technical requirements for the next phase of the project.

Fedora Futures Requirements Gathering (through December 2012)

...

...

...

Initial use cases and user stories that we want to ensure Fedora 4 will be prepared to address were collected at Use Cases. The Phase I team synthesized the collected use cases into a series of user stories for alpha development.

• Hybrid Use Case
  • Policy-controlled storage
  • Repository supports Amazon Glacier, or other asynchronous storage services
  • Use Case: Storing heterogeneous research data
  • Mass Object Creation
  • Scale for High Volume Read Access

...