AIP Batch Export (CPP-006)

Change history	Comments
CPP-Identifier	CPP-006
CPP-Label	AIP Batch Export
Author	Micky Lindlar
Contributors	Bertrand Caron, Juha Lehtonen, Mikko Laukkanen
Evaluators	Matthew Addis, Maria Benauer
Version 1.0.0 - 2025-08-29	Milestone version
Version 1.1.0 - 2026-03-26	Migration to XML
Version 1.2.0 - 2026-07-24	Added a step group for steps specific to a single AIP, steps renumbered accordingly.

1. Description of the CPP

As part of an exit strategy, the TDA batch exports Information packages and all associated Metadata in a manageable format/structure for Ingest into another TDA.

Inputs and outputs

Input(s)

Data

AIP(s)
File(s)

Metadata

Storage Metadata Information (Identifier of AIP to be exported, including to AIP versions)
Target location for export

Documentation/guidance

Contractual Documentation for batch export (for service providers, if applicable)
AIP specification
Exit Scenario Plan
Documentation of Export AIP (supported target structure and format)

Output(s)

Data

External copies of one or several complete AIPs

Metadata

Only Metadata contained in AIPs

Definition and scope

While the TDA manages Information packages across their life cycle, stores them as AIPs, and delivers them as DIPs to its consumer, it also needs to plan for situations in which an export of AIPs becomes necessary.

Scenarios that require an AIP Batch Export include, but are not limited to:

Exit Scenario: The TDA changes a major part of its system infrastructure, such as the digital preservation workflow software or the database.
Succession Planning: The TDA ceases to exist and needs to hand over its archival holdings to a successor.
Additional External Storage: The TDA wants to store additional offline copies of their AIPs. The AIP export will create a physical AIP as opposed to a logical one. This includes e.g. Metadata which might be kept in a database to be written into an XML or JSON File.
Disposal: If the TDA decides to dispose data (e.g. as part of Re-Appraisal) the data might be handed over to an external entity such as a different TDA that wants to preserve it. The AIP likely contains a level of information richness (e.g. in form of versions and full audit trails) that the DIP format of the TDA does not offer.
External Request for Export: An external entity (e.g. a customer for a digital preservation service) might request the data preserved by the TDA for use cases such as verification of provenance information.

This CPP may export 1-n AIPs including all AIP versions from the TDA to a storage location external to the archival storage. The target location can be located externally (e.g. an external SFTP server) or internally (e.g. to a different network share). The process makes no assumption as to the type of storage exported to (e.g. disk, tape).

The exported AIP should include all available information where possible (i.e. contain all Files and all accompanying Metadata). In addition to Descriptive, Structural, Administrative and Technical Metadata, this includes any Provenance metadata which might exist and describes any events undertaken on the Object during its lifespan within the TDA.

The format and structure of the exported AIP should be documented including an explanation of all internal identifiers or schemas that might be used within. This documentation needs to be provided as a sidecar File with the AIP Batch Export.

Process description

Trigger event(s)

Trigger Event	CPP-identifier
AIP is requested from external entity (e.g. customer for digital preservation service)
Succession plans are applied to transfer custody of Objects to another TDA
The TDA extends bit-level preservation capabilities and creates new (internal or outsourced) copies of AIPs (e.g. to implement geographically distributed storage or to copy AIPs to an offline storage system)
The TDA changes its system and all Information packages need to be exported (i.e. Exit scenario)
The TDA has flagged data for disposal and the AIPs are to be handed over to an external entity

Step-by-step description

No		Input	Steps	Output
sequence
1			Receive list of AIPs to be exported
2		Target structure and format of exported AIP	Optional: If multiple target structures and formats are supported:Set export to transform exported AIP to desired structure and format
3		List of AIPs to be exported	Select AIPs to be exported in TDA (e.g. by creating a set based on AIP identifiers and AIP version identifiers, if applicable)	Inventory of AIPs
				Inventory of AIP versions
				Location of information belonging to AIPs and AIP versions
