MigrationValidator Actor/Service

[revgum]

Periodically, (maybe a background job running a daily rake task?) check all Work that has been published to OD2, but hasn't been validated.

• Using Work type, query for validations
  • Evaluate metadata existence on OD2
  • Evaluate attached files/children and metadata existence on OD2
• If validations pass, then update the Work to mark it as validated

[revgum]

see #23

[lsat12357]

can we break this into maybe two pairs of actor/service? one to check the metadata and one to check files. maybe more if there are other things to break out and check. relationships?

[lsat12357]

This is mostly done. At the moment, the VerifyWorkService records the output of each verifier service in the migrator work, but there is no var in the work that shows this status. If the output is empty of errors, it would easy to add a Verified: success/errored to the migrator work env. The batch reporter in verification mode checks for the errors, it could be modified to also report this status.
Based on what happened with OD1 migration, we may get to the point where we choose to ignore some problems, and save fixes for cleanup activity; in that case, what would the status be, and how would it be updated.