NSDL Registry Use Cases (Application Profiles)
From Metadata-Registry
Revision as of 17:41, 8 October 2005 by 65.101.155.196 (Talk)
Contents
- 1 Registry Use Cases (Application Profiles)
- 1.1 Use Case 1: A Maintainer Publishes a Description of an Application Profile
- 1.2 Use Case 2: A Maintainer Creates an Application Profile
- 1.3 Use Case 3A: A Maintainer Creates an Application Profile--Uploading (Hosted)
- 1.4 Use Case 3B: A Maintainer Creates an Application Profile--Uploading (Non-Hosted)
Registry Use Cases (Application Profiles)
Use Case 1: A Maintainer Publishes a Description of an Application Profile
Use Case 2: A Maintainer Creates an Application Profile
- Purpose
- An NSDL project wants to
- Associate elements drawn from one or more declared metadata schemas with an application profile description in the Registry; and
- Define the uses of, and constraints on, those elements in the context of their project
- Primary Actor
- Maintainer
- Prerequisites
- A description of the Organization for whom the application profile is being created already exists in the Registry
- The Maintainer has already been associated with a Registry description of the application profile
- All elements to be used in the application profile must have been declared in one or more Web-addressable schemas whether hosted in the Registry or hosted elsewhere
Sequence
- Maintainer accesses the Create Application Profile page
- Maintainer searches for the appropriate application profile description amongst the descriptions assigned the Maintainer
- Maintainer searches for existing terms in the Registry that meet the needs of the Organization's metadata schema
- Maintainer selects approriate discovered elements and adds them one at a time to the application profile
- Maintainer may add elements to the application profile that are Web-addressable but not hosted in the Registry
- Maintainer determines use constraints on each element selected:
- If an element is to be restricted to the use of particular controlled vocabulary (rdfs:range), the Maintainer searches for that vocabulary in the Registry and associates it with the element
- Other constrains are applied (cardinality etc.)
- Maintainer either:
- Saves the application profile in order to continue work later; or
- Submits the completed application profile to the Registry
- Upon submission, Registry assigns a URI (PURL) to each term in the application profile using the base URI established when the application profile description was created
- Registry validates the input
- If the application profile 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
- If the application profile passes validation routines:
- An email notification is sent to the Maintainer (and the Organization Contact)
- The Registry queues the file for Registry Manager and/or Editor/Reviewer
- Upon review, Registry Manager submits the final application profile to the Registry
- Result
- Application profile associated with an Oranization is registered.
- A Maintainer associated with the Organization is associated with the application profile.
Use Case 3A: A Maintainer Creates an Application Profile--Uploading (Hosted)
- Purpose
- An NSDL project wants to upload a file to be hosted with the Registry that
- Associates elements drawn from one or more declared metadata schemas with an application profile description in the Registry; and
- Defines the uses of, and constraints on, those elements in the context of their project
- Primary Actor
- Maintainer
- Prerequisites
- A description of the Organization for whom the application profile is being created already exists in the Registry
- The Maintainer has already been associated with a Registry description of the application profile
- All elements to be used in the application profile have been declared in one or more Web-addressable schemas whether hosted in the Registry or hosted elsewhere
- The application profile to be uploaded already exists and is encoded in a Registry-appropriate syntax
- The application profile creator has included appropriate URIs for all elements base on the URI established when the application profile description was created
Sequence
- Maintainer accesses the Create Application Profile page
- Maintainer searches for the appropriate application profile description amongst the descriptions assigned the Maintainer
- Maintainer selects the file upload function for an existing application profile
- Maintainer selects the application profile file to upload by:
- Finding the application profile file on the Maintainer's local machine; or
- Providing a network address where the encoded file may be found
- Maintainer either:
- Saves the application profile in order to continue work later; or
- Submits the completed application profile to the Registry
- Upon submission, Registry validates the input
- If the application profile 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
- If the application profile passes validation routines:
- An email notification is sent to the Maintainer (and the Organization Contact)
- The Registry queues the file for Registry Manager and/or Editor/Reviewer
- Upon review, Registry Manager submits the final application profile to the Registry
- Result
- Application profile associated with an Oranization is registered.
- A Maintainer associated with the Organization is associated with the application profile.
Use Case 3B: A Maintainer Creates an Application Profile--Uploading (Non-Hosted)
- Purpose
- An NSDL project wants to upload a file for a non-hosted application profile that
- Associates elements drawn from one or more declared metadata schemas with an application profile description in the Registry; and
- Defines the uses of, and constraints on, those elements in the context of their project
Note: This use case is for application profiles that are hosted elsewhere--i.e., in a registry maintained by an agency other than the NSDL Registry
- Primary Actor
- Maintainer
- Prerequisites
- A description of the Organization for whom the application profile is being created already exists in the Registry
- The Maintainer has already been associated with a Registry description of the application profile
- All elements to be used in the application profile have been declared in one or more Web-addressable schemas whether hosted in the Registry or hosted elsewhere
- The application profile to be uploaded already exists and is encoded in a Registry-appropriate syntax
- The application profile creator has included appropriate URIs for all elements to the namespace managed by the Organization associated with the application profile
Sequence
- Maintainer accesses the Create Application Profile page
- Maintainer searches for the appropriate application profile description amongst the descriptions assigned the Maintainer
- Maintainer selects the file upload function for an existing application profile
- Maintainer selects the application profile file to upload by:
- Finding the application profile file on the Maintainer's local machine; or
- Providing a network address where the encoded file may be found
- Maintainer either:
- Saves the application profile in order to continue work later; or
- Submits the completed application profile to the Registry
- Upon submission, Registry validates the input
- If the application profile 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
- If the application profile passes validation routines:
- An email notification is sent to the Maintainer (and the Organization Contact)
- The Registry queues the file for Registry Manager and/or Editor/Reviewer
- Upon review, Registry Manager submits the final application profile to the Registry
- Result
- Application profile associated with an Oranization is registered.
- A Maintainer associated with the Organization is associated with the application profile.