4		Inventory of AIPs	Optional: Depending on handling method for updates in TDA:For each AIP: lock AIP to avoid it being updated during export	Locked location of source AIP
4		Inventory of AIPs versions		Locked location of source AIP
5	sequence - For each AIP in inventory list: Copy AIP to target location.
	5.1	Inventory of AIPs	Create logical structure for AIP
		Inventory of AIPs versions
		Storage Metadata Information
	5.2		Write logical structure to target location	Logical structure tree of exported AIPs
	5.3		Copy Files to target location	Files in logical structure tree of exported AIPs
	5.4	Database query for AIP	If (additional) Metadata is stored in other place tha AIP (e.g., database): collect all other information belonging to AIP (Metadata)	All information belonging to AIP
	5.5	Result of Database query for AIP	If (additional) Metadata is stored in database, transform Metadata into target format and write to target location, add export as provenance information into Metadata File during transformation	Metadata File(s) in target location
	5.5	Mapping for export of selected Metadata from database to flat Metadata		Provenance information in metadata File(s)
	5.6	Inventory of AIPs	The AIP in the target should be verified, including Files and Metadata to ensure it is complete and correct ´ (e.g. using checksums)	Number of Files matches (step 5.8)
		Inventory of AIP versions		All checksums match (step 5.8)
		List of Files (excluding Metadata files) at target location		Alert that number of Files do not match
		Fixity Metadata from source AIP		Alert that any of the File checksums does not match
	5.7	AIP ID	Optional: Depending on handling method for updates in TDA:Release lock on AIP.	Released lock
	5.8	Files in target location	Optional: If required:Perform additional repacking of Files at target location to meet target structure and format of exported AIP (e.g., tarball)
	5.8	Target structure and format of exported AIP
6		Documentation of Export AIP (supported target structure and format of exported AIP)	Add documentation to target location	Documentation of Export AIP (supported target structure and format of exported AIP
7		Inventory of AIPs	Document export in audit trail	Audit trail for export

Rationale(s) and worst case(s)

Rationale	Impact of inaction or failure of the process
When a TDA is closed down, it will have to pass data on to another TDA as part of succession planning. This might have to happen on short notice.	Data is lost.
When a TDA acts as a service provider, data will have to be exported in bulk to those who are subscribing to the service.	Data owner potentially loses control over data.
If a TDA is using external services and systems, e.g. for storing and preserving its AIPs, then it may need to exchange or transfer AIPs to or from third-party services and systems.	Data is lost, data can't be efficiently transferred between TDAs and preservation services.

2. Dependencies and relationships with other CPPs

Dependencies

CPP-ID	CPP-Title	Relationship description
CPP-001	Checksum Generation and Recording	Fixity metadata is used to verify the integrity of data written into the exported AIP.
CPP-002	Checksum Validation	To ensure the integrity of the data during transport from the TDA storage, the exported Files' checksums need to be verified.

Other relations

Relation	CPP-ID	CPP-Title	Relationship description
Not to be confused with	CPP-017	Disposal	By default, batch export does not remove the content from the TDA.
Not to be confused with	CPP-025	Enabling Access	Access is typically granted to the DIP which may be different from the AIP (e.g. the DIP may only present the last version or one of several Representations). The AIP contains all preservation Metadata which a DIP may not.
Affected by	CPP-021	AIP Versioning	Versioning impacts how the export will have to be run and where and how information about the versions may be found. In addition a policy might determine if only the last or all versions should be exported.
Affinity with	CPP-011	Replication	Replication creates new parallel copies of AIPs within a TDAs archival storage. AIP Batch Export exports AIPs to external locations.

3. Links to frameworks

Certification

Certification framework	Term used in framework to refer to the CPP	Section
CTS Link	"Technical aspects of business continuity, disaster recovery and succession planning"	R15 Technical InfrastructureOrganisational aspects are covered in R03 Continuity of Service
Nestor Seal Link	Export	C12 Crisis / successorship management
ISO 16363 Link	Export	4.3.5Also touched in 3.1.2.2 "The repository shall monitor its organizational environment to determine when to execute its succession plan, contingency plans, and/or escrow arrangements."

Reference Document	Term used in framework to refer to the process	Section
OAIS Link	/	The process is not described in OAIS but one of its purposes, Succession Planning, is briefly mentioned in 3.3.6 "Follows establised preservation policies and procedures".
PREMIS Link	/	/

4. Reference implementations

Publicly available documentation

Institution	Organisation type	Language	Hyperlink
TIB – Leibniz Information Centre for Science and Technology and University Library, DE	National library Non-commercial digital preservation service Research infrastructure Research performing organisation	English	https://wiki.tib.eu/confluence/spaces/lza/pages/93608980/Export+and+exit+scenario
CSC – IT Center for Science Ltd., FI	Non-commercial digital preservation service	Finnish	https://urn.fi/urn:nbn:fi-fe2024051731943 (section 13)
Archivematica, CA	Digital preservation system	English	ihttps://www.archivematica.org/en/docs/archivematica-1.17/user-manual/archival-storage/archival-storage/#downloading-an-aip