Bug #6599

DSpace transfer type asks quarantine user decision despite preconfiguration to skip

Added by Courtney Mumma over 6 years ago. Updated over 1 year ago.

Status:DuplicateStart date:04/15/2014
Priority:HighDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Google Code Legacy ID: Pull Request:
Sponsored:No Requires documentation:

Description

DSpace transfer type asks quarantine user decision despite preconfiguration to skip
Discovered in VIU COPPUL sandbox


Related issues

Related to Archivematica - Bug #6868: Fix preconfigured choices for normalization regression Duplicate 06/19/2014
Related to Archivematica - Bug #10216: Pre-set normalization option ignored if access directory ... Verified 08/17/2016
Duplicated by Archivematica - Bug #7237: Default quarantine configuration ignored for DSpace trans... Duplicate 09/15/2014

History

#1 Updated by Justin Simpson about 6 years ago

  • Assignee set to Holly Becker
  • Target version changed from Release 1.2.0 to Release 1.3.0

there are 2 quarantine nodes in the microservice chain links. Assigning to Holly to assess, after 1.3.0

#2 Updated by Holly Becker about 6 years ago

Previously, preconfigured choices were based on the name of the node. This was fixed to enable the updated file identification. However, quarantine has multiple nodes and the new UUID-based preconfigured choices do not work for the alternate nodes.

To fix this, the quarantine nodes (currently 05f99ffd-abf2-4f5a-9ec8-f80a59967b89 and 755b4177-c587-41a7-8c52-015277568302) need to be merged. Currently they appear to be separate because one sets a DSPACE specific magiclink. The DSPACE specific behaviour could be handle by using Transfers.typeOfTransfer, or by using UnitVariables (and the UnitVariable could be set earlier, before DSPACE merges with the common workflow).

This fix will probably be part of a larger project to clean up the Transfer MicroServiceChainLinks.

#3 Updated by Sarah Romkey almost 6 years ago

  • Target version changed from Release 1.3.0 to Release 1.4.0

#4 Updated by Evelyn McLellan about 5 years ago

  • Priority changed from Medium to Low
  • Target version deleted (Release 1.4.0)

Not currently working but is a low priority. Removing 1.4.0 as target release.

#5 Updated by Justin Simpson about 5 years ago

  • Priority changed from Low to High
  • Target version set to Release 1.4.0

I think we need this in the 1.4.0 release, to support automation of dspace ingests.

#6 Updated by Justin Simpson about 5 years ago

  • Status changed from New to In progress
  • Assignee changed from Holly Becker to Justin Simpson
  • Target version changed from Release 1.4.0 to Release 1.5.0

There is a workaround that can be used in 1.4.0, - supply a processingMCP.xml with the transfer, that includes the uuid of the quarantine task.

I will update this ticket with the required xml snippet after testing, and then re-assign to a dev for a longer term solution (refactor mcsl's) in next release.

#7 Updated by Sarah Romkey over 4 years ago

  • Target version deleted (Release 1.5.0)

#8 Updated by Justin Simpson almost 3 years ago

  • Subject changed from DSpace transfer type asks quarantine user decision despite preconfiguration to skip - AM 1.1 to DSpace transfer type asks quarantine user decision despite preconfiguration to skip
  • Target version set to Release 1.7.0

This is still happening in release 1.6.1. The workaround still works:

include this xml in the a processingMCP.xml file included with a transfer:

    <!-- Skip quarantine DSpace transfer -->
    <preconfiguredChoice>
      <appliesTo>05f99ffd-abf2-4f5a-9ec8-f80a59967b89</appliesTo>
      <goToChain>d4404ab1-dc7f-4e9e-b1f8-aa861e766b8e</goToChain>
    </preconfiguredChoice>

A fix was added to cover a similar use case, described here: https://projects.artefactual.com/issues/10216
But that fix does not cover this case.

#9 Updated by Justin Simpson almost 3 years ago

  • Related to Bug #10216: Pre-set normalization option ignored if access directory used added

#10 Updated by Justin Simpson almost 3 years ago

  • Assignee deleted (Justin Simpson)
  • Target version deleted (Release 1.7.0)

unassigned still, not sponsored, not making it into 1.7.0 release.

#11 Updated by Sarah Romkey over 1 year ago

  • Status changed from In progress to Duplicate

Also available in: Atom PDF