UC-6.1

Main Page > Vancouver Digital Archives > Requirements Analysis > UC-6 Access> UC-6.1 Co-ordinate Consumer Information Request

{| border="1" cellpadding="10" cellspacing="0" width=90%
 * colspan="4" style="background-color:silver;"|

UC-6.1 Co-ordinate Consumer Information Request
UC-6.1 Co-ordinate Consumer Information Request UC-6 Access None Co-ordinate Access Activities receives a request from Consumer for information (query results or formatted report) and provides Deliver Report with the requested information for delivery to Consumer. n/a Consumer submits query/report request (no reference use case number, as this is an externally initiated action) Co-ordinate Access Activities provides requested information to Deliver Response The Coordinate Access Activities function provides a single user interface to the information holdings of the archive... Three categories of Consumer requests are distinguished: query requests, which are executed in Data Management and return immediate result sets for presentation to the user; report requests, which may require a number of queries and produce formatted reports for delivery to the Consumer; and orders, which may access either or both Data Management and Archival Storage to prepare a formal Dissemination Information Package (DIP) for on- or off-line delivery...  This function will determine if resources are available to perform a request, assure that the user is authorized to access and receive the requested items, and notify the Consumer that a request has been accepted or rejected (possibly with an estimate of request cost and an option to cancel the request). It will then transfer the request to Data Management or to the Generate DIP function for execution....
 * colspan="2" style="background-color:#E0FFFF;"|Summary
 * Number
 * Number
 * Number
 * Name
 * Name
 * Context
 * Context
 * Context
 * Sub-Use Cases
 * Sub-Use Cases
 * Overview
 * Overview
 * Actors
 * Consumer
 * Co-ordinate Access Activities
 * Data Management>Perform Queries
 * Data Management>Generate Report
 * Deliver Response
 * colspan="2" style="background-color:#E0FFFF;"|Description
 * Preconditions
 * colspan="2" style="background-color:#E0FFFF;"|Description
 * Preconditions
 * Preconditions
 * Preconditions
 * Trigger
 * Trigger
 * Successful outcome
 * Successful outcome
 * Steps
 * 1) Co-ordinate Access Activities receives query request from Consumer (OAIS s 4.1.1.7, p 4-15)
 * 2) Co-ordinate Access Activities receives report request from Consumer (OAIS s 4.1.1.7, p 4-15)
 * 3) Co-ordinate Access Activities evaluates resources available to respond to request (OAIS s 4.1.1.7, p 4-15)
 * 4) Co-ordinate Access Activities evaluates Consumer's authorization to access requested information (OAIS s 4.1.1.7, p 4-15)
 * 5) Co-ordinate Access Activities provides notification of acceptance/rejection of Consumer's request to Deliver Response (this is considered to be assistance in the diagram illustrated by OAIS 4.1.1.7 Figure F-1) (OAIS s 4.1.1.7, p 4-15)
 * 6) Co-ordinate Access Activities sends Consumer's query request to Data Management>Perform Queries (OAIS s 4.1.1.7, p 4-15; Figure F-1: Composite of Functional Entities)
 * 7) Co-ordinate Access Activities sends Consumer's report request to Data Management>Generate Report (OAIS s 4.1.1.7, p 4-15; Figure F-1: Composite of Functional Entities)
 * 8) Co-ordinate Access Activities receives result set from Data Management>Perform Queries (OAIS s 4.1.1.7, p 4-15; Figure F-1: Composite of Functional Entities)
 * 9) Co-ordinate Access Activities receives report from Data Management>Generate Report (OAIS s 4.1.1.7, p 4-15; Figure F-1: Composite of Functional Entities)
 * 10) Co-ordinate Access Activities provides result set to Deliver Response (OAIS s 4.1.1.7, p 4-15; Figure 4-7: Functions of Access)
 * 11) Co-ordinate Access Activities provides report to Deliver Response (OAIS Figure 4-7: Functions of Access; OAIS Figure F-1: Composite of Functional Entities)
 * Exceptions
 * colspan="2" style="background-color:#E0FFFF;"|Documentation
 * Citations
 * OAIS s 4.1.1.7, p 4-15
 * colspan="2" style="background-color:#E0FFFF;"|Documentation
 * Citations
 * OAIS s 4.1.1.7, p 4-15
 * Citations
 * OAIS s 4.1.1.7, p 4-15
 * OAIS s 4.1.1.7, p 4-15
 * Diagrams
 * colspan="2" style="background-color:#E0FFFF;"|Notes
 * This use case is based on the Coordinate Access Activities function. The use case only pertains to requests initiated by the Consumer. Requests initiated by Administration have been separated into a separate use case UC-6.2, as some steps are not applicable to the Administration initiated request.
 * Event Based Orders and Adhoc Orders are understood to be sub-classes of the more general Order Agreement with the Consumer. Orders referred to in this sub-use case (and in UC-6.2 as well) are Adhoc orders as described on OAIS page 2-10 (section 2.3.3). Event Based Orders are addressed by use case UC-6.5.
 * The OAIS model makes separate references to "query requests" and "report requests". Because both requests draw on the data management database and follow similar workflows, they have been grouped together in this use case as an "Information Request" for simplicity. Contrast with an "order request" which requests delivery of a DIP, or an "assistance request" which request help.
 * }
 * This use case is based on the Coordinate Access Activities function. The use case only pertains to requests initiated by the Consumer. Requests initiated by Administration have been separated into a separate use case UC-6.2, as some steps are not applicable to the Administration initiated request.
 * Event Based Orders and Adhoc Orders are understood to be sub-classes of the more general Order Agreement with the Consumer. Orders referred to in this sub-use case (and in UC-6.2 as well) are Adhoc orders as described on OAIS page 2-10 (section 2.3.3). Event Based Orders are addressed by use case UC-6.5.
 * The OAIS model makes separate references to "query requests" and "report requests". Because both requests draw on the data management database and follow similar workflows, they have been grouped together in this use case as an "Information Request" for simplicity. Contrast with an "order request" which requests delivery of a DIP, or an "assistance request" which request help.
 * }
 * The OAIS model makes separate references to "query requests" and "report requests". Because both requests draw on the data management database and follow similar workflows, they have been grouped together in this use case as an "Information Request" for simplicity. Contrast with an "order request" which requests delivery of a DIP, or an "assistance request" which request help.
 * }