Closed mjgiarlo closed 1 year ago
Replication errors are currently reporting back to the preservationAuditWF, which is there to collect problems with the local copy, not the replicated copies. See https://argo.stanford.edu/catalog?f%5Bwf_wps_ssim%5D%5B%5D=preservationAuditWF%3Apreservation-audit%3Aerror
When preservationAuditWF is in an error state for a given druid, it cannot be further versioned.
The work in this issue involves:
These are the result codes to remove from the workflow reporter to keep replication errors out of the preservationAuditWF:
Audit::Results::ZIP_PART_CHECKSUM_MISMATCH, Audit::Results::ZIP_PART_NOT_FOUND, Audit::Results::ZIP_PARTS_COUNT_DIFFERS_FROM_ACTUAL, Audit::Results::ZIP_PARTS_COUNT_INCONSISTENCY, Audit::Results::ZIP_PARTS_SIZE_INCONSISTENCY,
Replication errors are currently reporting back to the preservationAuditWF, which is there to collect problems with the local copy, not the replicated copies. See https://argo.stanford.edu/catalog?f%5Bwf_wps_ssim%5D%5B%5D=preservationAuditWF%3Apreservation-audit%3Aerror
When preservationAuditWF is in an error state for a given druid, it cannot be further versioned.
The work in this issue involves:
These are the result codes to remove from the workflow reporter to keep replication errors out of the preservationAuditWF: