Page MenuHomePhabricator

Name/Wording of the function: Alternative to "Constraint violations"
Closed, ResolvedPublic

Description

What should the function be called? It is currently referred as "Constraint violation" but that term has various problems imho:

  • "Constraint" may suggest that there is a clear boundary, and if that is stepped over it is always a bad thing (but the checking code can be wrong, too!)
  • "Violation" may suggest again that bad things happened like a technical problem that will occur or anger in the community will be the result.

So the frame is negative and maybe even threatening.

Another framing could he that of helpful hints that encourage the user to either improve the data on wikidata or the constraints. Which could lead to:
"Data checks", "Constraint checks", "constraint hints" or so.

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Event Timeline

How about something like: "We found the following potential issues:" ?

I like it. It may be too long, though. (What about: "Potential issues"?)

"Potential issues" it is –
Would look like

image.png (208×501 px, 26 KB)

Change 352563 had a related patch set uploaded (by Lucas Werkmeister (WMDE); owner: Lucas Werkmeister (WMDE)):
[mediawiki/extensions/WikibaseQualityConstraints@master] Update constraint violation messages

https://gerrit.wikimedia.org/r/352563

Change 352563 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Change “constraint violations” to “potential issues”

https://gerrit.wikimedia.org/r/352563

Lucas_Werkmeister_WMDE moved this task from Review to Done on the Wikidata-Former-Sprint-Board board.

This is done and merged, I just want to keep this issue open until we’ve also updated the user script on Wikidata (subpage of Jonas’ user page).