Published Records validations

[ghukill]

Validations are currently at the Job level, but what about validations we may want to employ across all published Jobs/Records?

One example was notifying users if published records contained > 1 dpla_isShownAt fields. If so, that would imply duplicate records, at least insofar as what generally makes documents unique in DPLA.

Question is whether these would be:

• opinionated
  • automatic check for dpla_isShownAt field
  • possible DPLA specific
• scenario-based
  • like other validations, provide a mechanism by which validations could be applied

A key difference, might be validation across all published records. This is something that hasn't been addressed yet. All validations have been scoped to a single Record, they are not aware of Record beyond themselves.

[ghukill]

FWIW, this could be done via an published analysis job?

Pro

• workaround available now

Cons

• analysis job does not update with publishing changes
• duplication of Records for analysis job