Difference between revisions of "HUB Use Cases"

From Metadata-Registry
Jump to: navigation, search
(New page: ==XC HUB Use Cases== ===OAI Harvester Use Cases=== ===OAI Server Use Cases=== ===Service Registry Use Cases=== ====Use Case 1: A User wishes to register a Service==== ;Purpose:An XC pr...)
 
(→‎XC HUB Use Cases)
Line 1: Line 1:
 
==XC HUB Use Cases==
 
==XC HUB Use Cases==
 +
 +
===User Roles===
 +
 +
 +
 +
====Human Actors====
 +
 +
*'''System Administrator'''
 +
**Overall system administrator. Responsible for system-level software and hardware maintenance
 +
 +
*'''HUB Manager'''
 +
**One or more persons responsible for the administrative tasks involved in the management of a HUB instance
 +
**Authorizations: Service Administrator for all registered Services Editor for all Collections and Metadata [not sure about this one]
 +
**Only role authorized to Delete Services, Users, and Collections
 +
 +
*'''Service Administrator'''
 +
**One or more persons authorized to maintain one or more Service records. The user who registers a Service becomes the Service Administrator for that Service
 +
**Authorizations:
 +
***Service Administrator for all Services owned by that Agent
 +
***Edit/Delete Service Records
 +
***Designate other Registered Users as Service Contacts
 +
***Register Contacts and designate them as: Service Administrators for that Agent or Technical Contacts for that Agent
 +
 +
*'''Service Primary Contact'''
 +
**One or more persons acting on behalf of a Service, to whom notifications to the Service may be sent.
 +
**Domain of email address must match the domain registered to that Service
 +
 +
*'''Service Technical Contact'''
 +
**One or more persons acting on behalf of a service, to whom technical notifications to the Service may be sent.
 +
 +
*'''User'''
 +
 +
 +
 +
----
  
 
===OAI Harvester Use Cases===
 
===OAI Harvester Use Cases===
Line 8: Line 43:
  
 
====Use Case 1: A User wishes to register a Service====
 
====Use Case 1: A User wishes to register a Service====
−
;Purpose:An XC project has a metadata service that they wish to register. and needs to register their organization and at least one Maintainer
+
;Purpose:An XC project has a metadata service that they wish to register.  
−
;Primary Actor:Visitor
+
;Primary Actor:User
−
;Prerequisites:Visitor must be associated with the Organization
+
;Prerequisites:User must be associated with the organization providing the service
 
<b>Sequence</b>
 
<b>Sequence</b>
−
#Visitor accesses the Registry and initiates Organization Registration
+
#User accesses the Service Registry and initiates Registration in one of two ways:
−
#Visitor enters basic information about the organization -- Name, address, phone, domain (if available), URL, description, and enters self (and may designate others in addition) as organization contact by including name and email
+
#* by entering the URI of the OAI server for the service
−
#Visitor submits form and Registry sends confirmation email to all organizational contact(s).
+
#* by entering basic information about the organization providing the service -- Name, address, phone, domain (if available), URL, description. User may then enter self (and may designate others in addition) as Primary Contact or Technical Contact by including name and email. If User is neither Primary nor Technical Contact, another role may be entered.
−
#Registry asks if Visitor wishes to register as a Maintainer for that organization
+
#User submits form and Registry sends confirmation email to all contact(s) as well as the Hub Manager.
−
#If yes, see Use Case 8
+
#Use and contact(s) respond to confirmation email, verifying email address(es)
−
#Organization contact(s) responds to confirmation email, verifying email address(es)
+
#Registry notifies HUB Manager(s) that Service has been added
−
#Registry assigns PURL to organization and stores organization info in database
+
;Result: Service is registered. User is now a Registered User and an organization contact associated with the registered service.
−
#Registry notifies Registry Manager(s) that Organization has been added
+
−
;Result: Organization is registered. Visitor is now a Registered User and an Organization Contact associated with the registered organization.
+

Revision as of 15:57, 12 December 2007

XC HUB Use Cases

User Roles

[

Human Actors

  • System Administrator
    • Overall system administrator. Responsible for system-level software and hardware maintenance
  • HUB Manager
    • One or more persons responsible for the administrative tasks involved in the management of a HUB instance
    • Authorizations: Service Administrator for all registered Services Editor for all Collections and Metadata [not sure about this one]
    • Only role authorized to Delete Services, Users, and Collections
  • Service Administrator
    • One or more persons authorized to maintain one or more Service records. The user who registers a Service becomes the Service Administrator for that Service
    • Authorizations:
      • Service Administrator for all Services owned by that Agent
      • Edit/Delete Service Records
      • Designate other Registered Users as Service Contacts
      • Register Contacts and designate them as: Service Administrators for that Agent or Technical Contacts for that Agent
  • Service Primary Contact
    • One or more persons acting on behalf of a Service, to whom notifications to the Service may be sent.
    • Domain of email address must match the domain registered to that Service
  • Service Technical Contact
    • One or more persons acting on behalf of a service, to whom technical notifications to the Service may be sent.
  • User
    • A User is a visitor who has an intent to register a service. A User may assume an additional role while registering a service. **[


OAI Harvester Use Cases

OAI Server Use Cases

Service Registry Use Cases

Use Case 1: A User wishes to register a Service

Purpose
An XC project has a metadata service that they wish to register.
Primary Actor
User
Prerequisites
User must be associated with the organization providing the service

Sequence

  1. User accesses the Service Registry and initiates Registration in one of two ways:
    • by entering the URI of the OAI server for the service
    • by entering basic information about the organization providing the service -- Name, address, phone, domain (if available), URL, description. User may then enter self (and may designate others in addition) as Primary Contact or Technical Contact by including name and email. If User is neither Primary nor Technical Contact, another role may be entered.
  2. User submits form and Registry sends confirmation email to all contact(s) as well as the Hub Manager.
  3. Use and contact(s) respond to confirmation email, verifying email address(es)
  4. Registry notifies HUB Manager(s) that Service has been added
Result
Service is registered. User is now a Registered User and an organization contact associated with the registered service.
Retrieved from "http://wiki.metadataregistry.org/index.php?title=HUB_Use_Cases&oldid=3129"