Add constraint checking?

[Swpb2]

I don't know how practical this is (e.g. in terms of server load), but it would be great to get some warning if an edit being commanded will violate a constraint. I've done a bit of this in a script I have wrapping wikibase-cli, but I'm not necessarily doing it in the most efficient way, since I'm not much of a programmer. But I'll share what I've done if it would be of any help.

Thanks!

[maxlath]

Sure, you're welcome to share what you have already done!

[Swpb2]

Happy to, for what it's worth. First, I've sacrificed up-to-date-ness for speed: rather than querying for constraints with every edit command, I check against a couple of CSV files that I update periodically. Here are my queries for scope constraints (https://qlever.dev/wikidata/z9kQWF) and allowed qualifiers constraints (https://qlever.dev/wikidata/nnntjY).

My script is attached: it's powershell (I know...) so you'll have to change the file extension if you want to run it. The relevant bits are on lines 20-36 and 158-213. (The CSV it takes as input is generated by https://qlever.dev/wikidata/eCEtu1)

manual_migrate.txt

[maxlath]

Haven't looked deep into it, but that looks like some quite elaborated behavior, I don't know how much of that we can do in a case-agnostic way 😅. Maybe a better fit would be to have templates (see examples) that could be coupled to a specific use-case and set of constraints, rather than trying to generalize it in wikibase-cli core?