As an editor, I want to see why my value triggers a constraint violation in order to create cleaner data.
As an editor, I want other editors to understand why their edits are violating constraints in order to standardise our data.
**Problem:**
When a constraint violation is triggered not enough information is provided to the editor for them to understand the issue. By providing an easier way for editors to understand the constraint violations editors will be able to standardise data modelling more easily.
@ArthurPSmith created the [constraint clarification](https://www.wikidata.org/wiki/Property:P6607) property; see the [property proposal](https://www.wikidata.org/wiki/Wikidata:Property_proposal/constraint_clarification) as a way to make Property constraints more understandable for other editors who tries to add data that violates the constraints.
This needs to be better supported in the Wikibase Quality Constraints Extension.
**Example:**
{F35841294}
**Screenshots/mockups:**
**BDD**
GIVEN an editor adds a value that triggers a constraint violation
AND there is a constraint defined for the property
AND that has a constraint clarification
WHEN the constrain violation is triggered
AND the editor clicks the flag
THEN they are able to see a message from the constraint clarification that explains why that value violates the constraints of the Property
AND they are able to rectify the value that meets the Property constraints
**Acceptance criteria:**
*
**Open questions:**
**Original ticket:**
@ArthurPSmith just created the [constraint clarification](https://www.wikidata.org/wiki/Property:P6607) property; see the [property proposal](https://www.wikidata.org/wiki/Wikidata:Property_proposal/constraint_clarification) for discussion on how it can be used to improve violation messages. Assuming the community adopts it, we should include these clarifications in constraint violation messages.