Wikidata:Contact the development team/Archive/2017/06

This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

Wikidata:Requests for comment/Allow the creation of links to redirects in Wikidata

I think this RfC needs some comments from the developers point of view. --Succu (talk) 18:13, 30 May 2017 (UTC)

 Support I was just thinking this myself - there are several issues that have been raised that bring up development concerns:

(1) first of all, is it a significant change to allow redirects to be added as wikidata sitelinks, and are there drawbacks from the dev side to making this change (note that many editors achieve this now via a workaround)? While there have been many votes on both sides it looks like there's well over 60% in favor of making the change.

(2) second, can redirect sitelinks be treated differently somehow in the various UI's they appear - some visual indicator that it's not quite the same as a regular sitelink?

(3) is there any prospect of automatically adding links from other types of relations between wikidata items (part of and subproperties for example) to wikipedia interlanguage links?

(4) can redirect sitelinks be ignored when merging items (right now having sitelinks to the same language on two different items prevents them being merged in wikidata, but if one of them is a redirect to the other this should NOT prevent a merge)

I think that's most of the dev items but there may be some others in the comments there. I think some direct input would be helpful! ArthurPSmith (talk) 18:42, 6 June 2017 (UTC)

Sorry. It is on my todo list to write down all my thoughts on it but I didn't get to it yet :( --Lydia Pintscher (WMDE) (talk) 11:32, 7 June 2017 (UTC)

Annoying watchlist in client

This single edit affects my watchlist at Wikipedia. Nothing strange by that as such, but it fills 471 lines!!! It has been reported before, but it is now time to rise the priority of this bug! -- Innocent bystander (talk) 07:16, 2 June 2017 (UTC)

Full content of {{Collapse}} available here. --Edgars2007 (talk) 07:30, 3 June 2017 (UTC)

Missing precision

There are items with coordinates, but the precision is missing. (When editing an item through the PHP api library this is prevented due to the error message: Missing required field "precision".) Can the requirement for a precision be removed until all coordinates have a precision? A list of items with coordinates without a precision would be useful too, so they can be fixed. Mbch331 (talk) 07:52, 27 May 2017 (UTC)

Can you please provide a real-life example for this? The fact that a precision must be specified is not new (the relevant validator code is at least 2 years old). It might be that the database still contains a few cases where the precision is not set. We should fix these, but this can not be done by allowing more coordinates to have no precision. --Thiemo Mättig (WMDE) 10:55, 29 May 2017 (UTC)

A few examples with missing precisions: RSK Sanyo Broadcasting (Q843784), American Repertory Theater (Q1113755), TV Osaka (Q1324709), Strand Bookstore (Q3500024) --Pasleim (talk) 11:11, 29 May 2017 (UTC)

Can somebody make a query to find all respective items? Steak (talk) 12:16, 29 May 2017 (UTC)

It doesn't appear to be possible. The query service has precisions even when there is no precision in the data (see the above examples). I tried grepping a recent dump for '"precision":null' instead and found 105,583 items, so it doesn't look like we can fix it by hand. - Nikki (talk) 23:10, 11 June 2017 (UTC)

Representation of units in dimensionless quantities

It seems as if unitless quantities can be represented by two different data structures:

• unit: "1"
• unit: "http://www.wikidata.org/entity/Q199" (which uses 1 (Q199))

The former is implicitly set if I add a quantity claim in pywikibot and give no unit at all (e.g. claim.changeTarget(value=pywikibot.WbQuantity(site=repo, amount=someVar), summary=someString)), while the latter is the only way to store a quantity explicitly unitless (e.g. claim.changeTarget(value=pywikibot.WbQuantity(site=repo, amount=someVar, unit='http://www.wikidata.org/entity/Q199'), summary=someString)). Pywikibot complains if the explicitly given unit is not an entity URL.

Both variants of unitless quantities do not show any unit in the GUI; in SPARQL, there is some translation from "1" to "wd:Q199" active as far as I can see.

I now ran into this problem and stored a bunch of claims with explicit Q199 as a unit (second version from above), but they now show up on covi pages as violations of unitless quantities (P1082 and P1083). The following questions arise:

