Difference between revisions of "NSDL Registry Use Cases (Application Profiles)"

From Metadata-Registry
Jump to: navigation, search
(Use Case 9: Change Status of Application Profile Elements—Non-Hosted Application Profile)
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
=Registry Use Cases: Application Profiles=
 
==Use Case 1: Publish a Description of an Application Profile==
 
==Use Case 1: Publish a Description of an Application Profile==
 
;Purpose:A Maintainer associated with an Organization wishes to enter the description of an application profile into the Registry. This step is necessary before identifying specific terms or uploading an extant application profile. It is important to note that this use case describes the entry of a description of an application profile and not the application profile itself.
 
;Purpose:A Maintainer associated with an Organization wishes to enter the description of an application profile into the Registry. This step is necessary before identifying specific terms or uploading an extant application profile. It is important to note that this use case describes the entry of a description of an application profile and not the application profile itself.
Line 12: Line 13:
 
##Saves the application profile description in order to continue work later; or
 
##Saves the application profile description in order to continue work later; or
 
##Submits the completed application profile description to the Registry
 
##Submits the completed application profile description to the Registry
#Registry assigns PURL to application profile description, stores description info in database and sends confirmation email (no response required)
+
#Registry assigns URI to application profile description, stores description info in database and sends confirmation email (no response required)
 
#Registry notifies Registry Manager(s) that application profile description has been added
 
#Registry notifies Registry Manager(s) that application profile description has been added
 
#Registry displays a list of other Maintainers associated with this Organization and asks if Maintainer wishes to add them to this application profile and also offers Maintainer the opportunity to Register other Maintainers or add existing Maintainers to this Organization
 
#Registry displays a list of other Maintainers associated with this Organization and asks if Maintainer wishes to add them to this application profile and also offers Maintainer the opportunity to Register other Maintainers or add existing Maintainers to this Organization
Line 20: Line 21:
 
#Application profile description is entered into the Registry
 
#Application profile description is entered into the Registry
  
==Use Case 2: Publish an Application Profile ==
+
==Use Case 2: Publish an Application Profile Using Existing Elements Only==
;Purpose:An NSDL project wants to  
+
;Purpose:An organization or project wants to  
 
#Associate elements drawn from one or more declared metadata schemas with an application profile description in the Registry; and  
 
#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
+
#Define the uses of, and constraints on, those elements in the context of their project, and
 +
#Define appropriate vocabularies for use in the application profile
 
;Primary Actor:Maintainer
 
;Primary Actor:Maintainer
 
;Prerequisites:
 
;Prerequisites:
#A description of the Organization for whom the application profile is being created already exists in the Registry   
+
#A description of the Organization for whom the application profile is being created already exists in the Registry
 +
#An Application Profile description is already registered  
 
#The Maintainer has already been associated with a Registry description of the application profile
 
#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
 
#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
 
<b>Sequence</b>
 
<b>Sequence</b>
#Maintainer accesses the <i>Create Application Profile</i> page
 
 
#Maintainer searches for the appropriate application profile description amongst the descriptions assigned the Maintainer
 
#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 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 selects appropriate discovered elements and adds them 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 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 2a: Publish an Application Profile With Additional "Local" Elements==
 +
;Purpose:An organization or project wants to
 +
#Associate elements drawn from one or more declared metadata schemas with an application profile description in the Registry; and
 +
#Add specific locally-defined elements to the application profile, and
 +
#Define the uses of, and constraints on, those elements in the context of their project, and
 +
#Define appropriate vocabularies for use in the application profile
 +
;Primary Actor:Maintainer
 +
;Prerequisites:
 +
#A description of the Organization for whom the application profile is being created already exists in the Registry
 +
#An Application Profile description is already registered 
 +
#The Maintainer has already been associated with a Registry description of the application profile
 +
#All non-local 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
 +
<b>Sequence</b>
 +
#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 appropriate discovered elements and adds them to the application profile
 
##Maintainer may add elements to the application profile that are Web-addressable but not hosted in the Registry
 
