With Archivematica's current functionality, processing MCP.xml should be removed from the DIP it creates.
Current behaviour
Verified in 1.6.1, 1.7.2, and qa/0.x the DIP contains a processingMCP.xml whether or not a custom processing config is passed in the transfer directory or not. See two examples from 1.7.2 (first with default config):
Expected behaviour
With Archivematica's current functionality,
processing MCP.xml
should be removed from the DIP it creates.Current behaviour
Verified in
1.6.1
,1.7.2
, andqa/0.x
the DIP contains a processingMCP.xml whether or not a custom processing config is passed in the transfer directory or not. See two examples from1.7.2
(first with default config):And (custom processing added at Transfer):
Steps to reproduce
Create a DIP by selecting the appropriate normalization options in your configuration and then download it from the Storage Service afterwards.
Your environment (version of Archivematica, OS version, etc)
Docker-compose, multiple AM versions.