UC-4.3

Main Page > Vancouver Digital Archives > Requirements Analysis > UC-4 Administration > UC-4.3 Updating Archival Information

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

UC-4.3 Updating Archival Information
UC-4.3 Updating Archival Information UC-4 Administration None 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. Manage System Configuration sends change requests, procedures and tools to Archival Information Update (Step 11 of UC-4.2) Archival Information Update resubmits (updated) SIPs to Ingest>Receive Submission
 * colspan="2" style="background-color:#E0FFFF;"|Summary
 * Number
 * Number
 * Number
 * Name
 * Name
 * Context
 * Context
 * Sub-Use Cases
 * Sub-Use Cases
 * Overview
 * Overview
 * Actors
 * Archival Information Update
 * Manage System Configuration
 * Access>Co-ordinate Access Activites
 * Ingest>Receive Submission
 * colspan="2" style="background-color:#E0FFFF;"|Description
 * Preconditions
 * UC-1.5 Transfer of AIP to Archival Storage
 * Trigger
 * Preconditions
 * UC-1.5 Transfer of AIP to Archival Storage
 * Trigger
 * UC-1.5 Transfer of AIP to Archival Storage
 * Trigger
 * Trigger
 * Trigger
 * Successful outcome
 * Successful outcome
 * Steps
 * 1) Archival Information Update receives change requests, procedures and tools from Manage System Configuration (OAIS Figure 4-5: Functions of Administration Page 4-10)
 * 2) Archival Information Update sends a dissemination request to Access>Co-ordinate Access Activites (OAIS Page 4-11)
 * 3) Archival Information Update receives DIP from Access>Deliver Response (OAIS Figure F-1: Functions of Administration Page F-2)
 * 4) Archival Information Update updates the contents of the resulting DIPs (OAIS Page 4-11)
 * 5) Archival Information Update creates SIPs from the updated contents of the received DIPs (OAIS Page 4-11)
 * 6) Archival Information Update resubmits (updated) SIPs to Ingest>Receive Submission (OAIS Page 4-11)
 * 1) Archival Information Update creates SIPs from the updated contents of the received DIPs (OAIS Page 4-11)
 * 2) Archival Information Update resubmits (updated) SIPs to Ingest>Receive Submission (OAIS Page 4-11)

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."
 * 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 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.
 * }
 * colspan="2" style="background-color:#E0FFFF;"|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.
 * }
 * 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.
 * }
 * }