Wikidata:Database reports/Complex constraint violations/P2302

Complex constraint violations report for property constraint (discussion, uses, items, changes): constraint applicable to a Wikidata property

Data time stamp: (UTC)

The report is generated based on the settings on Property talk:P2302.

Updates overwrite this page. Some may already be fixed since the last update: check RecentChangesLinked.

The report can include false positives. No need to "fix" them.

"allowed units constraint", "integer constraint" and "no-bounds constraint" must only be used on properties with a Quantity datatype edit

"allowed units constraint", "integer constraint" and "no-bounds constraint" must only be used on properties with a Quantity datatype
Only properties with a quantity (Q29934271) datatype should have allowed units constraint (Q21514353), integer constraint (Q52848401) and no-bounds constraint (Q51723761) applied.
0 violations
Query time: 0.15 s


"Commons link constraint" must only be used on properties with a CommonsMedia, GeoShape, TabularData or String datatype edit

"Commons link constraint" must only be used on properties with a CommonsMedia, GeoShape, TabularData or String datatype
Only properties with a CommonsMedia (Q29934260), GeoShape (Q42742911), TabularData (Q42743260) or Wikibase string datatype (Q29934246) datatype should have Commons link constraint (Q21510852) applied.
0 violations
Query time: 0.12 s


"contemporary constraint" must only be used on properties with an Item datatype edit

"contemporary constraint" must only be used on properties with an Item datatype
Only properties with an Wikibase item (Q29934200) datatype should have contemporary constraint (Q25796498) applied.
0 violations
Query time: 0.12 s


"value-type constraint" must only be used on properties with an Item, Property or Lexeme datatype edit

"value-type constraint" must only be used on properties with an Item, Property or Lexeme datatype
Only properties with an Wikibase item (Q29934200), Wikibase property (Q29934218) or Wikibase lexeme (Q51885771) datatype should have value-type constraint (Q21510865) applied.
0 violations
Query time: 0.17 s


"allowed qualifiers constraint" and "required qualifiers constraint" must only be used on properties that have a scope of "as main value" edit

"allowed qualifiers constraint" and "required qualifiers constraint" must only be used on properties that have a scope of "as main value"
Properties with a property constraint (P2302) value of either allowed qualifiers constraint (Q21510851) or required qualifier constraint (Q21510856) must also have a property constraint (P2302) value of property scope constraint (Q53869507) with qualifier property scope (P5314) having the value as main value (Q54828448).
74 violations
Query time: 1.70 s

"one-of constraint" and "none-of constraint" are incompatible edit

"one-of constraint" and "none-of constraint" are incompatible
If one-of constraint (Q21510859) is defined as a constraint, then none-of constraint (Q52558054) must not be defined.
9 violations
Query time: 0.11 s

"single-value constraint", "single-best-value constraint" and "multi-value constraint" are incompatible edit

"single-value constraint", "single-best-value constraint" and "multi-value constraint" are incompatible
Only one of the following constraints must be defined for a property: single-value constraint (Q19474404), single-best-value constraint (Q52060874) or multi-value constraint (Q21510857).
25 violations
Query time: 5.64 s

Preferred values are forbidden edit

Preferred values are forbidden
Due to nature of constraints, making any specific constraint as preferred makes no sense and breaks tools that use wdt:P2302 in SPARQL queries.
0 violations
Query time: 0.81 s


Constraint fully disallows usage of property edit

Constraint fully disallows usage of property
Incorrectly filled "property scope" and "allowed-entity-types" constraints will mark all usage of statement as violation
7 violations
Query time: 0.95 s