Page tree
Skip to end of metadata
Go to start of metadata

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) 

2019 Use Cases

 Fedora6 Use Cases
TitleCreatorModified
Update RdfSources without worrying about server managed triplesJared WhikloApr 29, 2019
Johns Hopkins University Use casesHanh VuFeb 22, 2019
Restore the exact state of a resourceBen PennellFeb 13, 2019
Change the containment of a resourceBen PennellFeb 13, 2019
Durable identifiers for resourcesBen PennellFeb 13, 2019
Efficiently traverse repository hierarchyBen PennellFeb 13, 2019
Support containers with millions of childrenBen PennellFeb 13, 2019
Create version of a resource after a complex updateBen PennellFeb 13, 2019
Migrate to new versions of fcrepo without needing to relocate or reingest binariesBen PennellFeb 13, 2019
Proactive repository health checkDoron ShalviFeb 12, 2019
Migrate content from earlier versions of Fedora to Fedora 6Doron ShalviFeb 12, 2019
Object validationDoron ShalviFeb 12, 2019
File fixityDoron ShalviFeb 12, 2019
Fedora 6 Use Case ExampleRobin Lindley RuggaberFeb 11, 2019
University of Virginia - Live querying of object graphAndrew WoodsApr 09, 2014
University of Virginia - Applications can be easily built to work against fedoraAndrew WoodsMar 26, 2014
University of North Carolina at Chapel Hill - High Volume of Concurrent IngestsGreg JansenMar 07, 2014
Archive of digitised newspapersKåre Fiedler ChristiansenJan 03, 2014
Improve PerformanceJonathan GreenDec 10, 2013
Ingesting large files into the repositoryChris BeerJan 08, 2013
Multi-tenancy Single Fedora InstanceJonathan GreenJan 08, 2013
Repository subsystems can scale horizontallyBenjamin ArmintorJan 08, 2013
Scale for High Volume Read AccessEdwin ShinDec 12, 2012
Mass Object CreationEdwin ShinDec 12, 2012
Leverage Cloud StorageRobin Lindley RuggaberOct 25, 2012
Scalability for Asynchronous Ingest, Access and AuditRobin Lindley RuggaberOct 25, 2012
Research DataRobin Lindley RuggaberOct 25, 2012
Backups / Disaster RecoveryJonathan GreenOct 25, 2012


2012-2016 Use Cases

 Completed Use Cases
TitleCreatorModified
University of Pennsylvania - Expose content through Fedora, offloading serving of binary content to a dedicated serviceKatherine LynchJun 09, 2016
Objects can be associated with a PREMIS event serviceBenjamin ArmintorApr 22, 2014
Art Institute of Chicago Use Case - Object ServicesAndrew WoodsJan 23, 2014
Art Institute of Chicago Use Case - Content Model APIAndrew WoodsJan 17, 2014
Art Institute of Chicago Use Case - Access Policies via ModelsAndrew WoodsJan 17, 2014
Yale University - Applications use API for updating access conditions stored in FedoraAndrew WoodsJan 06, 2014
Yale University - Programmers use API for access condition support in external systemsAndrew WoodsJan 06, 2014
University of Wisconsin - Madison - Obtain list of objects that contain a given datastreamAndrew WoodsJan 06, 2014
University of Wisconsin - Madison - Obtain filtered list of objectsAndrew WoodsJan 06, 2014
University of Wisconsin - Madison - External Authentication and AuthorizationAndrew WoodsJan 06, 2014
University of North Carolina at Chapel Hill - Access Contingent Upon Workflow MetadataAndrew WoodsJan 06, 2014
University of North Carolina at Chapel Hill - Setting Individual PermissionsAndrew WoodsJan 06, 2014
University of North Carolina at Chapel Hill - Unified AuthorizationAndrew WoodsJan 06, 2014
University of New South Wales - Updating-Editing multiple fedora recordsAndrew WoodsJan 06, 2014
University of New South Wales - Generate final data output for fedora storage in Cool URL formatAndrew WoodsJan 06, 2014
University of New South Wales - Versioning interim data and accessible through Cool URL formatAndrew WoodsJan 06, 2014
University of New South Wales - Deposit interim data in RDF format and search using SPAQRLAndrew WoodsJan 06, 2014
University of New South Wales - Data management plan ingest and storageAndrew WoodsJan 06, 2014
Tufts University - Streamlined and secure way of distinguishing open from closed dataAndrew WoodsJan 06, 2014
Indiana University Use Case - Dissemination of large audio-video filesAndrew WoodsJan 06, 2014
Indiana University Use Case - Support Flexible data model changeAndrew WoodsJan 06, 2014
Indiana University Use Case - Easy traversal against the triplestoreAndrew WoodsJan 06, 2014
University of York Use Case - Access ControlTom CramerDec 17, 2013
Test CoverageJonathan GreenJun 13, 2013
Dynamic metadata : Fedora as a Semantic Object StoreWolfram HorstmannJan 08, 2013
Use case [stub]: External triple store spanning several repositoriesWolfram HorstmannJan 08, 2013
Use case [stub]: Research data packages in multiple storesWolfram HorstmannJan 08, 2013
Repository is a continuous graphThorny StaplesJan 08, 2013
An archaeologist at the Smithsonian collaborating with a biologist at another research institutionThorny StaplesJan 08, 2013
Researchers control the policies on their own objectsThorny StaplesJan 08, 2013
Use Case: Updating metadata fields of multiple objectsMatthias RazumJan 08, 2013
HTTP 1.1 Caching SupportJonathan GreenOct 25, 2012
SecurityJonathan GreenOct 25, 2012
Use Case: Distributed authentication and authorizationMatthias RazumOct 24, 2012
Use Case: Storing heterogeneous research dataMatthias RazumOct 24, 2012
  • No labels

4 Comments

  1. 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...

    ?

  2. 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?

  3. I'll respond ASAP in the relevant page discussions. Thanks, Adam!

  4. 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.