Difference between revisions of "AIP re-ingest"
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
=New micro-services= | =New micro-services= | ||
| − | == | + | ==New micro-services for all workflows== |
*Retrieve AIP from archival storage | *Retrieve AIP from archival storage | ||
Revision as of 13:57, 29 November 2013
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 (funded)
- Updating rights metadata (funded)
- Adding new DC metadata files (funded)
- Adding new submission documentation (not funded)
- Adding new digital objects (not funded)
- Deleting digital objects (not funded)
- Redoing format identification/validation (not funded)
- Redoing metadata extraction (not funded)
- Redoing preservation normalization (not funded)
- Generating new DIP (funded)
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
AIP 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.