Handling of packages on re-ingest
|Google Code Legacy ID:||Pull Request:|
There is an AIP re-ingest edge case that Archivematica does not handle well. To reproduce:
- Create an AIP that has zipped packages which have not been extracted.
- When re-ingesting the AIP, choose to extract the packages and delete the packages.
Result: the AIP will have both the extracted contents and the packages. Both will be reflected in the METS file but the packages will not have any of the re-ingestion events associated with them, because from the dashboard's point of view, they shouldn't have existed any longer.
Possible solutions to this:
- do not support this workflow by throwing some kind of error during re-ingest to inform the user.
- if we implement PREMIS 3, the directories that contain the extracted objects could be treated as intellectual entities and have re-ingest events associated with them.
- others possibly?