UC-1.5

Main Page > Requirements > OAIS Use Cases > UC-1 Ingest > UC-1.5 Transfer of AIP to Archival Storage

UC-1.5 Transfer of AIP to Archival Storage
Summary
Number	UC-1.5
Name	Transfer of AIP to Archival Storage
Context	UC-1 Ingest
Sub-Use Cases	None
Overview	The AIP is transferred from Coordinate Updates to Archival Storage>Receive Data
Actors	Coordinate Updates Generate AIP Archival Storage>Receive Data
Description
Preconditions	UC-1.3 Generation of AIP
Trigger	Generate AIP sends AIP to Coordinate Updates (Step 12 of UC-1.3)
Successful outcome	AIP is transferred to Archival Storage>Receive Data and storage confirmation (including identification information) is received from Archival Storage>Receive Data.
Steps	Coordinate Updates receives AIP from Generate AIP (OAIS Figure 4-2:Functions of Ingest Page 4-5) Coordinate Updates submits AIP storage request to Archival Storage>Receive Data (OAIS Page 4-6) Coordinate Updates sends AIP to Archival Storage>Receive Data (OAIS Page 4-6) Coordinate Updates receives storage confirmation (including storage identification information) from Archival Storage>Receive Data (OAIS Page 4-6)
Exceptions	If SIP updates Descriptive Information for an AIP already in Archival Storage, this use case will not apply.
Documentation
Citations	OAIS Page 4-6 "The Coordinate Updates function is responsible for transferring the AIPs to Archival Storage ... Transfer of the AIP includes a storage request and may represent an electronic, physical, or a virtual (i.e., data stays in place) transfer. After the transfer is completed and verified, Archival Storage returns a storage confirmation indicating (or verifying) the storage identification information for the AIP. ... Data Management updates may take place without a corresponding Archival Storage transfer when the SIP contains Descriptive Information for an AIP already in Archival Storage."
Diagrams
Notes