Re: [Wikidata] Better suggestions for constraint values on properties

2018-08-29 Thread Léa Lacroix
Hello James, Because we would have to calculate it and it would be very expensive in term of resources. Plus, the results may not be exactly what editors expect. With the lists of "allowed qualifiers", it's the perfect occasion to clean them up, and the community can have total control on what app

Re: [Wikidata] Better suggestions for constraint values on properties

2018-08-29 Thread James Heald
Why would it be so expensive to calculate? Surely a script could be run to execute a query for each property once a month to produce the required tabulation. Apart from a very very few properties with more than a million uses, such a query will typically execute in a lot less than 30 seconds

Re: [Wikidata] Better suggestions for constraint values on properties

2018-08-29 Thread Thad Guidry
The problem is the interface for this. A single drop-down list. In many places in Wikidata, like constraint adding, a 2 level list would be amazing. The single drop-down list for suggestions is very 1990's and there are widgets for listing suggestions that are much smarter and more helpful. Here,

Re: [Wikidata] Better suggestions for constraint values on properties

2018-08-29 Thread Thad Guidry
[image: Capture2.PNG] Or if someone worries about eating up screen space... just overlap 2nd level however much on the 1st level click...position left or right depending on parent and view window edges. -- Thad +ThadGuidry ___

Re: [Wikidata] Better suggestions for constraint values on properties

2018-08-29 Thread David Abián
I believe the criteria that has been followed is a great way of connecting what we have and what we think we should have, and seems to me better for data quality than simply suggesting the most frequently-used qualifiers. Constraints and data should converge (by changing constraints, data or both)

Re: [Wikidata] image re-use information available via a SPARQL query?

2018-08-29 Thread Lucas Werkmeister
There is a solution, but it’s a bit hacky. You can get the categories of the file via the MWAPI service [1] and then try to match those categories that denote a license (for example, a category starting with “CC-” *probably* indicates a Creative Commons license). Here’s a query using the example i