Use Case 1
Title | Data management plan ingest and storage |
Primary Actor | Researcher |
Scope | - |
Level | - |
Story | Researcher A creates a data management plan and stores in Fedora via Fedora User Interface or API. Note: Improve SOAP/REST API to handle deposit, edit and query final research data outputs. |
Use Case 2
Title | Deposit interim data in RDF format and search using SPAQRL |
Primary Actor | Researcher |
Scope |
|
Level |
|
Story | Researcher A’s grant application was successful, and is working with Researcher B on this project. They have already produced some data that they would like to store in the repository. So, they will need to store the following items in Fedora:
Note: It is not necessary for item 5 to be stored in Fedora with the rest of the items. Item 5 can be stored on external storage such as another Fedora or other storage system with a resolvable URL to item 5. Once stored in Fedora, the researchers are provided with URLs to the items stored. The URL of an item resolves to that item, which also contains URLs to the other related items. For example, item 6 will have URLs to items 1, 2, 3, 4 and 5, while item 4 will have a link to the data management plan. In addition, the URLs to the items are human readable, providing meaningful information about the corresponding resources. For example, the URL for item 1 could be http://www.domain.com/resoure/metadata/1135, which implies that this URL represents a metadata record. Additionally, Researcher A is interested in using SPARQL queries to find patterns in Fedora metadata records across multiple grant projects. Note: Improve SOAP/REST API to handle deposit, edit and query final research data outputs. |
Use Case 3
Title | Versioning interim data and accessible through ”Cool” URL format |
Primary Actor | Researcher |
Scope |
|
Level |
|
Story | Researcher C joins the project and improves the interim data. The improved data needs to be stored in Fedora as a new version of the previously stored record. So, the items deposited in Fedora are:
So, the URL of the new version becomes: http://www.domain.com/resoure/metadata/1/version2136 which has links to the previous version, Researchers A, B and C, the project record, and the new version of the data. Note: Improve SOAP/REST API to handle deposit, edit and query final research data outputs. |
Use Case 4
Title | Generate final data output for fedora storage in ”Cool” URL format |
Primary Actor | Researcher |
Scope |
|
Level |
|
Story | The research project is complete and has produced some final data that needs to be stored in Fedora. Notably, the final data has been produced from the interim data mentioned in Use case 3. The items to be stored in Fedora are:
The URLs of the final data output: Metadata: http://www.domain.com/resoure/metadata/2137 Data: http://www.domain.com/resoure/data/2138 Note: Improve SOAP/REST API to handle deposit, edit and query final research data outputs.
|
Use Case 5
Title | Updating/Editing multiple fedora records |
Primary Actor | Researcher |
Scope |
|
Level |
|
Story | Researcher A is interested in editing multiple Fedora records. Using a SPARQL query or simple search the researcher has the ability to locate and update metadata fields for multiple fedora records. This is of particular interest for large collections of related objects that require periodic updates. Note: Improve SOAP/REST API to handle deposit, edit and query final research data outputs. |
Other Use Cases of Interest
- xxx