AIP re-ingest

Main Page > Requirements > AIP re-ingest

This page documents requirements for retrieving an Archivematica AIP from archival storage and re-ingesting it for further processing.

Use cases

• Updating DC metadata (version 1.5)
• Updating rights metadata (version 1.5)
• Adding new DC metadata files (version 1.5)
• Adding new submission documentation (unsponsored)
• Adding new digital objects (unsponsored)
• Deleting digital objects (unsponsored)
• Redoing format identification/validation (version 1.6)
• Redoing metadata extraction (version 1.6)
• Redoing preservation normalization (version 1.6)
• Generating new DIP (version 1.5)

Full re-ingest

To be supported in version 1.6. Sends an AIP to the beginning of transfer to run all micro-services on AIP, and re-normalize for preservation and access if desired.

Metadata re-ingest

Supported in version 1.5. Sends an AIP to the beginning of ingest to allow user to update metadata.

Partial re-ingest

Supported in version 1.5. Sends an AIP to the beginning of ingest to allow user to update metadata and normalize for access.

New micro-services

New micro-services for all workflows

• Retrieve AIP from archival storage
• Place AIP in active transfers for processing
• Extract AIP contents and run BagIt checks
• Add approve AIP re-ingest micro-service
• Re-use existing file UUIDs
• Identify new metadata files
• Validate schemas in new metadata files
• Update METS file
• Replace AIP

METS versioning

• Versioning will be captured via METS file updates.
• METS file updates will be handled through <status>, <created> and <groupID> attributes in the various METS sections. See for example Element <dmdSec> at http://www.loc.gov/standards/mets/docs/mets.v1-9.html.
• This means that there will always only be one AIP METS file, but it will contain both superseded and current metadata and versioning information for all updates.