Difference between revisions of "NSDL Registry Use Case Documentation (Schemas)"

From Metadata-Registry
Jump to: navigation, search
Line 1: Line 1:
 +
=Registry Use Cases (Schemas)=
 
==Use Case 1: Publish a Description of a Schema (Element Set)==
 
==Use Case 1: Publish 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 <u>description</u> of an schema and not the schema itself.
 
;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 <u>description</u> of an schema and not the schema itself.

Revision as of 19:03, 10 October 2005

Registry Use Cases (Schemas)

Use Case 1: Publish 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

Use Case 2: Register Schema Element(s)—Hosted Schema

Purpose
Maintainer wishes to add new elements (properties) associated with a schema description that is hosted in the Registry
Primary Actor
Maintainer
Prerequisites
  1. Maintainer must be associated with that Organization and logged in
  2. The associated schema description exists in the Registry

Sequence

  1. Maintainer selects the schema from a list of schema descriptions with which he or she is associated
  2. Maintainer accesses the Element Set Maintenance page and selects 'Enter New Elements'
  3. Registry displays the Describe Element form
  4. Maintainer enters the information for one or more new elements
  5. Maintainer either:
    1. Saves the element(s) in order to continue work later; or
    2. Submits the element(s) to the Registry
  6. Registry assigns a PURL to each element based on the URI established at creation of the schema description
  7. Registry validates the schema
  8. If the schema does not validate, an email notification is sent to the associated Maintainer that includes error messages associated with the process, a link to a FAQ detailing the error messages and possible next steps
  9. If the schema passes validation routines:
    1. An email notification is sent to the Maintainer (and the Organization Contact)
    2. The Registry queues the schema for Registry Manager and/or Editor/Reviewer
  10. Upon review, Registry Manager submits the schema to the Registry
Result
Schema is registered in the Registry and published

Use Case 2: Register Schema Element(s)—Non-Hosted Schema