Bug #705

Quarantine will not run scripts on files that have been run through before.

Added by Courtney Mumma almost 12 years ago. Updated almost 9 years ago.

Status:VerifiedStart date:
Priority:MediumDue date:
Assignee:Austin Trask% Done:

0%

Category:-
Target version:Release 0.5
Google Code Legacy ID:archivematica-50 Pull Request:
Sponsored: Requires documentation:

Description

The reason this is a problem is that sometimes we'll ask producers to
resubmit SIPs if they fail a manifest check or an integrity check prior to
Quarantine.

[g] Legacy categories: Ingest, Component-Quarantine

History

#1 Updated by Austin Trask almost 12 years ago

can you please detail the steps your taking? so I can reproduce.. thanks!

#2 Updated by Courtney Mumma almost 12 years ago

From Glenn:
My memory from the first time this happened:
1) Copy /SIP_1_0 from /sharedfolder to /quarantine (using "paste into folder")
2) file browser shows that the files in /quarantine/SIP_1_0 are locked
2) Let quarantine period run out; files are automatically removed from /quarantine to
/normalizeMe (but folder /SIP_1_0 is left behind in /quarantine); FITS and ClamAV
reports appear in /accessionrecords
3) Manually delete the empty folder /quarantine/SIP_1_0
4) Copy the /SIP_1_0 from /sharedfolder to quarantine again
5) file browser shows files in /quarantine/SIP_1_0 are not locked
6) Quarantine period runs out
7) FITS/Clam reports are not created, files are not moved to /normalizeMe

Note - I tried reproducing it again, but it did not behave the same way the second
time. I'm continuing to test

#3 Updated by Evelyn McLellan almost 12 years ago

  • Target version changed from Release 0.4 to Release 0.5

[g] Labels added: Milestone-Release-0.5
[g] Labels removed: Milestone-Release-0.4

#4 Updated by Evelyn McLellan almost 12 years ago

  • Status changed from New to Verified

Fixed in 0.5.

Also available in: Atom PDF