Difference between revisions of "AIP re-ingest"
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
*Generating new DIP | *Generating new DIP | ||
| + | =New micro-services= | ||
| + | |||
| + | ==Basic micro-services for all workflows== | ||
| + | |||
| + | *Retrieve AIP from storage | ||
| + | *Place AIP in transfer directory | ||
| + | *Extract AIP and run BagIt checks | ||
| + | *Approve AIP re-ingest | ||
| + | *Re-use existing UUIDs | ||
| + | *Generate UUIDs for new objects | ||
| + | *Generate new METS file/update METS file | ||
| + | *Generate/update AIC or replace existing AIP | ||
Revision as of 19:33, 31 October 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
- Updating rights metadata
- Adding new metadata files
- Adding new submission documentation
- Adding new digital objects
- Deleting digital objects
- Redoing format identification/validation
- Redoing metadata extraction
- Redoing preservation normalization
- Generating new DIP
New micro-services
Basic micro-services for all workflows
- Retrieve AIP from storage
- Place AIP in transfer directory
- Extract AIP and run BagIt checks
- Approve AIP re-ingest
- Re-use existing UUIDs
- Generate UUIDs for new objects
- Generate new METS file/update METS file
- Generate/update AIC or replace existing AIP