UC-4.7

Main Page > Vancouver Digital Archives > Requirements Analysis > UC-4 Administration > UC-4.7 Activating Requests

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

UC-4.7 Activating Requests
UC-4.7 Activating Requests UC-4 Administration None Activating Requests issues periodic dissemination requests for Consumers based on previously registered dissemination triggers.
 * colspan="2" style="background-color:#E0FFFF;"|Summary
 * Number
 * Number
 * Number
 * Name
 * Name
 * Context
 * Context
 * Sub-Use Cases
 * Sub-Use Cases
 * Overview
 * Overview
 * Actors
 * Activate Requests
 * Access>Coordinate Access Activities
 * colspan="2" style="background-color:#E0FFFF;"|Description
 * Preconditions
 * Trigger
 * Event driven request received
 * Successful outcome
 * Steps
 * 1) Activate Requests maintains records of event-driven requests (OAIS Page 4-12, s. 4.1.1.5)
 * 2) Activate Requests periodically compares event-driven request records the contents of the archive to determine if all needed data is available (OAIS Page 4-12, s. 4.1.1.5)
 * 3) Activate Requests generates an order and sends a dissemination request to Access>Coordinate Access Activities if needed data is available (OAIS Page 4-12, s. 4.1.1.5; Figure F-1: Composite of Functional Entities)
 * 4) Activate Requests generates an order and sends a dissemination request to Access>Coordinate Access Activities if a Consumer specified period has elapsed (OAIS Page 4-12, s. 4.1.1.5; Figure F-1: Composite of Functional Entities)
 * 5) Activate Requests generates an order and sends a dissemination request to Access>Coordinate Access Activities if a Consumer specified event has elapsed (OAIS Page 4-12, s. 4.1.1.5; Figure F-1: Composite of Functional Entities)
 * Successful outcome
 * Steps
 * 1) Activate Requests maintains records of event-driven requests (OAIS Page 4-12, s. 4.1.1.5)
 * 2) Activate Requests periodically compares event-driven request records the contents of the archive to determine if all needed data is available (OAIS Page 4-12, s. 4.1.1.5)
 * 3) Activate Requests generates an order and sends a dissemination request to Access>Coordinate Access Activities if needed data is available (OAIS Page 4-12, s. 4.1.1.5; Figure F-1: Composite of Functional Entities)
 * 4) Activate Requests generates an order and sends a dissemination request to Access>Coordinate Access Activities if a Consumer specified period has elapsed (OAIS Page 4-12, s. 4.1.1.5; Figure F-1: Composite of Functional Entities)
 * 5) Activate Requests generates an order and sends a dissemination request to Access>Coordinate Access Activities if a Consumer specified event has elapsed (OAIS Page 4-12, s. 4.1.1.5; Figure F-1: Composite of Functional Entities)
 * 1) Activate Requests periodically compares event-driven request records the contents of the archive to determine if all needed data is available (OAIS Page 4-12, s. 4.1.1.5)
 * 2) Activate Requests generates an order and sends a dissemination request to Access>Coordinate Access Activities if needed data is available (OAIS Page 4-12, s. 4.1.1.5; Figure F-1: Composite of Functional Entities)
 * 3) Activate Requests generates an order and sends a dissemination request to Access>Coordinate Access Activities if a Consumer specified period has elapsed (OAIS Page 4-12, s. 4.1.1.5; Figure F-1: Composite of Functional Entities)
 * 4) Activate Requests generates an order and sends a dissemination request to Access>Coordinate Access Activities if a Consumer specified event has elapsed (OAIS Page 4-12, s. 4.1.1.5; Figure F-1: Composite of Functional Entities)

OAIS Page 4-12, s. 4.1.1.5 "The Activate Requests function maintains a record of event-driven requests and periodically compares it to the contents of the archive to determine if all needed data is available. If needed data is available, this function generates a dissemination request that is sent to Access. This function can also generate orders on a periodic basis where the length of the period is defined by the Consumers or on the occurrence of an event (e.g., a database update)."
 * Exceptions
 * colspan="2" style="background-color:#E0FFFF;"|Documentation
 * Citations
 * colspan="2" style="background-color:#E0FFFF;"|Documentation
 * Citations
 * Citations
 * Citations
 * Diagrams
 * colspan="2" style="background-color:#E0FFFF;"|Notes
 * This may tie in to the City's "Open data initiative" as it seems to provide a mechanism through which updated data sets can be disseminated when available.
 * }
 * colspan="2" style="background-color:#E0FFFF;"|Notes
 * This may tie in to the City's "Open data initiative" as it seems to provide a mechanism through which updated data sets can be disseminated when available.
 * }
 * This may tie in to the City's "Open data initiative" as it seems to provide a mechanism through which updated data sets can be disseminated when available.
 * }
 * }