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 -- for example, this query for
qualifiers on P161 "cast member" executes in 16 seconds:
Alternatively, possibly even more efficiently, one could build the table
the other way round by querying which properties use each qualifier and
how often -- for example, this query for which properties use qualifier
P1810 "named as", which executes in a little over 5 seconds
; or P582 "end time" in about 48 seconds:
Basing the suggester on such a tabulation would allow for the many
properties for which no restriction on qualifiers is currently
considered; and also for many qualifiers, such as P582 "end time" or
P1480 "sourcing circumstances" which should be generically usable on
pretty much any statement, but which the community often hasn't bothered
to add to the list of specifically permitted qualifiers, because it
would make the list too long and unwieldy; and because people have had
better things to do.
On 29/08/2018 10:08, Léa Lacroix wrote:
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 appears in the
I hope that answers your question.
On 28 August 2018 at 23:24, James Heald <jpm.heald(a)gmail.com> wrote:
Interesting, but why not simply suggest the most
qualifiers for the given property?
The list of "allowed qualifiers" is often wildly incomplete; or
alternatively no such constraint is specified at all.
On 28/08/2018 14:05, Léa Lacroix wrote:
Currently, when adding a new value in the constraints section of a
property, there is no suggestion to fill the value or the qualifier. We’ve
been improving this by a few changes that are going to be deployed this
- When adding a new value in the property constraint statement, a list
of suggestions will be displayed and, all the relevant constraint
will be showed first. They will be selected among the list of
present in the statement “property constraint -> one of constraint”
constraint (P2302) <https://www.wikidata.org/wiki/Property:P2302>.
- Of course, you can still type anything you want in the field to
value. The full text search has been improved (when typing “none
you will also see “none of constraint” in the suggester)
In a very near future, we will also make the following happen:
- Same behavior for qualifiers inside the constraint statements. The
suggester will pick up the values from “allowed qualifiers constraint”
- When clicking on “add value” in the property constraint statement, a
suggester menu will directly appear (without having to click on the
The first two changes will appear on wikidata.org
on August 30th, the
following ones in the next weeks. Feel free to make some tests, and let us
know if you find a bug or something that doesn’t behave as expected.
Related tickets: phab:T199672 <https://phabricator.wikimedia.org/T199672
Wikidata mailing list
This email has been checked for viruses by AVG.
Wikidata mailing list