Service Access

1. Client requests access to the CAS.
2. Service prompts user for identifying information. (UI)
3. Client provides identifying information.
4. Service authenticates user.
5. Service determines authorized access.
6. Service grants user requested access.

Alternative: Authentication Failure
At step 4, authentication fails.

1. Allow client to re-enter identifying information and re-try.

Alternative: User Not Authorized
At step 5, the client is not authorized to access the service.

1. The requested action is not allowed.

Product Access

1. Client requests access to a product.
2. Service determines authorized access.
3. Service grants client requested access.

Alternative: User Not Authorized
At step 2, the client is not authorized to access the specified product.

1. The requested action is not allowed.

Policy Definition

1. Follow steps 1 through 6 from the Service Access use case.
2. Service prompts client for product type information. (UI)
3. Client provides product type information. (This includes name, a data element list and any tasks and rules to be associated with the product type. This will also include access rights and on-line retention policy.)
4. Service adds the product type to the catalog.

Alternative: Policy Modification
At step 4, product type already exists in the catalog.

1. The product type policy is updated in the catalog.

Metadata Validation

1. Service validates metadata content syntactically. (This includes structure and mandatory elements.)
2. Service validates metadata content semantically. (This includes valid domain values.)

Alternative: Syntactic Validation Failure
At step 1, syntactic validation fails.

1. Allow client to re-enter metadata and re-try. (UI)

Alternative: Semantic Validation Failure
At step 2, semantic validation fails.

1. Allow client to re-enter metadata and re-try. (UI)

Product Registration

1. Follow steps 1 through 6 from the Service Access use case.
2. Service prompts client for product information. (UI)
3. Client provides product information. (This includes product type, product name, metadata and product specification.)
4. Follow steps 1 through 2 from the Metadata Validation use case.
5. Service copies product files into on-line storage.
6. Service registers product in the catalog with initial version.

Alternative: New Version
At step 6, the next available version number for the given product name is assigned.

Product Registration with Task Execution

1. Follow steps 1 through 6 from the Product Registration use case.
2. Service determines the tasks to execute.
3. Service executes and evaluates all rules associated with a task.
4. Service executes each task assuming all associated rules are satisfied.

Alternative: Rule Not Satisfied
At step 3, a rule is not satisfied.

1. Service moves the associated task into the queue to be executed later after a predetermined wait-time has expired.

Monitor Task Execution

1. Follow steps 1 through 6 from the Service Access use case.
2. Service prompts client for a date/time range. (UI)
3. Client provides a date/time range.
4. Service returns task information that matches the date/time range.

Move Product to Off-line Storage

1. Service determines whether a product is a candidate for moving to off-line storage based on access history and defined policies.
2. Service notifies the operator to move the product from on-line storage to off-line storage.
3. Operator moves the product from on-line storage to off-line storage.
4. Operator updates the product reference in the catalog to reflect the new location.

Product Query

1. Follow steps 1 through 6 from the Service Access use case.
2. Service prompts client for product identifying information. (UI)
3. Client provides product identifying information. (This could include product type and/or metadata.)
4. Service returns product references that match the product identifying information. (This would include product name and version.)

Product Retrieval

1. Follow steps 1 through 4 from the Product Query use case.
2. Client provides product identifying information. (This would include product name and version.)
3. Service prompts client for product staging location. (U I)
4. Client provides product staging location.
5. Service copies product from on-line storage to specified product staging location.

Product Retrieval

1. Follow steps 1 through 4 from the Product Query use case.
2. Client provides product identifying information. (This would include product name and version.)
3. Follow steps 1 through 3 from the Product Access use case.
4. Service determines product accessibility. (The product may be stored in on-line, near-line or off-line storage.)
5. Service prompts client for product staging location. (UI)
6. Client provides product staging location.
7. Service copies product from on-line or near-line storage to specified product staging location.

Alternative: Product is Off-line, Move On-line
At step 4, the product is determined to be in off-line storage.

1. Service notifies the client that the requested product is in off-line storage.
2. Service notifies the operator to move the product from off-line storage to on-line storage.
3. Operator moves the product from off-line storage to on-line storage.
4. Operator updates the product reference in the catalog to reflect the new location.
5. Operator notifies the client that the requested product is now available in on- line storage.
6. Return to primary scenario at step 1.

Alternative: Product is Off-line, Stage
At step 4, the product is determined to be in off-line storage.

1. Service notifies the client that the requested product is in off-line storage.
2. Service notifies the operator to copy the product from off-line storage to a staging area.
3. Operator copies the product from off-line storage to a staging area.
4. Operator notifies the client that the requested product is now available in a staging area for some period of time.
5. Client copies the product from the staging area.
6. Operator removes the product from the staging area after the period of time has expired.

Product Removal

1. Follow steps 1 through 4 from the Product Query use case.
2. Client provides product identifying information. (This would include product name and version.)
3. Follow steps 1 through 3 from the Product Access use case.
4. Service removes all references to the product from the catalog.

Product Metadata Modification

1. Follow steps 1 through 4 from the Product Query use case.
2. Client prov ides product identifying information. (This would include product name and version.)
3. Follow steps 1 through 3 from the Product Access use case.
4. Service prompts client for metadata modifications. (UI)
5. Client provides metadata modifications.
6. Follow steps 1 through 2 from the Metadata Validation use case.
7. Service updates metadata in the catalog for the specified product.

Product Access Rights Modification

1. Follow steps 1 through 4 from the Product Query use case.
2. Client provides product identifying information. (This would include product name and version.)
3. Follow steps 1 through 3 from the Product Access use case.
4. Service prompts client for access rights modifications. (UI)
5. Client provides access rights modifications.
6. Service updates access rights in the catalog for the specified product.