##Maintainer may add elements to the application profile that are Web-addressable but not hosted in the Registry
 +
#Maintainer registers local elements for use within the application profile
 +
##As part of the registration process a URI is created for the local element
 
#Maintainer determines use constraints on each element selected:
 
#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
 
##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
Line 41: Line 79:
 
##Saves the application profile in order to continue work later; or
 
##Saves the application profile in order to continue work later; or
 
##Submits the completed application profile to the Registry
 
##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
+
#Upon submission, Registry assigns a URI to each term in the application profile using the base URI established when the application profile description was created
 
#Registry validates the input
 
#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 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
Line 52: Line 90:
 
#A Maintainer associated with the Organization is associated with the application profile.
 
#A Maintainer associated with the Organization is associated with the application profile.
  
==Use Case 3: Create an Application Profile--Uploading (Hosted)==
+
==Use Case 3: Publish an Application Profile--Uploading (Hosted)==
;Purpose:An NSDL project wants to upload a file containing a machine-readable application profile to be hosted by the Registry that  
+
;Purpose:An organization or project wants to upload a file containing a machine-readable application profile to be hosted by the Registry that  
 
#Associates elements drawn from one or more declared metadata schemas with an application profile description in the Registry; and  
 
#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
 
#Defines the uses of, and constraints on, those elements in the context of their project
 +
#Associates element usage with appropriate controlled vocabularies
 
;Primary Actor:Maintainer
 
;Primary Actor:Maintainer
 
;Prerequisites:
 
;Prerequisites:
 
#A description of the Organization for whom the application profile is being created already exists in the Registry   
 
#A description of the Organization for whom the application profile is being created already exists in the Registry   
 +
#A description of the application profile has been regsitered
 
#The Maintainer has already been associated with a Registry description of the application profile
 
#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
 
#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 to be uploaded already exists and is encoded in a Registry-appropriate syntax
#The application profile creator has included appropriate Registry URIs for all elements base on the URI established when the application profile description was created
+
#The application profile creator has included appropriate Registry URIs for all elements based on the URI established when the application profile description was created
 +
#The application profile created has included appropriate URIs for all controlled vocabularies used within the application profile
 
<b>Sequence</b>
 
<b>Sequence</b>
#Maintainer accesses the <i>Create Application Profile</i> page
 
 
#Maintainer searches for the appropriate application profile description amongst the descriptions assigned the Maintainer
 
#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 file upload function for an existing application profile
Line 84: Line 124:
  
 
==Use Case 4: Create an Application Profile&#8212;Uploading (Non-Hosted)==
 
==Use Case 4: Create an Application Profile&#8212;Uploading (Non-Hosted)==
;Purpose:An NSDL project wants to upload a file for a non-hosted, machine-readable application profile that  
+
;Purpose:An organization or project wants to upload a file for a non-hosted, machine-readable application profile that  
 
#Associates elements drawn from one or more declared metadata schemas with an application profile description in the Registry; and  
 
#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
 
#Defines the uses of, and constraints on, those elements in the context of their project
 +
#Associates element usage with appropriate controlled vocabularies
 
<u>Note:</u> 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
 
<u>Note:</u> 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
 
;Primary Actor:Maintainer
 
;Prerequisites:
 
;Prerequisites:
 
#A description of the Organization for whom the application profile is being created already exists in the Registry   
 
#A description of the Organization for whom the application profile is being created already exists in the Registry   
 +
#The application profile description has already been registered (or uploaded)
 
#The Maintainer has already been associated with a Registry description of the application profile
 
#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
 
#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
Line 135: Line 177:
 
##The Registry queues the file for Registry Manager and/or Editor/Reviewer
 
##The Registry queues the file for Registry Manager and/or Editor/Reviewer
 
#Upon review, Registry Manager submits the final edited application profile to the Registry
 
#Upon review, Registry Manager submits the final edited application profile to the Registry
#Registry backs up the old application profile and replaces it with the new file (possible rollback?)
+
#Registry backs up the existing version of the application profile, associates it with the file being added, and adds the new (edited) file
 
