If using a custom processingMCP.xml file in my transfer, the "Include default SIP processingMCP.xml" should not appear in the Ingest tab, because the default is not included.
Current behaviour
Currently, this microservice appears and is lit up as green as if it were. A user would reasonably misunderstand this to think that their custom processing configuration was being ignored and replaced.
Steps to reproduce
Set up a transfer with a custom processingMCP.xml file (this can be done by adding this file to the top-level of a directory you wish to transfer).
Run through the Transfer tab and into the Ingest tab
You should see this:
Your environment (version of Archivematica, OS version, etc)
1.8, CentOS
For Artefactual use:
Please make sure these steps are taken before moving this issue from Review to Verified in Waffle:
All PRs related to this issue are properly linked 👍
All PRs related to this issue have been merged 👍
Test plan for this issue has been implemented and passed 👍
Documentation regarding this issue has been written and it has been added to the release notes, if needed 👍
Expected behaviour
If using a custom processingMCP.xml file in my transfer, the "Include default SIP processingMCP.xml" should not appear in the Ingest tab, because the default is not included.
Current behaviour
Currently, this microservice appears and is lit up as green as if it were. A user would reasonably misunderstand this to think that their custom processing configuration was being ignored and replaced.
Steps to reproduce
Set up a transfer with a custom processingMCP.xml file (this can be done by adding this file to the top-level of a directory you wish to transfer). Run through the Transfer tab and into the Ingest tab
You should see this:
Your environment (version of Archivematica, OS version, etc)
1.8, CentOS
For Artefactual use: Please make sure these steps are taken before moving this issue from Review to Verified in Waffle: