Use Cases Wanted! The Fedora community is encouraged to add use cases in the format detailed below by creating a new sub-page from this wiki page. In order to ensure that the community's needs are reflected in the software, this input is critical.
Also, please review the existing use cases here and comment on or "like" ones as you see fit.
Use case structure (from Wikipedia) : Title (Goal) Primary Actor Scope Level Story (A paragraph or two describing what happens)
Fedora6 Use Cases
Title Creator Modified Update RdfSources without worrying about server managed triples Jared Whiklo Apr 29, 2019 Johns Hopkins University Use cases Hanh Vu Feb 22, 2019 2 Restore the exact state of a resource Ben Pennell Feb 13, 2019 Change the containment of a resource Ben Pennell Feb 13, 2019 Durable identifiers for resources Ben Pennell Feb 13, 2019 1 Efficiently traverse repository hierarchy Ben Pennell Feb 13, 2019 Support containers with millions of children Ben Pennell Feb 13, 2019 Create version of a resource after a complex update Ben Pennell Feb 13, 2019 Migrate to new versions of fcrepo without needing to relocate or reingest binaries Ben Pennell Feb 13, 2019 Proactive repository health check Doron Shalvi Feb 12, 2019 Migrate content from earlier versions of Fedora to Fedora 6 Doron Shalvi Feb 12, 2019 Object validation Doron Shalvi Feb 12, 2019 File fixity Doron Shalvi Feb 12, 2019 1 Fedora 6 Use Case Example Robin Lindley Ruggaber Feb 11, 2019 University of Virginia - Live querying of object graph Andrew Woods Apr 09, 2014 4 University of Virginia - Applications can be easily built to work against fedora Andrew Woods Mar 26, 2014 2 1 University of North Carolina at Chapel Hill - High Volume of Concurrent Ingests Greg Jansen Mar 07, 2014 2 1 Archive of digitised newspapers Kåre Fiedler Christiansen Jan 03, 2014 3 Improve Performance Jonathan Green Dec 10, 2013 1 Ingesting large files into the repository Chris Beer Jan 08, 2013 4 Multi-tenancy Single Fedora Instance Jonathan Green Jan 08, 2013 2 1 Repository subsystems can scale horizontally Benjamin Armintor Jan 08, 2013 4 Scale for High Volume Read Access Edwin Shin Dec 12, 2012 Mass Object Creation Edwin Shin Dec 12, 2012 Leverage Cloud Storage Robin Lindley Ruggaber Oct 25, 2012 1 Scalability for Asynchronous Ingest, Access and Audit Robin Lindley Ruggaber Oct 25, 2012 Research Data Robin Lindley Ruggaber Oct 25, 2012 2 Backups / Disaster Recovery Jonathan Green Oct 25, 2012 4
Legacy Use Cases
Title Creator Modified Tufts University - Reasonable curators administrative interface Andrew Woods Feb 15, 2019 3 1 Cache Warming Ralf Claussnitzer Feb 19, 2015 Multiple Metadata Formats Ralf Claussnitzer Feb 19, 2015 HTTP Authentication Ralf Claussnitzer Feb 19, 2015 Dynamic Sets Ralf Claussnitzer Feb 19, 2015 Deleted Record Policy Ralf Claussnitzer Feb 19, 2015 1 Hydra Authorization Use Case Andrew Woods May 28, 2014 4 Yale University - Fedora managing access conditions Andrew Woods Mar 26, 2014 4 University of Virginia - Repository generated-mediated derivatives Andrew Woods Jan 06, 2014 2 University of Virginia - Repository-level metadata transformations-mapping Andrew Woods Jan 06, 2014 University of New South Wales - Viewing-exporting usage statistics about fedora records Andrew Woods Jan 06, 2014 Reporting Functionality Unknown User (escowles@ucsd.edu) Apr 25, 2013 Hybrid Use Case (Metadata Services) Benjamin Armintor Jan 08, 2013 4 Hybrid Use Case Edwin Shin Jan 08, 2013 5 Objects can be associated with a descriptive metadata service Benjamin Armintor Jan 08, 2013 1 UUID's: Object Mobility and Merging Stores Neil Jefferies Jan 08, 2013 1 Policy-controlled storage A. Soroka Jan 08, 2013 2 1 Using the resources of the Semantic Web to describe repository contents Benjamin Armintor Jan 08, 2013 4 More Functional AUDIT Datastream Jonathan Green Oct 25, 2012 2 1
Completed Use Cases
Title Creator Modified University of Pennsylvania - Expose content through Fedora, offloading serving of binary content to a dedicated service Katherine Lynch Jun 09, 2016 2 1 Objects can be associated with a PREMIS event service Benjamin Armintor Apr 22, 2014 12 Art Institute of Chicago Use Case - Object Services Andrew Woods Jan 23, 2014 Art Institute of Chicago Use Case - Content Model API Andrew Woods Jan 17, 2014 6 Art Institute of Chicago Use Case - Access Policies via Models Andrew Woods Jan 17, 2014 4 Yale University - Applications use API for updating access conditions stored in Fedora Andrew Woods Jan 06, 2014 3 Yale University - Programmers use API for access condition support in external systems Andrew Woods Jan 06, 2014 4 University of Wisconsin - Madison - Obtain list of objects that contain a given datastream Andrew Woods Jan 06, 2014 3 University of Wisconsin - Madison - Obtain filtered list of objects Andrew Woods Jan 06, 2014 5 University of Wisconsin - Madison - External Authentication and Authorization Andrew Woods Jan 06, 2014 9 University of North Carolina at Chapel Hill - Access Contingent Upon Workflow Metadata Andrew Woods Jan 06, 2014 3 University of North Carolina at Chapel Hill - Setting Individual Permissions Andrew Woods Jan 06, 2014 3 University of North Carolina at Chapel Hill - Unified Authorization Andrew Woods Jan 06, 2014 3 University of New South Wales - Updating-Editing multiple fedora records Andrew Woods Jan 06, 2014 2 University of New South Wales - Generate final data output for fedora storage in Cool URL format Andrew Woods Jan 06, 2014 1 University of New South Wales - Versioning interim data and accessible through Cool URL format Andrew Woods Jan 06, 2014 2 University of New South Wales - Deposit interim data in RDF format and search using SPAQRL Andrew Woods Jan 06, 2014 2 University of New South Wales - Data management plan ingest and storage Andrew Woods Jan 06, 2014 1 Tufts University - Streamlined and secure way of distinguishing open from closed data Andrew Woods Jan 06, 2014 4 Indiana University Use Case - Dissemination of large audio-video files Andrew Woods Jan 06, 2014 1 Indiana University Use Case - Support Flexible data model change Andrew Woods Jan 06, 2014 1 Indiana University Use Case - Easy traversal against the triplestore Andrew Woods Jan 06, 2014 2 University of York Use Case - Access Control Tom Cramer Dec 17, 2013 4 Test Coverage Jonathan Green Jun 13, 2013 2 Dynamic metadata : Fedora as a Semantic Object Store Wolfram Horstmann Jan 08, 2013 12 1 Use case [stub]: External triple store spanning several repositories Wolfram Horstmann Jan 08, 2013 4 Use case [stub]: Research data packages in multiple stores Wolfram Horstmann Jan 08, 2013 1 Repository is a continuous graph Thorny Staples Jan 08, 2013 3 An archaeologist at the Smithsonian collaborating with a biologist at another research institution Thorny Staples Jan 08, 2013 2 Researchers control the policies on their own objects Thorny Staples Jan 08, 2013 1 Use Case: Updating metadata fields of multiple objects Matthias Razum Jan 08, 2013 2 1 HTTP 1.1 Caching Support Jonathan Green Oct 25, 2012 4 Security Jonathan Green Oct 25, 2012 4 Use Case: Distributed authentication and authorization Matthias Razum Oct 24, 2012 3 Use Case: Storing heterogeneous research data Matthias Razum Oct 24, 2012 2
4 Comments
A. Soroka
Ben-- under externalizable IDs, would you buy this:
Fedora should be able to produce and manage externally-meaningful IDs, without respect to its internal workings...
?
A. Soroka
Ben-- under "Flexible types of stored entities", are you contemplating a meta-contract that would be exposed to the community and its developers for people to fulfill in order to create new providers for these kinds of entities? E.g. someone (J. Random Fedora Institution) who wants to add a "PREMIS module" would be able to fulfill a certain meta-contract with the repository architecture and interfaces and guarantee themselves of good operation? Or is this about work that we might do near-term in the core of the project to actually produce some of these new kinds of providers?
Benjamin Armintor
I'll respond ASAP in the relevant page discussions. Thanks, Adam!
Deborah Kaplan
1
Is there going to be some effort to distinguish in this list between use cases and features/requirements? It's making it kind of hard to read the page.