;Result:
 
;Result:
 
Updated application profile description
 
Updated application profile description
Line 159: Line 201:
 
##The Registry queues the file for Registry Manager and/or Editor/Reviewer
 
##The Registry queues the file for Registry Manager and/or Editor/Reviewer
 
#Upon review, Registry Manager submits the final edited application profile to the Registry
 
#Upon review, Registry Manager submits the final edited application profile to the Registry
#Registry backs up the old application profile and replaces it with the new file (possible rollback?)
+
#Registry backs up the existing version of the application profile, associates it with the file being added, and adds the new (edited) file
 
;Result:
 
;Result:
 
Updated application profile
 
Updated application profile
Line 209: Line 251:
 
##The Registry queues the file for Registry Manager and/or Editor/Reviewer
 
##The Registry queues the file for Registry Manager and/or Editor/Reviewer
 
#Upon review, Registry Manager submits the final edited application profile to the Registry
 
#Upon review, Registry Manager submits the final edited application profile to the Registry
#Registry backs up the old application profile and replaces it with the new file (possible rollback?)
+
#Registry backs up the existing version of the application profile, associates it with the file being added, and adds the new (edited) file
 
;Result:
 
;Result:
 
Updated application profile
 
Updated application profile
Line 239: Line 281:
 
;Result:
 
;Result:
 
Updated application profile with elements(s) status changes
 
Updated application profile with elements(s) status changes
 +
 +
[[Category:Use Cases]]

Latest revision as of 19:46, 27 March 2010

Registry Use Cases: Application Profiles

Use Case 1: Publish a Description of an Application Profile

Purpose
A Maintainer associated with an Organization wishes to enter the description of an application profile into the Registry. This step is necessary before identifying specific terms or uploading an extant application profile. It is important to note that this use case describes the entry of a description of an application profile and not the application profile 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 Application Profile Maintenance page and selects 'Describe New Application Profile'
  2. Registry displays the Describe Application Profile form, containing a list of Organizations with which Maintainer is associated
  3. Maintainer selects Organization, adds a description of the application profile
  4. Maintainer either:
    1. Saves the application profile description in order to continue work later; or
    2. Submits the completed application profile description to the Registry
  5. Registry assigns URI to application profile description, stores description info in database and sends confirmation email (no response required)
  6. Registry notifies Registry Manager(s) that application profile 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 application profile and also offers Maintainer the opportunity to Register other Maintainers or add existing Maintainers to this Organization
  8. Maintainer selects from list and/or adds Maintainer registration information for other Maintainers
  9. Registry sends other Maintainers a confirmation email indicating that they have been added to this application profile
Result
  1. Application profile description is entered into the Registry

Use Case 2: Publish an Application Profile Using Existing Elements Only

Purpose
An organization or project wants to
  1. Associate elements drawn from one or more declared metadata schemas with an application profile description in the Registry; and
  2. Define the uses of, and constraints on, those elements in the context of their project, and
  3. Define appropriate vocabularies for use in the application profile
Primary Actor
Maintainer
Prerequisites
  1. A description of the Organization for whom the application profile is being created already exists in the Registry
  2. An Application Profile description is already registered
  3. The Maintainer has already been associated with a Registry description of the application profile
  4. 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

  1. Maintainer searches for the appropriate application profile description amongst the descriptions assigned the Maintainer
  2. Maintainer searches for existing terms in the Registry that meet the needs of the Organization's metadata schema
  3. Maintainer selects appropriate discovered elements and adds them to the application profile
    1. Maintainer may add elements to the application profile that are Web-addressable but not hosted in the Registry
  4. Maintainer determines use constraints on each element selected:
    1. 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
    2. Other constrains are applied (cardinality etc.)
  5. Maintainer either:
    1. Saves the application profile in order to continue work later; or
    2. Submits the completed application profile to the Registry
  6. Upon submission, Registry assigns a URI to each term in the application profile using the base URI established when the application profile description was created
  7. Registry validates the input
  8. 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
  9. If the application profile passes validation routines:
    1. An email notification is sent to the Maintainer (and the Organization Contact)
    2. The Registry queues the file for Registry Manager and/or Editor/Reviewer
  10. Upon review, Registry Manager submits the final application profile to the Registry
