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.
Emerging use cases/user stories that we want to ensure Fedora will be well-prepared to address
Use case structure (from Wikipedia):
...
Goal) | |
---|
Primary Actor | |
---|
Scope | |
---|
Level |
---|
...
|
Story (A paragraph or two |
---|
...
...
From A. Soroka (UVa/APTrust)
- Title: Using the resources of the Semantic Web to describe repository contents
- Primary Actor: Curator
- Scope: One person workflow
- Level: I don't know what "level" is supposed to mean. Like in Dungeons and Dragons?
- (Story):
- Curators (and other similarly-motivated persons) should be able to use the powerful communal resources of the Semantic Web (vocabularies and ontologies) to describe resources in Fedora. It shouldn't be necessary to do very much customization to begin using sophisticated RDF to describe resources and have the descriptions available through usual presentations (SPARQL endpoints, RDF/XML Linked Data, etc.). This would not (and should never) include providing the machinery that a curator would actually use (UI), but the services that would support that machinery. Fedora offers some of this now, but much remains to be done.
B. Armintor (Columbia)
- Title: Asynchronous storage
- Primary Actor: System
- Scope:
- Level:
- Story: The storage subsystem has support for asynchronous storage devices, and can communicate the fixity and availability of content stored on such to other subsystems.
B. Armintor (Columbia)
- Title: Horizontal scalability
- Primary Actor: System Administrator
- Scope:
- Level:
- Story: Subsystems requiring increased throughput can be augmented by adding additional machines in parallel.
B. Armintor (Columbia)
- Title: Externalizable identifiers
- Primary Actor:
- Scope:
- Level:
- Story: The identity subsystem identifies objects and entities in an externally meaningful fashion (ie handles, ARKs).
B. Armintor (Columbia)
2019 Use Cases Expand |
---|
|
Content Report Table |
---|
showLikesCount | true |
---|
maxResults | 50 |
---|
showCommentsCount | true |
---|
spaces | FF |
---|
labels | Fedora6UseCase |
---|
|
|
2012-2016 Use Cases Expand |
---|
|
Content Report Table |
---|
showLikesCount | true |
---|
maxResults | 50 |
---|
showCommentsCount | true |
---|
spaces | FF |
---|
labels | uc-legacy |
---|
|
|
Expand |
---|
|
Content Report Table |
---|
showLikesCount | true |
---|
maxResults | 50 |
---|
showCommentsCount | true |
---|
spaces | FF |
---|
labels | uc-completed |
---|
|
|
Expand |
---|
|
Content Report Table |
---|
showLikesCount | true |
---|
maxResults | 50 |
---|
showCommentsCount | true |
---|
spaces | FF |
---|
labels | uc-obsolete |
---|
|
|
...