Open jens-st opened 3 years ago
jens-st
commented
2 months ago Dear Artefactual team,
it's been some time since I suggested this configuration feature to opt-out of the default validation behaviour.
Can you imagine Archivematica having such a functionality, would it be a good fit and feasible? If yes, what would it take? Can you give hints about a timeline, preconditions and requirements?
Best regards, Jens
jens-st
commented
1 week ago Dear Artefactual team,
would you tentatively (non-committally) accept a patch for this issue in case we decide to develop one?
Best regards, Jens
sarah-mason
commented
1 week ago Hi Jens,
Apologies that your message in September went unanswered. But you've asked some good questions on how best to contribute your code and it's a conversation we should absolutely have. As for your last question a few days ago, we would tentatively accept a patch for this issue if you are able to develop one.
Speaking from my previous experience with other end users, this lack of functionality has caused them to have to do an extra validation step before ingest. If you would like to talk a bit more about your previous questions regarding the contributions, please email contributors@artefactual.com.
Best wishes, Sarah Mason Contributor Success Specialist
Please describe the problem you'd like to be solved As described in preservation-planning I'd like to suggest a feature to opt out on the default format policy behaviour to regard every validation error as non-critical for archiving. Validation errors are not considered one of the Errors that fail transfers.
Some institutions have strict requirements for data quality in certain workflows. In those cases, if an error was found the transfer should not be archived but reported and later corrected by staff.
Describe the solution you'd like to see implemented I propose an additional processing configuration option like "Continue on validation error? yes/no" that retains the current behaviour by default but enables the user to opt out and have every validation error be a failed transfer. Additionally, it would be flexible enough to change the behaviour on a per-transfer basis.
Describe alternatives you've considered How to trigger a transfer failure from Validation command describes how that might be achieved but it requires changing and maintaining the file workflow.json yourself. The new environment variable ARCHIVEMATICA_MCPSERVER_WORKFLOW_FILE allows you to use your own workflow file but still has a very high requirement for knowledge about the internal workings of Archivematica (and still needs to be maintained and probably breaks on future versions).
Additional context
For Artefactual use:
Before you close this issue, you must check off the following: