Page MenuHomePhabricator

Add “no bounds” constraint
Closed, ResolvedPublic


As a data maintainer I want to be able to find problematic values that have a explicitly defined bound but should not. I want to be able to define per property if it should take bounds or not.

We should have a new constraint type No bounds for quantity properties that are about non-physical quantities without uncertainty. This is in fact a substantial fraction of Wikidata quantity properties. Since use of bounds indicates uncertainty and we cannot use novalue for bounds, we need to indicate the absence of uncertainty by using no bounds at all, rather than ±0 bounds.

Transferred to phabricator from wikidata.

See README for the steps to add a new constraint type.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 13 2017, 5:32 PM

Do you think some properties that are definitely physical might also need the opposite, a constraint that says the values should always have uncertainty? In that case we could perhaps merge the constraint types into one, and have a parameter that determines whether values should have bounds or not…

Restricted Application added a project: User-Ladsgroup. · View Herald TranscriptApr 4 2018, 10:41 AM

Change 425332 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[mediawiki/extensions/WikibaseQualityConstraints@master] Add “no bounds” constraint

Change 425332 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Add “no bounds” constraint

@Lucas_Werkmeister_WMDE @Ladsgroup would be <3 if you could show me on a test system.

Change 427900 had a related patch set uploaded (by Lucas Werkmeister (WMDE); owner: Lucas Werkmeister (WMDE)):
[mediawiki/extensions/WikibaseQualityConstraints@master] Add NoBoundsChecker in DelegatingConstraintCheckerTest

Change 427900 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Add NoBoundsChecker in DelegatingConstraintCheckerTest