UC-4.3

Main Page > Requirements > OAIS Use Cases > UC-4 Administration > UC-4.3 Updating Archival Information

UC-4.3 Updating Archival Information
Summary
Number	UC-4.3
Name	Updating Archival Information
Context	UC-4 Administration
Sub-Use Cases	None
Overview	Archival Information Update updates the contents of the archive by requesting DIPs, updating them, transforming them into SIPs, and resubmitting them to Ingest>Receive Submission.
Actors	Archival Information Update Manage System Configuration Access>Co-ordinate Access Activites Ingest>Receive Submission
Description
Preconditions	UC-1.5 Transfer of AIP to Archival Storage
Trigger	Manage System Configuration sends change requests, procedures and tools to Archival Information Update (Step 11 of UC-4.2)
Successful outcome	Archival Information Update resubmits (updated) SIPs to Ingest>Receive Submission
Steps	Archival Information Update receives change requests, procedures and tools from Manage System Configuration (OAIS Figure 4-5: Functions of Administration Page 4-10) Archival Information Update sends a dissemination request to Access>Co-ordinate Access Activites (OAIS Page 4-11) Archival Information Update receives DIP from Access>Deliver Response (OAIS Figure F-1: Functions of Administration Page F-2) Archival Information Update updates the contents of the resulting DIPs (OAIS Page 4-11) Archival Information Update creates SIPs from the updated contents of the received DIPs (OAIS Page 4-11) Archival Information Update resubmits (updated) SIPs to Ingest>Receive Submission (OAIS Page 4-11)
Exceptions
Documentation
Citations	OAIS, Page 4-11, s. 4.1.1.5 "The Archival Information Update function provides a mechanism for updating the contents of the archive. It receives change requests, procedures and tools from Manage System Configuration. It provides updates by sending a dissemination request to Access, updating the contents of the resulting DIPs and resubmitting them as SIPs to Ingest."
Diagrams
Notes
	This function is likely requesting AIP content delivered as as special configuration of DIPs which would not necessarily reach the average consumer. Consumer-bound DIPs could contain a subset of metadata used by the archive and/or a special access version of the Content Data Object (such as a compressed image or a file that has been redacted for public release), but for updating, a complete and full-sized version of the Content Data Object would be required. There is no function defined within OAIS which designs the DIP(s), and it is not made clear in OAIS if the DIP for updating is of a different design than the design(s) requested by the Consumer, but it must be.