| Esc3300 | |
| Sep 17 2016, 10:29 AM |
| F18489724: Screen Shot 2018-05-23 at 13.17.26.png | |
| May 23 2018, 12:53 PM |
Some statements suggested through the primary sources tool violate property constraints.
Currently, it seems that users of the Primary Sources have no way of knowing that through the tool itself.
Some seem to have no awareness at all that they may need to check statements before adding them.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T145930 Primary Sources tool suggests (and adds) statements violating constraints | |||
| Open | None | T148152 Field value matching needs to check for regular expression P1793 before suggestion |
I agree, but I think this should be handled at the data level, not at the tool one.
In Wikidata, constraint violation checks are already performed at the data level. See screenshot below, taken from https://www.wikidata.org/wiki/Q312387.