Result
  1. Application profile associated with an Oranization is registered.
  2. A Maintainer associated with the Organization is associated with the application profile.

Use Case 2a: Publish an Application Profile With Additional "Local" Elements

Purpose
An organization or project wants to
  1. Associate elements drawn from one or more declared metadata schemas with an application profile description in the Registry; and
  2. Add specific locally-defined elements to the application profile, and
  3. Define the uses of, and constraints on, those elements in the context of their project, and
  4. Define appropriate vocabularies for use in the application profile
Primary Actor
Maintainer
Prerequisites
  1. A description of the Organization for whom the application profile is being created already exists in the Registry
  2. An Application Profile description is already registered
  3. The Maintainer has already been associated with a Registry description of the application profile
  4. All non-local 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

  1. Maintainer searches for the appropriate application profile description amongst the descriptions assigned the Maintainer
  2. Maintainer searches for existing terms in the Registry that meet the needs of the Organization's metadata schema
  3. Maintainer selects appropriate discovered elements and adds them to the application profile
    1. Maintainer may add elements to the application profile that are Web-addressable but not hosted in the Registry
  4. Maintainer registers local elements for use within the application profile
    1. As part of the registration process a URI is created for the local element
  5. Maintainer determines use constraints on each element selected:
    1. 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
    2. Other constrains are applied (cardinality etc.)
  6. Maintainer either:
    1. Saves the application profile in order to continue work later; or
    2. Submits the completed application profile to the Registry
  7. Upon submission, Registry assigns a URI to each term in the application profile using the base URI established when the application profile description was created
  8. Registry validates the input
  9. 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
  10. If the application profile passes validation routines:
    1. An email notification is sent to the Maintainer (and the Organization Contact)
    2. The Registry queues the file for Registry Manager and/or Editor/Reviewer
  11. Upon review, Registry Manager submits the final application profile to the Registry
Result
  1. Application profile associated with an Oranization is registered.
  2. A Maintainer associated with the Organization is associated with the application profile.

Use Case 3: Publish an Application Profile--Uploading (Hosted)

Purpose
An organization or project wants to upload a file containing a machine-readable application profile to be hosted by the Registry that
  1. Associates elements drawn from one or more declared metadata schemas with an application profile description in the Registry; and
  2. Defines the uses of, and constraints on, those elements in the context of their project
  3. Associates element usage with appropriate controlled vocabularies
Primary Actor
Maintainer
Prerequisites
  1. A description of the Organization for whom the application profile is being created already exists in the Registry
  2. A description of the application profile has been regsitered
  3. The Maintainer has already been associated with a Registry description of the application profile
  4. 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
  5. The application profile to be uploaded already exists and is encoded in a Registry-appropriate syntax
  6. The application profile creator has included appropriate Registry URIs for all elements based on the URI established when the application profile description was created
  7. The application profile created has included appropriate URIs for all controlled vocabularies used within the application profile

Sequence

  1. Maintainer searches for the appropriate application profile description amongst the descriptions assigned the Maintainer
  2. Maintainer selects the file upload function for an existing application profile
  3. Maintainer selects the application profile file to upload by:
    1. Finding the application profile file on the Maintainer's local machine; or
    2. Providing a network address where the encoded file may be found
  4. Maintainer either:
    1. Saves the application profile in order to continue work later; or
    2. Submits the completed application profile to the Registry
  5. Upon submission, Registry validates the input
  6. 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
  7. If the application profile passes validation routines:
    1. An email notification is sent to the Maintainer (and the Organization Contact)
    2. The Registry queues the file for Registry Manager and/or Editor/Reviewer
  8. Upon review, Registry Manager submits the final application profile to the Registry and it is published
