Page MenuHomePhabricator

[Task] Hooks to keep violations table up to date.
Closed, InvalidPublic


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).

Related Objects

Event Timeline

Jonaskeutel raised the priority of this task from to High.
Jonaskeutel updated the task description. (Show Details)
Jonaskeutel added subscribers: Jonaskeutel, Aklapper.
Tamslo edited projects, added Wikibase-Quality; removed Wikibase-Quality-Constraints.
Tamslo set Security to None.
Lydia_Pintscher renamed this task from Hooks to keep violations table up to date. to [Task] Hooks to keep violations table up to date..Aug 17 2015, 4:04 PM
Lucas_Werkmeister_WMDE lowered the priority of this task from High to Medium.Apr 25 2017, 10:24 AM
Lucas_Werkmeister_WMDE moved this task from TODO to Backlog on the Wikibase-Quality board.

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.