NSDL Registry Use Case Documentation (Schemas)

From Metadata-Registry
Revision as of 11:46, 9 October 2005 by 65.101.155.196 (Talk)

Jump to: navigation, search

Use Case 1: Maintainer Publishes a Description of a Schema (Element Set)

Purpose
A Maintainer associated with an Organization wishes to enter the description of a schema (element set) into the Registry. This step is necessary before identifying specific elements (properties) or uploading an extant schema. It is important to note that this use case describes the entry of a description of an schema and not the schema itself.
Primary Actor
Maintainer
Prerequisites
  1. Organization must be registered
  2. Maintainer must be associated with that Organization and logged in

Sequence

  1. Maintainer accesses the Element Set Maintenance page and selects 'Describe New Element Set'
  2. Registry displays the Describe Element Set form containing a list of Organizations with which Maintainer is associated
  3. Maintainer selects Organization, adds a description of the Element Set
  4. Maintainer either:
    1. Saves the element set description in order to continue work later; or
    2. Submits the completed element set description to the Registry
  5. Registry assigns PURL to the element set description, stores description info in database and sends confirmation email (no response required)
  6. Registry notifies Registry Manager(s) that an element set description has been added
  7. Registry displays a list of other Maintainers associated with this Organization and asks if Maintainer wishes to add them to this element set
  8. Maintainer selects from list
  9. Registry sends other Maintainers a confirmation email indicating that they have been added to this application profile
Result
  1. Element set (schema) description is entered into the Registry and published