When we save constraint violations or external mismatches in a violation table, the table has to be always up to date, which is quite difficult since many, many changes at many, many different places could lead to a change in the status of a claim (both compliance --> violation and violation --> compliance).
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Invalid | None | T102763 [Task] Hooks to keep violations table up to date. | |||
Invalid | None | T105042 [Task] Add column exception to violation table |
Event Timeline
Comment Actions
As far as I’m aware, WikibaseQualityConstraints currently does not save constraint violations at all: they are always re-checked each time the special page is loaded or the API is called. And at least as far as I can tell from a quick glance, WikibaseQualityExternalValidation doesn’t either. So I’m lowering the priority for now and moving to Backlog, since this seems to be more a reminder for when we actually save violations than a task that needs to be done now.