IESR Use Case 7: Contribute to IESR
| Creator |
Ann Apps, Mimas, The University of Manchester, UK |
| Date |
2006-11-09 |
| Identifier |
http://iesr.ac.uk/use/uses-cases/usecase7.html |
| Rights |
This work is licensed under a
Creative Commons Licence:
Attribution Required;
Non-Commercial;
Share-Alike.
|
| Change History |
|
| 2006-11-09 |
This is the first version |
Use Scenarios
These scenarios illustrate various ways in which IESR might be used according to the Use Case detailed in the next section.
7.1 Alison, who is the support officer for the XYZ service, has to supply details of the collections that she manages to a remote service that needs similar details. This involves supplying details of new collections and also timely updates to existing descriptions. The remote service requires this information to be supplied as an XML data file. Alison uses the IESR Editor to create and update the collection descriptions in IESR. She uses an option of the Editor to download each description in an XML format, which she then sends to the remote supplier.
7.2 Simon is the manager of a project that has created a collection of local information around the town of Erehwon, including photographs, tourist information, local history, geography, demographics, etc. Now this collection is completed, although future updating is expected, Simon wants to advertise this resource widely to increase its use. He contributes the description of this collection to IESR. In the next phase of the project an OAI-PMH interface onto the collection is developed to increase its open availability. Simon adds details of this OAI-PMH service to the collection description in IESR to advertise its availability.
7.3 Penny uses IESR (maybe via a portal) to discover resources that are useful to her research. She realises that a free resource she makes considerable use of, a dataset with Z39.50 access, is not described in IESR. She uses an IESR suggestions form to suggest that the dataset be described in IESR. IESR checks that the terms and conditions of the resource allow its description in IESR, contacting the resource provider for permission otherwise. IESR staff use available information about the resource to include its description in IESR. IESR then emails the resource provider to inform them of the resource's inclusion in IESR and responds to any requests for corrections.
[Note that this is a possible scenario only and that the Use Case Extension 1a details possible options for describing the resource.]
Use Case
Use Case Summary
A contributor includes and maintains descriptions of their resources in IESR.
Primary Actor (and goals)
| Contributor |
To contribute resources for inclusion in IESR, aiming for increased use of their resources |
Secondary Actors (and goals)
| IESR |
To register Contributor, quality check resource descriptions, and disseminate resources |
Stakeholders and Interests
| IESR Users |
To discover and use resource descriptions |
Main Success Scenario
| Step |
Action |
Analysis |
|---|
| 1 |
Contributor contacts IESR requesting inclusion of their resources |
|
| 2 |
IESR sets up basic registration for Contributor and provides guidelines |
|
| 3 |
Contributor completes more detailed registration with IESR |
|
| 4 |
Contributor uses IESR Editor to create resource descriptions |
|
| 5 |
IESR includes completed resource descriptions is database |
|
| 6 |
Contributor maintains descriptions in IESR by regular checking and updating if necessary |
IESR reminds Contributor regularly. IESR marks current status of description. A `status' field in the administrative metadata indicating when a record was last checked is required |
Extensions
[A possible extension to step n of the 'main success scenario' is labelled nx, steps involved in its execution being labelled nxm, etc.]
| Step |
Extension |
Analysis |
|---|
| 1a |
IESR is contacted by a user who suggests a resource that could be included |
Scenario 7.3. IESR needs a suggestions form |
| 1a1 |
IESR checks resource is in scope, and that its terms and conditions are suitable for its inclusion |
|
| 1a2 |
IESR contacts Contributor and suggests they describe their resource |
|
| 1a2a |
Alternatively IESR has the resource to create a description of the resource |
IESR needs staff to create resource descriptions |
| 1a2a1 |
IESR contacts resource provider to ask for permission to describe their resource |
|
| 1a2a2 |
IESR creates resource description from information publicly available |
|
| 1a2a3 |
IESR contacts resource provider for comments and corrections |
|
| | | |
| 4a |
Contributor wants an XML copy of description created in Editor |
Scenario 7.1 |
| 4a1 |
Contributor uses option in Editor to download XML copy of description |
IESR needs to include this option in Editor |
| 4b |
Contributor has insufficient manual effort available to provide description |
|
| 4b1 |
Contributor's resource will not appear in IESR |
This is failure scenario. Manual resource required for creating descriptions is an issue that needs discussion |
| | | |
| 5a |
An IESR QA check is performed on new description |
|
| 5a1 |
IESR contacts Contributor if corrections are required |
|
| | | |
| 6a |
A new service is implemented that provides access to a collection |
Scenario 7.2 |
| 6a1 |
Contributor uses IESR Editor to create description of new service |
|
| 6b |
Contributor has insufficient manual effort available to maintain description |
|
| 6b1 |
Contributor's resource may not be current in IESR |
This is failure scenario. Manual resource required for maintaining descriptions is an issue that needs discussion |
