UC-6.4

From Archivematica
Revision as of 15:16, 4 September 2009 by Evelyn McLellan (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Main Page > Requirements > OAIS Use Cases > UC-6 Access > UC-6.4 Co-ordinate Administration Update Request

[edit] UC-6.4 Co-ordinate Administration Update Request

Summary
Number

UC-6.4

Name

Co-ordinate Administration Update Request

Context

UC-6 Access

Sub-Use Cases

None

Overview

Co-ordinate Access Activities receives a request from Administration>Archival Information Update for a DIP and sends the request to Generate DIP. DIP is received from Generate DIP and sent to Administration>Archival Information Update

Actors
  • Co-ordinate Access Activities
  • Administration>Archival Information Update
  • Generate DIP
Description
Preconditions

[possibly an Administartion use case related to Archival Information Update]

Trigger
  • UC-4.? Administration>Archival Information Update sends a DIP request to Generate DIP
Successful outcome

Co-ordinate Access Activities sends DIP to Deliver Response

Steps
  1. Co-ordinate Access Activities receives a dissemination request from Administration>Archival Information Update (OAIS s 4.1.1.7, p 4-15)
  2. Co-ordinate Access Activities evaluates resources available to respond to request (OAIS s 4.1.1.7, p 4-15)
  3. Co-ordinate Access Activities sends dissemination request to Generate DIP (OAIS s 4.1.1.7, p 4-15)
  4. Co-ordinate Access Activities receives DIP from Generate DIP (OAIS s 4.1.1.7, p 4-15; OAIS Figure F-1: Composite of Functional Entities)
  5. Co-ordinate Access Activities sends DIP to Deliver Response (OAIS Figure 4-7: Functions of Access; OAIS Figure F-1: Composite of Functional Entities)
Exceptions
Documentation
Citations

OAIS s 4.1.1.7, p 4-15

The Coordinate Access Activities function provides a single user interface to the information holdings of the archive. … The Archival Information Update function in Administration also submits dissemination requests to obtain DIPs needed to perform its update functions. Other special request types are allowed, but are not detailed. 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…. It will then transfer the request to Data Management or to the Generate DIP function for execution. …

Diagrams
Notes
  • Does user authorization (Step 3) need to happen, or is it assumed that Administration requests have de-facto authorization?
  • Presumably, Administration has specific requirements about how the DIP is formed in order for it to be able to update/migrate it and re-submit it to ingest. Where are these requirements specified?
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox