Currently, it is not possible to define property constraints in Wikibase Cloud. Enabling the Wikibase Quality Constraints extension in Wikibase Cloud will be incredibly useful for including the values that are allowed for a particular property to help ensure that constraints are met. This is even more critical for projects with multiple users who may contribute directly in the user interface.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | Feature | None | T356571 Property constraints for Wikibase Cloud | ||
Open | Rosalie_WMDE | T378743 Prepare instances to investigate behavior of Quality Constraints if enabled as-is |
Event Timeline
For the record, I've seen several users coming from Wikidata interested in this over the past year.
On Wikidata there are also reports related to constraints which are or were done by KrBot and DeltaBot (constraint violations) so if those are part of what you are looking for they might have to be done separately. Or it might be that the latter bot could be made to work without the extension and at least give the reports. It looks like it relies on certain IDs that need to be changed and also the endpoint https://query.wikidata.org/bigdata/namespace/wdq/sparql would be more like https://furry.wikibase.cloud/query/sparql
this drives us towards feature parity with wikidata but we're unclear how low hanging task is given the huge number of entities that wikis need to have (and then be configured to use) for the extension to work
Well, that aspect is more a matter of work for the user; it looks like most of the parameters could just be entity IDs that are passed through - are they all actually required for core functionality or does it just not do those left unspecified?
The UI might be tricky, perhaps a separate Constraints tab rather than trying to shoehorn it into Features?
I think not all but at least some will be required for the functionality most people will expect. I'd also worry it would be confusing for users if one some but not all of the functionality is there
Just to note that I would appreciate this feature very much as well. It would make a huge difference for collaborative Wikibase cloud instances. – It might be true that some people will expect all of the functionality to appear at once, but most (I suppose) would already be very happy if some of the core features were available. That's certainly the case for myself. Thanks for the great work on Wikibase.cloud, by the way, I think it is an absolute game-changer for Linked Open Data.