Constraint report
Jump to navigation
Jump to search
This special page performs constraint checks on any entity you want. The entities are fetched from the live system, so every constraint violation you fix there will be instantly removed from this list.
The constraints are parsed from statements on properties each time those statements are edited, usually within a few minutes.
Result for Jean Anthelme Brillat-Savarin (Q313027)
: 3, : 4, : 2, : 2942, : 210
| Status | Property | Message | Constraint |
|---|---|---|---|
| publication date | The parameter "item of property constraint" must be one of the following: | allowed-entity-types constraint | |
| publication date | The parameter "item of property constraint" must be one of the following: | allowed-entity-types constraint | |
| house number | /^(?:^(((지하|B) )?\d{1,5}(-\d{1,5})?\.?|\d{1,5}(((-\d{1,5})?([a-zA-Z]|[а-яА-Я]|bis|ter)?)|(\\/\d{1,5}))?)$)$/u is not a valid regular expression. | format constraint | |
| Commons category | The property Commons category should not be used in this location (as qualifier). The only valid locations for this property are: | property scope constraint | |
| based on heuristic | Values of based on heuristic statements should be instances or subclasses of algorithm or reasoning (or of a subclass of them), but record linkage currently isn't. | value-type constraint | |
| based on heuristic | Values of based on heuristic statements should be instances or subclasses of algorithm or reasoning (or of a subclass of them), but record linkage currently isn't. | value-type constraint | |
| based on heuristic | Values of based on heuristic statements should be instances or subclasses of algorithm or reasoning (or of a subclass of them), but record linkage currently isn't. | value-type constraint | |
| position held | This position held statement is missing a qualifier start time. | required qualifier constraint | |
| position held | This position held statement is missing a qualifier start time. | required qualifier constraint |