Result
  1. Application profile associated with an Oranization is registered.
  2. A Maintainer associated with the Organization is associated with the application profile.

Use Case 4: Create an Application Profile—Uploading (Non-Hosted)

Purpose
An organization or project wants to upload a file for a non-hosted, machine-readable application profile that
  1. Associates elements drawn from one or more declared metadata schemas with an application profile description in the Registry; and
  2. Defines the uses of, and constraints on, those elements in the context of their project
  3. Associates element usage with appropriate controlled vocabularies

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
  1. A description of the Organization for whom the application profile is being created already exists in the Registry
  2. The application profile description has already been registered (or uploaded)
  3. The Maintainer has already been associated with a Registry description of the application profile
  4. 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
  5. The application profile to be uploaded already exists and is encoded in a Registry-appropriate syntax
  6. The application profile creator has included appropriate URIs for all elements to the namespace managed by the Organization associated with the application profile

Sequence

  1. Maintainer accesses the Create Application Profile page
  2. Maintainer searches for the appropriate application profile description amongst the descriptions assigned the Maintainer
  3. Maintainer selects the file upload function for an existing application profile
  4. Maintainer selects the application profile file to upload by:
    1. Finding the application profile file on the Maintainer's local machine; or
    2. Providing a network address where the encoded file may be found
  5. Maintainer either:
    1. Saves the application profile in order to continue work later; or
    2. Submits the completed application profile to the Registry
  6. Upon submission, Registry validates the input
  7. 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
  8. If the application profile passes validation routines:
    1. An email notification is sent to the Maintainer (and the Organization Contact)
    2. The Registry queues the file for Registry Manager and/or Editor/Reviewer
  9. Upon review, Registry Manager submits the final application profile to the Registry
Result
  1. Application profile associated with an Oranization is registered and published
  2. A Maintainer associated with the Organization is associated with the application profile

Use Case 5: Add/Edit Application Profile Description

Purpose
Maintainer associated with an existing application profile wishes to add information or editing existing information in the application profile description
Primary Actor
Maintainer
Prerequisites
  1. The Maintainer has already been associated with a Registry description of the application profile
  2. The application profile has already been registered and published

Sequence

  1. Maintainer searches for his or her associated application profiles
  2. Maintainer selects application profile to edit
  3. Registry provides Edit Application Profile Description form
  4. Maintainer adds/edits information
  5. Maintainer either:
    1. Saves the application profile edits in order to continue work later; or
    2. Submits the edited application profile to the Registry
  6. Upon submission, Registry validates the input
  7. 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
  8. If the application profile passes validation routines:
    1. An email notification is sent to the Maintainer (and the Organization Contact)
    2. The Registry queues the file for Registry Manager and/or Editor/Reviewer
  9. Upon review, Registry Manager submits the final edited application profile to the Registry
  10. Registry backs up the existing version of the application profile, associates it with the file being added, and adds the new (edited) file
Result

Updated application profile description

Use Case 6: Add/Edit Application Profile Elements—Hosted Application Profile

Purpose
Maintainer associated with an existing application profile wishes to add information or editing existing information to elements in the application profile
Primary Actor
Maintainer
Prerequisites
  1. The Maintainer has already been associated with a Registry description of the application profile
  2. The application profile has already been registered and published

Sequence

  1. Maintainer searches for his or her associated application profiles
  2. Maintainer selects application profile containing the terms to edit
  3. Registry provides Edit Application Profile Elements form
  4. Maintainer adds/edits information
  5. Maintainer either:
    1. Saves the application profile edits in order to continue work later; or
    2. Submits the edited application profile to the Registry
  6. Upon submission, Registry validates the input
  7. 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
  8. If the application profile passes validation routines:
    1. An email notification is sent to the Maintainer (and the Organization Contact)
    2. The Registry queues the file for Registry Manager and/or Editor/Reviewer
  9. Upon review, Registry Manager submits the final edited application profile to the Registry
  10. Registry backs up the existing version of the application profile, associates it with the file being added, and adds the new (edited) file