• Can we harmonize both types, both in the representation in entities as well as in input?
• Which way is preferred?
• Should explicit Q199 also regarded as unitless in the covi pages if {{Constraint:Units}} with parameter |list=novalue is in place? This is currently not the case, thus explicit Q199 shows up on covi pages.

Further reading: phab:T135589, Wikidata:Contact the development team/Archive/2016/05#Representation of no unit, and likely some other places.

Thanks, MisterSynergy (talk) 11:43, 10 June 2017 (UTC)

Special:WhatLinksHere broken?

Looks like new items don't get added anymore.
--- Jura 10:41, 11 June 2017 (UTC)

In the meantime, links are there. It seems that update was merely delayed.
--- Jura 16:42, 11 June 2017 (UTC)

Convert UBERON ID to external-id

Tracked in Phabricator
Task T167408

Can we convert UBERON ID (P1554) to an external-id datatype?

https://www.wikidata.org/wiki/User:ArthurPSmith/Identifiers/1

Thanks Gstupp (talk) 23:08, 7 June 2017 (UTC)

•  Support. This clearly needs to be done. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:56, 8 June 2017 (UTC)
•  Support ChristianKl (talk) 10:16, 14 June 2017 (UTC)

Lua error: not enough memory.

For forms like "{{Q|Q...}}" or "{{P|...}}" (see Talk:Q16521) --Fractaler (talk) 07:14, 16 June 2017 (UTC)

Hello,

It seems that you reached the limits of Lua here :) What exactly are you trying to do? If you're trying to create the tree of subclasses of taxon, I'm afraid it's too big. One solution could be to optimize the lua module. Lea Lacroix (WMDE) (talk) 07:56, 16 June 2017 (UTC)

Mediawiki API Service for WDQS

Could you please add ".wikisource.org" to the list of available endpoints at [1]. Though items with wikipedia sitelinks vastly outnumber those with wikisource links, it would definitively make sense to be able to cross-query with wikisource categories/templates/... Thanks. -- Nono314 (talk) 12:27, 18 June 2017 (UTC)

@Smalyshev (WMF): Lea Lacroix (WMDE) (talk) 14:44, 19 June 2017 (UTC)

 Done --Smalyshev (WMF) (talk) 18:02, 20 June 2017 (UTC)

Tabular data in SPARQL queries?

