Problem: workflow is inevitably interrupted when extraction fails

[sevein]

Please describe the problem you'd like to be solved When the user chooses to extract contents of packages via the processing config, and extraction fails with any of the packages identified within the transfer, the workflow fails and the whole transfer is rejected and marked as failed, giving no choice to continue without extraction.

Describe the solution you'd like to see implemented Introduce a new MCPClient setting EXTRACT_CONTENTS_CONTINUE_ON_ERROR which, when set to true, will force the workflow to continue processing the package at all costs.

Describe alternatives you've considered Making this configurable via processing config in the future if there is interest.

Additional context @Slange-Mhath from Bodleian has implemented this solution already in his fork: https://github.com/Slange-Mhath/AM_metadata_output_tool/pull/4. It needs more testing though. Particularly, we need to know how the workflow deals with already-extracted contents when EXTRACT_CONTENTS_CONTINUE_ON_ERROR is enabled and the workflow moves on.

---

For Artefactual use:

Before you close this issue, you must check off the following:

• [ ] All pull requests related to this issue are properly linked
• [ ] All pull requests related to this issue have been merged
• [ ] A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
• [ ] Documentation regarding this issue has been written and merged
• [ ] Details about this issue have been added to the release notes

[sevein]

We've received some feedback from a user after testing https://github.com/Slange-Mhath/AM_metadata_output_tool/pull/4:

When config variable is set to true (so continues) a transfer which has broken zip and normal zips. Transfer is successful, where normal zips are extracted fine in AIP and the broken zip is included in the AIP (with no extraction)