AIP re-ingest

From Archivematica
Revision as of 17:40, 9 December 2016 by Sromkey (talk | contribs)
Jump to navigation Jump to search

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/characterization (version 1.6)
  • Redoing metadata extraction (version 1.6)
  • Redoing preservation normalization (version 1.6)
  • Generating new DIP (version 1.5)
  • Running OCR on re-ingest (version 1.6)
  • Rerunning other micro-services (Examine Contents, Transfer Structure Report) (unsponsored)

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.

AIP re-ingest Preservation and metadata.png

Metadata re-ingest

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

AIP re-ingest workflows - Metadata only.png

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.

AIP re-ingest objects with metadata.png

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.
  • The original METS file will also be maintained as submission documentation

dmdSec

Retrieved from "https://wiki.archivematica.org/index.php?title=AIP_re-ingest&oldid=11492"