@Lea Lacroix (WMDE): Will it be possible to query tabular data in SPARQL queries? (The contents inside a .tab file, not whether an item is linked with a .tab file.) This is important in deciding how to use tabular data inside wikidata, specifically whether current statements should be moved to .tab files because they will be queried too from SPARQL, or is not advisable to do so because cannot be queried from SPARQL (please, see discussion at Wikidata:Project chat#How to use Tabular data). —surueña 05:49, 19 June 2017 (UTC)

Hello,

Unfortunately, querying tabular data in SPARQL queries will not be possible in a near future. We will work on this at some point. Lea Lacroix (WMDE) (talk) 08:50, 20 June 2017 (UTC)

Thanks Lea for the confirmation, then we need to have this into mind when considering the adequate usage of tabular data inside Wikidata, being more conservative until SPARQL queries are possible. Cheers —surueña 13:53, 20 June 2017 (UTC)

Is the entity suggester up-to-date?

It seems that many relatively new properties are never suggested when adding a statement even if they are widely used. Are these suggestions updated on a regular basis? When was the last update? Thanks. — Ayack (talk) 16:14, 19 June 2017 (UTC)

Mostly updated every first week of the month, see here. Sjoerd de Bruin (talk) 16:28, 19 June 2017 (UTC)

@Sjoerddebruin: Ok, thanks. Seems that it was just a feeling then. — Ayack (talk) 16:50, 19 June 2017 (UTC)

I'm interested what property you are talking about, though. :) Sjoerd de Bruin (talk) 16:56, 19 June 2017 (UTC)

On French churches, Observatoire du Patrimoine Religieux ID (P3371) (13.380 uses) and messes.info Catholic church ID (P1644) (11.164 uses) are never suggested, while GeoNames ID (P1566) always shows up even if it's only present on 30 French churches. See Saint Joseph, Mala'efo'ou (Q29584042) for example. — Ayack (talk) 18:36, 19 June 2017 (UTC)

I think external identifiers aren't supported anymore since they moved to a different datatype. So you don't get improved suggestions for combinations of identifiers at the moment, sadly. Sjoerd de Bruin (talk) 18:45, 19 June 2017 (UTC)

@Lea Lacroix (WMDE): Do you confirm this issue? Is it tracked somewhere? Thanks. — Ayack (talk) 19:19, 19 June 2017 (UTC)

Hey, I confirm what Sjoerd said. We are working on improving the entity suggester in general, because we know that it's far from perfect, and that's why we removed this feature from the externals IDs. There is no ticket about this specific problem, but several tickets exist about entity suggester. phab:T86923 phab:T72037 Lea Lacroix (WMDE) (talk) 08:55, 20 June 2017 (UTC)

Ok, thanks. When you said you removed the feature, it means that suggested external identifiers are no longer updated, right? (because some are still proposed) — Ayack (talk) 19:17, 20 June 2017 (UTC)

ISIL (P791)

ISIL (P791) should be external-ID, not string. Is it possible to convert datatype? It's an instance of Wikidata property for a multi-source identifier (Q21264328). Thanks. --M.casanova (talk) 16:32, 21 June 2017 (UTC)

 Comment Listed in Wikidata:Identifier migration/0#Properties with serious objections to conversion. Not the first time to have been asked for: Wikidata:Project chat/Archive/2017/05#Changing the data type of properties. Matěj Suchánek (talk) 12:01, 22 June 2017 (UTC)

checkConstraints

It does not look like the Gadget is updated on changes in the constraints? In Södra Vindö (Q18333766) the P31 warns that it has a disallowed qualifier. Based on which other qualifiers were allowed already, I thought it was unproblematic to add replaced by (P1366) to the list. That was some days ago, but claims like this in "Södra Vindsö" still have warning-signs. -- Innocent bystander (talk) 16:10, 26 June 2017 (UTC)

Tracked in Phabricator
Task T169200

Yeah, the constraint templates are only imported once every few weeks… we hope to switch to constraint statements soon, which will update immediately, but we’ll probably also do another reimport of the constraint templates first. --Lucas Werkmeister (WMDE) (talk) 11:03, 29 June 2017 (UTC)

Wikidata API Rate Limit

I am having issues making edits to Wikidata using the mediawiki api. I will get an "actionthrottledtext" error with the text: "You've exceeded your rate limit. Please wait some time and try again." See here for more info. I am trying to find the actual rate limit, but cannot find it documented anywhere. Can someone point me to the proper procedures for using the API? Thanks Gstupp (talk) 17:38, 28 June 2017 (UTC)

checkConstraints

It does not look like the Gadget is updated on changes in the constraints? In Södra Vindö (Q18333766) the P31 warns that it has a disallowed qualifier. Based on which other qualifiers were allowed already, I thought it was unproblematic to add replaced by (P1366) to the list. That was some days ago, but claims like this in "Södra Vindsö" still have warning-signs. -- Innocent bystander (talk) 16:10, 26 June 2017 (UTC)

Tracked in Phabricator
Task T169200

Yeah, the constraint templates are only imported once every few weeks… we hope to switch to constraint statements soon, which will update immediately, but we’ll probably also do another reimport of the constraint templates first. --Lucas Werkmeister (WMDE) (talk) 11:03, 29 June 2017 (UTC)

Wikidata API Rate Limit

I am having issues making edits to Wikidata using the mediawiki api. I will get an "actionthrottledtext" error with the text: "You've exceeded your rate limit. Please wait some time and try again." See here for more info. I am trying to find the actual rate limit, but cannot find it documented anywhere. Can someone point me to the proper procedures for using the API? Thanks Gstupp (talk) 17:38, 28 June 2017 (UTC)