| Table of Contents |
|---|
...
| Include Page | ||
|---|---|---|
|
...
Title
|
...
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.
...
| Include Page | ||
|---|---|---|
|
...
|
...
Title
|
...
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:
- An RDF-based metadata record describing any source data from which the “interim” data was derived (Item 1)
- RDF-based Metadata records about Researchers A and B (Items 2 and 3)
- An RDF-based metadata record about their research project (item 4). This includes relationship between the project (Item 4) and the data management plan created in Use case 1.
- The actual data object (item 5).
- An RDF-based metadata record describing their “interim” data and the research methodology (Item 6). This includes relationships between item 6 and items 1,2,3,4 and 5
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.
| Include Page | ||
|---|---|---|
|
...
|
...
|
...
Title
|
...
|
...
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:
- The new version of the data
- An RDF-based record about Researcher C
- An RDF-based metadata record describing the new version of the data and the research methodology. This also includes relationships between the new version of the data, metadata, Researcher C along with Researchers A and B, as well as the source data and the project record (items 1 and 4 in use case 2)
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.
| Include Page | ||
|---|---|---|
|
...
|
...
|
...
Title
|
...
|
...
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:
- A copy of the data
- An RDF-based metadata record describing the new data and the research methodology. This will include
- Relationship between the metadata record and the version 2 of the interim data result created in Use case 3
- Relationships between the metadata record, the project record and the researchers records
- Relationships with any external resources, such as related publications and datasets
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.
| Include Page | ||||
|---|---|---|---|---|
|
| Include Page | ||
|---|---|---|
|
Use Case 5 - Updating/Editing multiple fedora records
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. |
...
|
...
Title
...
|
...
Primary Actor
...
Researcher, Faculty/School/Department
...
Scope
...
...
Level
...
...
Story
Researcher A is interested in a report on the following statistics about his or her records.
- total number of records he or she has deposited over a certain period of time
- total number of times the records have been accessed over a certain period of time;
- total number of the times the associated attachments (datastreams) have been accessed over a certain period of time;
- geo-location/region from where the records and the attachments have been accessed.
Researcher A uses the Fedora SOAP or REST API to request the above stats from Fedora.
Researcher A's Faculty/School/Department is interested in a report on the following statistics.
...
|
...