Bug #13396

AtoM does not remove transfer packages after DIP upload

Added by Dan Gillean about 1 year ago. Updated about 1 year ago.

Status:NewStart date:07/27/2020
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Archivematica integration
Target version:-
Google Code Legacy ID: Tested version:2.5, 2.6
Sponsored:No Requires documentation:

Description

Reported via the AtoM user forum, 2020-07-27: https://groups.google.com/d/msg/ica-atom-users/gzxQPpEtSHM/S7hv3XvuBwAJ

This has not yet been reproduced internally, but the user confirms recreating it in 2.5.0, 2.5.4, and 2.6.0.

When AtoM deposits a DIP in the /tmp directory (or wherever DIP upload deposits have been configured), after extracting the digital objects and linking them to the target AtoM descripitons, the source DIP package is not deleted. This could lead to disk full issues on the AtoM server over time. Ideally, part of the job managing DIP upload should include the deletion of the transfer once it's no longer needed.

To reproduce

  • First, make sure you have an AM and AtoM instance properly configured for DIP upload, and access to the server for the AtoM installation
  • Perform a DIP upload
  • Check the deposit directory (/tmp or other, depending on config) after DIP upload has completed

Error encountered

  • The source DIP transfer package is still present

Expected outcome

  • As part of the job managing DIP upload, the source DIP package should be deleted when it is no longer needed

Also available in: Atom PDF