Problem: Pointer file for reingested AIP has unnecessary LASTMODDATE in header

evelynPM commented 5 years ago

Expected behaviour When an AIP is re-ingested, the CREATEDATE and LASTMODDATE in the pointer file should be two different dates/times.

Current behaviour The CREATEDATE is being replaced by the current date and time. For example, .

Steps to reproduce Re-ingest an AIP and open the pointer file.

Your environment (version of Archivematica, OS version, etc) Tested on bionic.

For Artefactual use: Please make sure these steps are taken before moving this issue from Review to Done:

All PRs related to this issue are properly linked 👍
All PRs related to this issue have been merged 👍
Test plan for this issue has been implemented and passed 👍
Documentation regarding this issue has been written and it has been added to the release notes, if needed 👍

evelynPM commented 5 years ago

Hmm. Actually, the METS file is not being versioned. Ideally it should have only a CREATEDATE and not a LASTMODDATE, since it's a new file that's replacing an older one.

evelynPM commented 4 years ago

Changed title of issue because the problem is that the pointer file isn't versioned, yet it has a LASTMODDATE in the METS header. It's the same date and time as CREATEDATE. It should probably be removed.

archivematica / Issues

Problem: Pointer file for reingested AIP has unnecessary LASTMODDATE in header #885