Emerging use cases/user stories that we want to ensure Fedora will be well-prepared to address
Use case structure (from Wikipedia):
- Title (goal)
- Primary Actor
- Scope
- Level
- (Story): the body of the use case is simply a paragraph or two of text, informally describing what happens.
Smithsonian Use Cases
Title: Researchers control the policies on their own objects
Primary Actor: A researcher
Scope: All researchers
Level: got no clue what this means
Story: In SIdora, the researchers interface that is developed in Islandora on top of Fedora, researchers are the official "owners" of the objects that they create in the repository. This is owner in the Fedora object attribute sense. We interpret owner to mean the person who sets the policies. In SIdora, researchers can build large graphs of related objects they need to be able to selectively restrict the ones that they want kept private by setting the policy on the object, exposing them where they like by making them public.