Result

Updated application profile

Use Case 7: Add/Edit Application Profile Elements—Non-Hosted Application Profile

Purpose
Maintainer associated with a non-hosted application profile existing in the Registry wishes to add information or editing existing information for an element in the application profile
Primary Actor
Maintainer
Prerequisites
  1. The Maintainer has already been associated with a Registry description of the application profile
  2. The application profile to be changed is hosted and maintained in a namespace outside the Registry
  3. Edits to the application profile have been handled in the Organization's namespace according to its own editorial and versioning processes

Sequence

  1. Maintainer selects correct application profile in the Registry from those to which he or she has been associated
  2. Maintainer selects the file upload function for an existing application profile
  3. Maintainer selects the application profile file to upload by:
    1. Finding the application profile file on the Maintainer's local machine; or
    2. Providing a network address where the encoded file may be found
  4. Maintainer either:
    1. Saves the edited application profile in order to continue work later; or
    2. Submits the edited application profile to the Registry
  5. Upon submission, Registry validates the input
  6. 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
  7. If the application profile passes validation routines:
    1. An email notification is sent to the Maintainer (and the Organization Contact)
    2. The Registry queues the file for Registry Manager and/or Editor/Reviewer
  8. Upon review, Registry Manager submits the final application profile to the Registry
  9. Registry backs up the existing version of the application profile, associates it with the file being added, and adds the new (edited) file
Result

Updated application profile

Use Case 8: Change Status of Application Profile Elements—Hosted Application Profile

Purpose
Maintainer associated with an existing application profile wishes to change the status of an element
Primary Actor
Maintainer
Prerequisites
  1. The Maintainer has already been associated with a Registry description of the application profile
  2. The application profile has already been registered and published

Sequence

  1. Maintainer searches for his or her associated application profiles
  2. Maintainer selects application profile containing the element whose status is to be changed
  3. Registry provides Edit Application Profile Elements form
  4. Maintainer changes the status of the element
  5. Maintainer either:
    1. Saves the application profile element status change in order to continue work later; or
    2. Submits the edited application profile to the Registry
  6. Upon submission, Registry validates the input
  7. 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
  8. If the application profile passes validation routines:
    1. An email notification is sent to the Maintainer (and the Organization Contact)
    2. The Registry queues the file for Registry Manager and/or Editor/Reviewer
  9. Upon review, Registry Manager submits the final edited application profile to the Registry
  10. Registry backs up the existing version of the application profile, associates it with the file being added, and adds the new (edited) file
Result

Updated application profile

Use Case 9: Change Status of Application Profile Elements—Non-Hosted Application Profile

Purpose
Maintainer associated with an existing, non-hosted application profile wishes to change the status of an element
Primary Actor
Maintainer
Prerequisites
  1. The Maintainer has already been associated with a Registry description of the application profile
  2. The application profile has already been registered and published in the Registry
  3. The status change for the element(s) has been handled in the Organization's namespace according to its own editorial processes

Sequence

  1. Maintainer searches Registry for his or her associated application profiles
  2. Maintainer selects application profile containing the element(s) whose status is to be changed
  3. Maintainer selects the file upload function for an existing application profile
  4. Maintainer selects the application profile file containing the status change(s) to upload by:
    1. Finding the application profile file on the Maintainer's local machine; or
    2. Providing a network address where the encoded file may be found
  5. Maintainer either:
    1. Saves the edited application profile in order to continue work later; or
    2. Submits the edited application profile to the Registry
  6. Upon submission, Registry validates the input
  7. 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
  8. If the application profile passes validation routines:
    1. An email notification is sent to the Maintainer (and the Organization Contact)
    2. The Registry queues the file for Registry Manager and/or Editor/Reviewer
  9. Upon review, Registry Manager submits the final application profile to the Registry
  10. Registry backs up the existing version of the application profile, associates it with the file being added, and adds the new (edited) file
Result

Updated application profile with elements(s) status changes