Sep 11 2017
what part is missing?
yeah .. probably the same thing. Hadn't notice that I unfocused it though.
At Wikidata, I tried to change or add value to statements with item datatype, e.g. enter the place of birth a person. The border around the entry field changes colors (depending on whether the value meets constraints or not), but then fails to allow me to save it (cancel or remove are enabled).
Sep 6 2017
Sep 5 2017
Thanks! I will try that.
The simplicity of this approach seems convincing. It could complement number of sitelinks and statements.
Sep 2 2017
It would be good if there was a way to change this on www.wikidata.org
Aug 31 2017
To solve the initial problem, would it be possible to interpret something like:
- ($1+459.67)* 5/9
- criterion used: kelvin (Q11579)
Aug 30 2017
Situation hasn't changed with the file update of T132839#3566926
We did some experiments with https://www.wikidata.org/wiki/Property:P2370 on some of these. Maybe that's why.
- Special:SetDescription | Special:SetLabel, Special:SetDescription suggests that these two are unused
- Special:SetLabelDescriptionAliases suggests the same. Maybe the actual use isn't recorded: e.g. https://www.wikidata.org/wiki/Special:SetLabelDescriptionAliases/Q11485/en is this included?
Once in a while, one ends up on https://www.wikidata.org/wiki/Special:SetLabelDescriptionAliases as js doesn't load.
The query currently finds:
Aug 28 2017
I'm confusing things. It's not an external id .. so it would be handled by the gadget.
odd. It worked with P2536 and occasionally, I suggest to do just that.
It's not used : try https://www.wikidata.org/wiki/Property:P2536#P1630 and https://www.wikidata.org/wiki/Q15397819#P2536
I guess the dev question is if one wants simple code for this or wait for more complex use cases that might require a dedicated server
If the formatter is deprecated, it shouldn't be used at all. Once in a while a site goes down. It should be possible to mark this without deleting the statement .. I thought it was possible :(
Currently different constraints give separate sections on the reports.
As it's a limitation to the openness of Wikidata, do we need to demonstrate current abuse?
This might also apply to Wikipedia projects.
Aug 26 2017
The earlier suggestion to store GCJ02 data in a separate property seems preferable ..
and do Special:NewRichItem?prop1=P31&value1=Q5
Aug 23 2017
More at T173710
The quickest user seems to do 12000 per hour (not per minute): https://quarry.wmflabs.org/query/20823
Are these originating also in clients or initially coming from Wikidata? What triggers them?
Labels are still missing ..
I'm not sure about (2.): obviously there are descriptions with caps, possibly due to Android auto-completion, but the bulk of descriptions at Wikidata are bot generated and are unlikely to have incorrect caps.
I thought simple shouldn't be used at Wikidata and gets cleaned out regularly.
wikibase_addUsagesForPage are these new requests from client wikis? e.g. a template in some wikipedia reading labels or statements?
It seems a bit odd that people view a description "Village in Kafkanistan" and then are expected to type "village in Kafkanistan" for the item of the neighboring village
Aug 19 2017
parameter for single value constraint. Multiple values are allowed under the single value constraint if they have different values for this property
I wonder if this leads people to do descriptions starting with caps when doing mobile edits: https://www.wikidata.org/w/index.php?title=Special:RecentChanges&tagfilter=mobile+edit
If it's the same as on this, I think it broke on February 22.
Aug 16 2017
A few items (such as Q76) might be so complete that the only new statement that could reasonably be added is P570.
Here is the current frequency of properties on items with instance=film (approx. 197000):
Aug 14 2017
if entities are made, I don't think they necessarily need to be on www.wikidata.org .. Wikibase could easily run on Meta, as it does on Commons.
Aug 11 2017
Depending on the field you are trying to cover, I think wikibase:statements and wikibase:sitelinks can already do a lot (as in your sample).
It seems to be part of a series of GUI changes that deteriorated the general impression of the Wikidata Query Service.
I just want to know why we got an incompatible syntax highlighter.
@Lydia_Pintscher why was it decided to use an incompatible syntax highlighter in query service GUI? This is just confusing for users.
The recent update of the query service GUI has just too many defects. I think we'd better revert to the previous one.
Aug 10 2017
Oddly T119738 doesn't seem to impact it.
Entities where client wikis think they are subscribed to, but Wikidata doesn't dispatch any change as the entry in its list is missing.
what's the situation in the other direction ?
The nice thing about the rule is that it brings random tickets back to the top of the pile .. The only problem is that on some days there are hundreds.
How about adding a link to query server that lists them?
Maybe it's time to rise the priority of this.
Aug 9 2017
No. it's not what I saw happening. Maybe anything that was edited since the start of this should be purged.
Thanks. It works. For the above and also some others.
Aug 8 2017
About the lowercase issue, see T172642. This problem seems unrelated to the question about articles linked to redirected items.
It seems it already exists! Thanks.
Aug 7 2017
A couple of hundreds or none for a few other wikis.
this returns about 4500 for nlwiki
I think Addbot just read the same table as you.
Aug 6 2017
Looking at it closer, I also found some on eswiki:
Aug 3 2017
Is there a way to meter specifically the update channel for enwiki?
I think that was about things like https://www.wikidata.org/wiki/Template:Constraint:Person that never actually worked.
oh .. forget what I just wrote.
I inserted numbering in the task description.