Problem: Storage Service package moves leave old copies behind

[replaceafill]

Expected behaviour

The Storage Service move package API endpoint removes the source package copy after successfully moving the package to the target location.

Current behaviour

If you move an AIP from a local filesystem AIP storage location to an S3 AIP storage location, the AIP is stored in the S3 bucket, but the original filesystem-based copy is left behind.

Steps to reproduce

1. Start a local Archivematica environment with a Storage Service connected to both:

   • a local filesystem AIP storage location
   • an S3 AIP storage location

2. Create a new standard transfer and store the resulting AIP in the local filesystem AIP storage location.

3. Confirm that the AIP exists in the local filesystem AIP storage location.

4. Use the Storage Service move package API endpoint to move the AIP to the S3 AIP storage location.

5. Confirm that the move request completes successfully and that the AIP package record now points to the S3 AIP storage location.

6. Confirm that the AIP object exists in the S3 bucket.

7. Check the original local filesystem AIP storage path.

8. Observe that the original local filesystem copy still exists after the successful move.

Your environment (version of Archivematica, operating system, other relevant details)

• artefactual/archivematica@27b3ad9
• artefactual/archivematica-storage-service@928ff1e

---

For Artefactual use:

Before you close this issue, you must check off the following:

• All pull requests related to this issue are properly linked
• All pull requests related to this issue have been merged
• A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
• Documentation regarding this issue has been written and merged (if applicable)
• Details about this issue have been added to the release notes (if applicable)