Validation Stack to Flag Problems as Warnings, not Errors, and Move them to Permanent
Ability to run the validation stack during ingest, but only flagging warnings, not errors. All IEs will be moved to the permanent repositories and if needed, the problems will be dealt with in a future stage.
Submitted by Ex Libris PM on behalf of our customers
Andreas Romeyke commented
this is a bad idea, I think. The reason to use a validation is
- to know the risk about IEs in archive
- to deny/sort broken files out
The rosetta system has already a quarantaine zone to deal with problematic files, which is the TA workbench.
The purpose of the TA is to repair broken data as early as possible in the archiving process. Moving broken files into the permanent repository contradicts this paradigm.
With best regards