Candidate Features for Fedora 4.x

Currently Supported Features	Design	Core	Non-core	4.0	Use Cases
AuthN/Z	design		x		Page: Hydra Authorization Use Case Page: Yale University - Fedora managing access conditions Page: University of Virginia - Repository generated-mediated derivatives
Backup	design	x			Page: Backups / Disaster Recovery
Clustering		x			Consistent deployment REST-API support against master node
Content Modeling - Structural		x			Content by label There is no content with the specified labels
Managed External Datastreams			x		Page: Ingesting large files into the repository
Store/Deliver Large Files	design	x			Page: Ingesting large files into the repository Page: Research Data
Search	design		x		Page: University of Virginia - Applications can be easily built to work against fedora
Transactions		x			Page: Islandora CLAW Transaction Use Case Page: University of Virginia - Applications can be easily built to work against fedora
Triplestore	design		x		Page: Using the resources of the Semantic Web to describe repository contents Page: University of Virginia - Live querying of object graph
Versioning		x			Page: Structure - Automated Retention of All changes to Items Page: Structure - Manual Edit of Existing Items Page: Structure - Manual Creation of "New Editions" of an Item Page: Structure - Generated provenance for all added bitstreams
Non-Functional: Easy Deployment
Non-Functional: Performance - Single-node					Page: Improve Performance Page: University of North Carolina at Chapel Hill - High Volume of Concurrent Ingests

Post-4.0 Priority 1 Features	Design	Core	Non-core	4.0	Use Cases
3 to 4 Upgrade	design		x		Content by label There is no content with the specified labels
Audit Service	design	x			Page: Reporting Functionality Page: University of New South Wales - Viewing-exporting usage statistics about fedora records Page: More Functional AUDIT Datastream
Asynchronous storage API	design	x			Page: Support for Hierarchical Storage Management-like systems Page: Scalability for Asynchronous Ingest, Access and Audit Page: Leverage Cloud Storage Page: Repository supports Amazon Glacier, or other asynchronous storage services Page: Hybrid Use Case
Asynchronous storage Implementation		x			Page: Support for Hierarchical Storage Management-like systems Page: Scalability for Asynchronous Ingest, Access and Audit Page: Leverage Cloud Storage Page: Repository supports Amazon Glacier, or other asynchronous storage services Page: Hybrid Use Case
LDP-Paging		x
Web Access Control			x
API Partitioning		x

Post-4.0 Priority 2 Features	Design	Core	Non-core	4.0
Batch Operations		x			Page: Hybrid Use Case (Metadata Services) Page: Yale University - Fedora managing access conditions
CMIS			x
Content Modeling - Services and Validation					Page: Use case: transform application workflow Page: Art Institute of Chicago Use Case - Structural Validation Page: Modeling content in concert with the wider world Page: Art Institute of Chicago Use Case - Structural Validation - Properties
Disseminator-like Functionality			x		Page: Objects can be associated with a descriptive metadata service Page: University of Virginia - Repository-level metadata transformations-mapping Page: University of Virginia - Repository generated-mediated derivatives
Human-readable Filesystem Storage			x
Metrics		x			Page: Reporting Functionality Page: University of New South Wales - Viewing-exporting usage statistics about fedora records Page: More Functional AUDIT Datastream
Multi-tenancy		x			Page: Multi-tenancy Single Fedora Instance
OAI-PMH	design		x
ORCID Support			x
Policy-driven Storage	design	x			Page: Policy-controlled storage Page: Hybrid Use Case
Relationships API		x
Self-healing Storage			x
WebDAV			x
Non-Functional: Performance - Clustered					Page: University of North Carolina at Chapel Hill - High Volume of Concurrent Ingests Page: Mass Object Creation Page: Repository subsystems can scale horizontally Page: Scale for High Volume Read Access

Previously Un-prioritized Features	Design	Core	Non-core	4.0	Use Cases
Admin UI			x		Page: Tufts University - Reasonable curators administrative interface
Content API		x			Page: Yale University - Fedora managing access conditions Page: University of Virginia - Applications can be easily built to work against fedora
Identifiers		x			Page: Hybrid Use Case (Metadata Services) Page: UUID's: Object Mobility and Merging Stores
Large-Scale Content		x			Page: Archive of digitised newspapers

Integrations	Core	Non-core	Use Cases
Hydra Integration		x	Page: Hydra Authorization Use Case
Islandora Integration		x

Page tree

Roadmap

Candidate Features for Fedora 4.x