Change Details

Now that the constraints are machine-readable on property pages, it is a charming idea to query constraint violations on the fly using the Wikidata Query Service. It should be possible to identify items based on various criteria, such as: * 1. French painters with any type of constraint violation on any claim * 2. French painters with a specific constraint violation (e.g. single values constraint) on any claim * 3. French painters with any type of constraint violation on a claim of a specific property (e.g. P569) * 4. French painters with a specific constraint violation (e.g. single values constraint) on a claim of a specific property (e.g. P569) * 5. And so on… Right now we only have the possibility to work on all constraint violations of a given property (via covi pages), but it is not possible to limit this to sets of items in a given topical area (such as “French painters”). It should also be possible to equip the constraint boxes on property talk pages with SPARQL links that way. Right now we have to wait for daily KrBot updates, which slows down maintenance occasionally. The idea of this task is not new and has already been mentionend by several users, but I didn’t find a phabricator task yet. Still I hope it is not a duplicate.

Now that the constraints are machine-readable on property pages, it is a charming idea to query constraint violations on the fly using the Wikidata Query Service. It should be possible to identify items based on various criteria, such as: 1. French painters with any type of constraint violation on any claim 2. French painters with a specific constraint violation (e.g. single values constraint) on any claim 3. French painters with any type of constraint violation on a claim of a specific property (e.g. P569) 4. French painters with a specific constraint violation (e.g. single values constraint) on a claim of a specific property (e.g. P569) 5. And so on… Right now we only have the possibility to work on all constraint violations of a given property (via covi pages), but it is not possible to limit this to sets of items in a given topical area (such as “French painters”). It should also be possible to equip the constraint boxes on property talk pages with SPARQL links that way. Right now we have to wait for daily KrBot updates, which slows down maintenance occasionally. The idea of this task is not new and has already been mentionend by several users, but I didn’t find a phabricator task yet. Still I hope it is not a duplicate.

Now that the constraints are machine-readable on property pages, it is a charming idea to query constraint violations on the fly using the Wikidata Query Service. It should be possible to identify items based on various criteria, such as: * 1. French painters with any type of constraint violation on any claim * 2. French painters with a specific constraint violation (e.g. single values constraint) on any claim * 3. French painters with any type of constraint violation on a claim of a specific property (e.g. P569) * 4. French painters with a specific constraint violation (e.g. single values constraint) on a claim of a specific property (e.g. P569) * 5. And so on… Right now we only have the possibility to work on all constraint violations of a given property (via covi pages), but it is not possible to limit this to sets of items in a given topical area (such as “French painters”). It should also be possible to equip the constraint boxes on property talk pages with SPARQL links that way. Right now we have to wait for daily KrBot updates, which slows down maintenance occasionally. The idea of this task is not new and has already been mentionend by several users, but I didn’t find a phabricator task yet. Still I hope it is not a duplicate.