Open main menu

Wikidata:Contact the development team

(Redirected from Wikidata:Devs)

Contact the development team

Wikidata development is ongoing. You can leave notes for the development team here, on #wikidata connect and on the mailing list or report bugs on Phabricator. (See the list of open bugs on Phabricator.)

Regarding the accounts of the Wikidata development team, we have decided on the following rules:

  • Wikidata developers can have clearly marked staff accounts (in the form "Fullname (WMDE)"), and these can receive admin and bureaucrat rights.
  • These staff accounts should be used only for development, testing, spam-fighting, and emergencies.
  • The private accounts of staff members do not get admin and bureaucrat rights by default. If staff members desire admin and bureaucrat rights for their private accounts, those should be gained going through the processes developed by the community.
  • Every staff member is free to use their private account just as everyone else, obviously. Especially if they want to work on content in Wikidata, this is the account they should be using, not their staff account.
On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2019/08.

Development plan Usability and usefulness Status updates Development input Contact the development team


Graphes no longer workingEdit

Hello, since few days, this template does not work when used with a Wikidata query : Can someone look this up ? I've lag a phabricator there . Hope it will be solved… Thanks. Bouzinac (talk) 11:37, 22 June 2019 (UTC)

Same issue with Template:Graph:Pie chart used on 100+ pages here. It only works when previewing. Ayack (talk) 16:01, 24 June 2019 (UTC)
 :-(Bouzinac (talk) 13:19, 27 June 2019 (UTC)

@Smalyshev (WMF): Is this something that could have been caused by a change on our side? Lea Lacroix (WMDE) (talk) 08:06, 2 July 2019 (UTC)

Same problem in Greek Wikipedia. Xaris333 (talk) 08:07, 10 July 2019 (UTC)

  • So what's the outcome? Who can fix it? --- Jura 04:19, 24 July 2019 (UTC)
As per comments on phab:T226250, it's unclear who is maintaining Graphoid, which makes the issue hard to be fixed. Lea Lacroix (WMDE) (talk) 07:12, 24 July 2019 (UTC)
Where do you read that? Who is handling the server logs? --- Jura 07:23, 24 July 2019 (UTC)
On this ticket is discussed who is maintaining the Graphoid service. It was unclear but since some volunteers suggested to help, I hope there will be a positive outcome. Lea Lacroix (WMDE) (talk) 08:42, 24 July 2019 (UTC)
Very bizarre as it can in fact work, if written in another fashion eg [1]Bouzinac (talk) 11:45, 24 July 2019 (UTC)
  • @Lydia Pintscher (WMDE): Can you pick this up? It's some that is broken on Wikidata itself, a WMF production website, for more than a month. Wouldn't it be up to WMF to fix (or deactivate) it? If WMF can't, maybe WMDE-Wikidata development team can help? --- Jura 11:45, 29 July 2019 (UTC)
Hello Jura,
The Wikidata team cannot take the ownership of Graphoid, because we never worked on it so far and we already have a lot on our plate. However, we will start investigating on one of the possible issues (the user-agent header to send requests to the Query Service) to help understand where the issue comes from. Lea Lacroix (WMDE) (talk) 15:29, 29 July 2019 (UTC)

Search for multiple (specific) types via wikibase:api "EntitySearch" running into 50 record limit?Edit

I'm trying to let people search for anything, as long as it's something in the popular culture like an actor, book, movie, sports team, etc. So if I search "Patriots" I should get the NFL Team and the movie The Patriot. And I think I've gotten a good start with this:

SELECT distinct ?ordinal ?item ?itemLabel ?itemDescription ?image WHERE {
  SERVICE wikibase:mwapi {
    bd:serviceParam wikibase:api "EntitySearch";
                    wikibase:endpoint "";
                    mwapi:search "Patriots";
                    mwapi:limit 1000;
                    mwapi:language "en" .
    ?item wikibase:apiOutputItem mwapi:item .
    ?ordinal wikibase:apiOrdinal true .
  ?item wdt:P31/wdt:P279* ?type.
  OPTIONAL{?item wdt:P18 ?image .}
  FILTER( ?type in (wd:Q5, wd:Q17537576, wd:Q12973014))
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
} ORDER BY ASC (?ordinal) LIMIT 100
Try it!

I'm using the EntitySearch service so that I can get the :apiOrdinal value to help sort the results for relevance, and ?type contains the whole list of parent types so that I can just use "creative work" and "sports team" as catch-alls to filter on. (The FILTER list of Q types is incomplete, I was just starting to get the test going)

But, the problem happens when you replace "Patriots" with "Fellowship". In theory I should get the book and film Fellowship of the Ring. But the only result is for the "group" Fellowship of the Ring. If you take off the FILTER, you'll see it only returns 40 records from the EntitySearch for some reason? And if you change it to "Fellowship of the Ring" it will correctly find the book and film, so the EntitySearch can find those two. But for some reason it seems like EntitySearch is capping the results to a limit of 40?

Any ideas on what's going on?

Thanks! --Thomas.lumen (talk) 15:24, 12 July 2019 (UTC)

@Smalyshev (WMF): Any idea? Lea Lacroix (WMDE) (talk) 06:09, 15 July 2019 (UTC)
You may be seeing the effects of incomplete continuation implementation, which has been fixed in but not deployed yet. Try next week after it's deployed, it may work better. If not, I'll take another look and see what's going on there. Smalyshev (WMF) (talk) 18:25, 18 July 2019 (UTC)
Thanks @Smalyshev (WMF): - Looks like the code was deployed, but if I comment out the FILTER line, and query "Fellowship" it still only returns ~45 results when there are definitely more than that. --Thomas.lumen (talk) 12:20, 24 July 2019 (UTC)
@Thomas.lumen, Smalyshev (WMF): I think MWAPI doesn’t support continuation for EntitySearch at all – in the source code, MWApiServiceCall.parseContinue() only looks at //api/continue in the response XML (with a “TODO support other options?”), but action=wbsearchentities returns a custom search-continue property. You can use the wbsearch generator instead:
SELECT DISTINCT ?ordinal ?item ?itemLabel ?itemDescription ?image WHERE {
  SERVICE wikibase:mwapi {
    bd:serviceParam wikibase:endpoint "";
                    wikibase:api "Generator";
                    mwapi:generator "wbsearch";
                    mwapi:gwbssearch "Fellowship";
                    mwapi:gwbslanguage "en";
                    mwapi:gwbslimit "max".
    ?item wikibase:apiOutputItem mwapi:title.
    ?ordinal wikibase:apiOrdinal true.
  ?item wdt:P31/wdt:P279* ?type.
  OPTIONAL{ ?item wdt:P18 ?image. }
  FILTER(?type IN (wd:Q5, wd:Q17537576, wd:Q12973014))
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
ORDER BY ASC(?ordinal)
Try it! --Lucas Werkmeister (WMDE) (talk) 16:38, 29 July 2019 (UTC)
It'd probably be good to amend MWAPI to be able to deal with custom continuations... Smalyshev (WMF) (talk) 23:12, 29 July 2019 (UTC)
@Lucas Werkmeister (WMDE), Smalyshev (WMF): So is the issue that MWAPI needs to deal with continuations? Because when I run this new version of the query with wbsearch, I still hit the 50 record cap when I remove the FILTER and so "Fellowship" doesn't pull in the movie or book in the first 50 results that come back. --Thomas.lumen (talk) 17:11, 31 July 2019 (UTC)
@Thomas.lumen: Hm, I think I didn’t think this through – it looks like wbsearch(entities), when used as a generator, doesn’t support continuation either. I’ve filed T229460 to solve this. --Lucas Werkmeister (WMDE) (talk) 18:13, 31 July 2019 (UTC)

Multilanguage labelEdit

There was not so active discussion at Wikidata:Project_chat/Archive/2019/06#Multilanguage_label. Is it possible to add such fallbacks? mul-Latn, mul-Cyrl and "mul" over all of them. --Infovarius (talk) 12:18, 17 July 2019 (UTC)

I pinged Amire80 to get his opinion. Lea Lacroix (WMDE) (talk) 10:25, 19 July 2019 (UTC)
Sounds kind of sensible, but I'd love to see a few more focused examples. --Amir E. Aharoni (talk) 11:34, 19 July 2019 (UTC)
@Lea Lacroix (WMDE): How about adding mul-Latn, mul-Cyrl and "mul" on the test-server so that we can provide focused examples better? ChristianKl❫ 20:39, 7 August 2019 (UTC)
Can you provide these examples here with text? I don't think that it makes a lot of sense to create new fallbacks on the test system if we're not sure that it will be deployed further. Lea Lacroix (WMDE) (talk) 09:31, 8 August 2019 (UTC)
Daniel Muñoz (Q5392517)->mul(Daniel Muñoz)
Entomobrya (Q10484814)->mul-Latn(Entomobrya)
Such Is the Law (Q7632782)->mul-Latn(Such Is the Law)
Surgical indications for anterior cruciate ligament reconstruction combined with extra-articular lateral tenodesis or anterolateral ligament reconstruction (Q58126952)->mul-Latn(Surgical indications for anterior cruciate ligament reconstruction combined with extra-articular lateral tenodesis or anterolateral ligament reconstruction)
Hang Lei (Q58420581)->mul-Latn(Hang Lei)
We potentially save a lot of edits when the label doesn't have to copied manually here but the name gets shown as a fallback. ChristianKl❫ 19:14, 11 August 2019 (UTC)
@Lea Lacroix (WMDE):ChristianKl❫ 10:00, 13 August 2019 (UTC)

Use a property as a link sourceEdit

In a custom Wikibase installation I would like to use a text content of a property to build a link to a page, but it seems I am unable to.
Let's say I have a property where the text is Some Page: so I tried to buld a link writing [[{{#statements:P1}}]] and expected the result to be Some Page, while in fact I am getting a plain text [[Some Page]].

I made several searches on the internet, but I failed to understand why this is not working and how to modify my approach to make it works instead. I assume I am making some fundamental error, but I am not sure what.
May I ask you if you can briefly explain to me the error or point me to the proper documentation to read to achieve this result?

Thanks --Lucamauri (talk) 15:39, 18 July 2019 (UTC)

I don't know if this method works, but I wouldn't do it because the returned item label may be different from the pagelink. Besides depending on the property there could be zero or more than one result. --Dipsacus fullonum (talk) 07:27, 22 July 2019 (UTC)
I can insure that the label is exactly as the page name and that at least a result is always present, so these are not issues. Beside that, can you please explain how to do this technically? if there is another way to reference a page, kindly just let me know. Thanks. --Lucamauri (talk) 08:35, 22 July 2019 (UTC)
The safe way is to use a lua module to access the pagelink so it can make links constructed like [[Page link|item label]]. In many projects the pagelink and the label will often be different due to disambiguation. The module can be called from a template and if the module isn't used for anything else, it can be made in a few lines of lua. --Dipsacus fullonum (talk) 19:15, 22 July 2019 (UTC)
PS. I made an example of a minimal module to create links from property values af --Dipsacus fullonum (talk) 20:19, 22 July 2019 (UTC)
Thanks @Dipsacus fullonum:, I had a look at your example and I adapted it to my own use, very helpful.
Allow me one last question: a LUA script is the only way to address this functionality or just a convenient one? I mean, could it be done in any other way? --Lucamauri (talk) 10:40, 29 July 2019 (UTC)


Our taxobox is no longer working since yesterday. Maybe this is somehow related to the drop of mw.config.get( 'wbEntity') yesterday. We use this script to activate the taxobox on WD pages. Unfortnatly there is no current maintainer of this utility. Would be great if someone could have a look. Many thanks im advance. --Succu (talk) 17:59, 25 July 2019 (UTC)

I don't think that it's related, since the script doesn't contain mw.config.get( 'wbEntity'), and the change has been done last week anyway. The Wikidata team doesn't maintain community scripts but we can have a look and try to identify the problem. Lea Lacroix (WMDE) (talk) 19:00, 29 July 2019 (UTC)
Dear Lea, I'm aware that the Wikidata team doesn't maintain community scripts. But the infobox at WD exists since 2013 (!!) a while before the Phabricator-Story Create demo infoboxes was written. For me it's obvious that this is somehow related to the drop of mw.config.get( 'wbEntity') or some other deployment rolled out that day. --Succu (talk) 20:08, 29 July 2019 (UTC)
Hi Succu, so the script needs to be updated as it was relying on wbEntity that we removed in, announcement .. here's an updated script that uses the suggested alternative `wikibase.entityPage.entityLoaded` instead . Tested on wikidata production (in browser console) on and I could see the box. --Alaa Sarhan (WMDE) (talk) 22:37, 29 July 2019 (UTC)
Great! Many thanks! I copied the code to User:Succu/taxobox.js and changed my common.js.

Achim Raschka (talk)
Andrawaag (talk)
Brya (talk)
CanadianCodhead (talk)
Christian Ferrer (talk)
Dan Koehl (talk)
Daniel Mietchen (talk)
FelixReimann (talk)
Infomuse (talk)
Infovarius (talk)
Jean-Marc Vanel
Joel Sachs
Josve05a (talk)
Klortho (talk)
Lymantria (talk)
Mellis (talk)
Michael Goodyear
Mr. Fulano (talk)
Nis Jørgensen
Peter Coxhead
Andy Mabbett (talk)
Prot D
Rod Page
Strobilomyces (talk)
Tommy Kronkvist (talk)
Tris T7 TT me
William Avery
  Notified participants of WikiProject Taxonomy --Succu (talk) 18:38, 30 July 2019 (UTC)

can't we just save over the original if it no longer works? --99of9 (talk) 22:06, 30 July 2019 (UTC)

Cannot indicate measurement unitEdit

While i types melting point (P2101) = 33,8 in erucic acid (Q413531), isn't appearing a edit box for measurement unit. Bug? The browser is 64-bit Google Chrome 75.0.3770.142. -- Sergey kudryavtsev (talk) 10:26, 2 August 2019 (UTC)

Hello. The issue is known and being fixed. — Envlh (talk) 10:35, 2 August 2019 (UTC)
@Envlh: Thank you. Please, ping me when it will be fixed. -- Sergey kudryavtsev (talk) 11:11, 2 August 2019 (UTC)

About delete itemsEdit

Hey guys. Couple weeks ago i create 2 new item for my musical group and my self.

Sadistic Divine (musical group) And my self as original member and founder of band "Hamid Sarami"

But afte 2 weeks my items was deleted I have google knowledge panel and have many fans in my country and asia You can check it out on my soundcloud or bandcamp or instagram page with this username "sadisticdivine" so my band is a famous group so this is my question. Why my items about my band myself was deleted ? I add musicbrainz and discogs id as official databass. This is my band's item page

And me

I create this items couple days So please don't remove it.

Wikidata doesn't exist for the purpose of self-promotion or a way to get into the google knowledge panel. ChristianKl❫ 20:41, 7 August 2019 (UTC)

WDQS graph view : Label that do not appear although its entity has a labelEdit

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. author  TomT0m / talk page

I noticed that in this query result the entity entity (Q35120), although it obviously has a label in english, is showed in the graph view with its entity url, unlike every other one who are showed thanks to their respective english label. Is this a weird bug ? author  TomT0m / talk page 13:13, 2 August 2019 (UTC)

Ooops my bad, I understood my mistake, I forgot to require the label for the « source » item of the graph, those with no parents. author  TomT0m / talk page 08:25, 5 August 2019 (UTC)

Native label optionEdit

Hi there! "valueview-expertextender-languageselector-label" thingy is not working properly (or at all :). Thanks for fixing it. (I have to continue my nationalist crusade of vandalism to add "Native label: Turkish (tr)" to the Turkish-language names. :) Bye. --E4024 (talk) 13:14, 2 August 2019 (UTC)

Is this issue related to phab:T229604? If so, we're working on it :) Lea Lacroix (WMDE) (talk) 14:31, 2 August 2019 (UTC)
Wow! I just wondered if anybody else was here in August and they are... Thanks guys and gals. :) --E4024 (talk) 14:44, 2 August 2019 (UTC)

Bug of search bar with 2017 source editorEdit

There is a bug when using the rapid search bar, some results are hidden, as in this screenshot :

2017 source editor and search bug

I use this to drag and drop items in the edit zone, which is pretty useful but … depending on the zoom level the first and most useful result, often, is totally hidden behind the button bar and impossible to click on, so this process is impossible. I don’t know if it’s a bug specific to the source editor on Wikidata or if it’s a general bug. author  TomT0m / talk page 16:37, 2 August 2019 (UTC)


Does wikidata have a "help desk"? The reason I'm asking is one of my edits here was reverted. I'm wondering why. If someone had edited the selection I wouldn't have thought twice about it - but reverts usually indicate something very wrong. The user who reverted is in a foreign language so I'm not sure how I would ask him or her directly. If I'm doing something wrong then I'll stop. Feel free to check my contribs and let me know - I'm on the The English wiki here Thank you for any assistance you can provide. Ched (talk) 14:07, 5 August 2019 (UTC)

  • update: I've left a message in English at the users talk page number 2 (?) Ched (talk) 14:24, 5 August 2019 (UTC)
Hello, you can ask for help on the Project Chat, but also on social networks like the Telegram group. If you're having strong disagreements with someone you can also bring it to the admins noticeboard. Lea Lacroix (WMDE) (talk)


What happens if there is an item and a Wikidata page? e.g. for Project:Village pump (Q16503)? --- Jura 16:03, 5 August 2019 (UTC)

Amir Sarabadani (WMDE) can you confirm that it will be live wiki after two weeks or this week. Regards, ZI Jony (Talk) 16:24, 7 August 2019 (UTC)
In some cases, for example on help and meta pages, the section may contain two links to Wikidata, for example on Help:Contents where there will be the “Wikidata” link (linking to d:Help:Contents) and the “Wikidata item” link (linking to d:Q914807).
The change will be announced today and will be live on August 22nd on Wikipedias. Lea Lacroix (WMDE) (talk) 07:54, 8 August 2019 (UTC)
Wouldn't it be better to display them at a separate place? When was the community consulted about this change? --- Jura 10:52, 8 August 2019 (UTC)
As someone mentioned it in the ticket and on the mailing-list, the menu bars are already full of stuff, we probably don't want to create yet another section.
This request was mentioned since 2014, we got a lot of people asking for it in the ticket, in duplicates, as well as various discussions onwiki, and recently the Basque Wikipedia implemented a script so they already have their links moved to "other projects". These are enough signals for us to move forward with the task. Lea Lacroix (WMDE) (talk) 12:01, 8 August 2019 (UTC)
Can you link the community discussion? Phabricator is hardly suitable for this and non devs generally don't participate. The Wikidata community venue is mainly Wikidata:Project chat. I'd expect the community liaison to liaise beforehand rather than just post announcements. If the request hasn't been actioned since 2014 maybe people lost interest.
The Wikidata item link is fundamentally different from a sitelink. I think it's confusing having several links to the same wiki in the sidebar. What would be the different labels that have been requested in the phab ticked? --- Jura 12:16, 8 August 2019 (UTC)
As mentioned in the announcement, the labels will stay the same, which will be "Wikidata item" for the link to the item, and "Wikidata" for the possible sitelink. Lea Lacroix (WMDE) (talk) 13:05, 8 August 2019 (UTC)
Can you reschedule this to allow Wikidata users to comment? --- Jura 13:15, 8 August 2019 (UTC)

Blazegraph bug ?Edit

select ?item ?article ?titre
    select ?item ?article ?titre {
      ?article schema:about ?item ;
               schema:isPartOf <> ;
               schema:name ?titre .
               filter not exists { ?item schema:description ?descr filter (lang(?descr) = "fr") }.
    } limit 100
  } as %pool
  include %pool .

Try it!


select ?item ?article ?titre {
      ?article schema:about ?item ;
               schema:isPartOf <> ;
               schema:name ?titre .
               filter not exists { ?item schema:description ?descr filter (lang(?descr) = "fr") }.
    } limit 100

Try it! does work in like 4 seconds.

This is basically the same query except its used in a named subquery that is just included as is in a parent subquery. I don’t really understand why this timeout in that setup. author  TomT0m / talk page 10:41, 8 August 2019 (UTC)

This also fails with a regular subquery :

select ?item ?article ?titre

    select ?item ?article ?titre {
      ?article schema:about ?item ;
               schema:isPartOf <> ;
               schema:name ?titre .
               filter not exists { ?item schema:description ?descr filter (lang(?descr) = "fr") }.
    } limit 10
  ?article schema:about ?item .
} limit 100

Try it! author  TomT0m / talk page 10:53, 8 August 2019 (UTC)

Query that timeouts, I really don't understand whyEdit

select distinct ?class {
    ?class wdt:P279* wd:Q58415929 .
} limit 1

Try it!

 – The preceding unsigned comment was added by TomT0m (talk • contribs) at 17:37, 11 August 2019‎ (UTC).

You used "*" --- Jura 18:44, 11 August 2019 (UTC)

Hello @TomT0m:

we had the same problem with queries that worked before (until about end of July), but now are running into a timeout ("java.util.concurrent.TimeoutException").

See d:Wikidata_talk:SPARQL_query_service#Query_timeout_limit_for_important_query_reached.

We also used the asterisk operator ("/wdt:P279*") for *any* number of instances (zero to unlimited/infinite) from the instance to the subclasses, like all the examples fiven in the tutorial (which are not working anymore neither):

[...] The solution: ?item wdt:P31/wdt:P279* ?class. This means that there’s one “instance of” and then any number of “subclass of” statements between the item and the class.

?work wdt:P31/wdt:P279* wd:Q838948. # instance of any subclass of work of art

First I assumed, that the query runs into an endless loop, if A is subclass of B and B is subclass of A, but i could not confirm that by viewing the tree structure (here for the class "film"):

When I removed the "/wdt:P279*" in the query, I got all films, but not the subclasses (for example d:Q18517638 was missing, since it is a "animation film"/"3D film" as subclass of "film").

When I used "/wdt:P279+", I got only the subclasses of "film", but not the instances of "film" themselves.

From my point of view, a solution could be to combine those two by using "UNION"

    ?film wdt:P31 wd:Q11424 .
    ?film wdt:P31/wdt:P279+ wd:Q11424 .

For example, to get all films released in 2019 in Germany the query would be:

SELECT DISTINCT ?film ?release ?filmLabel WHERE {
  { ?film wdt:P31 wd:Q11424. }
  { ?film (wdt:P31/(wdt:P279+)) wd:Q11424. }
  ?film p:P577 ?release_statement.
  ?release_statement (psv:P577/wikibase:timePrecision) 11 ;
    ps:P577 ?release.
  FILTER((YEAR(?release)) = 2019 )
  ?release_statement pq:P291 wd:Q183.
  FILTER(NOT EXISTS { ?release_statement wikibase:rank wikibase:DeprecatedRank. })
  FILTER(NOT EXISTS { ?release_statement pq:P400 ?platform. })
  FILTER(NOT EXISTS { ?release_statement pq:P437 ?distribution. })
  FILTER(NOT EXISTS { ?film wdt:P31 wd:Q506240. })
  FILTER(NOT EXISTS { ?film wdt:P31 wd:Q21191270. })
  SERVICE wikibase:label { bd:serviceParam wikibase:language "de". }
ORDER BY (?release) (?filmLabel)

Try it!

--M2k~dewiki (talk) 00:25, 15 August 2019 (UTC)

Добавление РФС как ссылкиEdit

Случано создал страницу РФС в викиданных. И можете создать код участника РФС для футболистов. Заранее спасибо. --Kookdans (talk) 13:15, 15 August 2019 (UTC)

  • Уведомите меня --Kookdans (talk) 13:26, 15 August 2019 (UTC)
  • И добавьте тогда профиль РФС для игоря лещюка --Kookdans (talk) 13:33, 15 August 2019 (UTC)
  • RFS --Kookdans (talk) 13:57, 15 August 2019 (UTC)
  • No uderstand me? Сan create an RFS member code for the players. Thank you in advance. Notify me And then add the profile of the RFS for Igor Leshchuk. --Kookdans (talk) 14:13, 15 August 2019 (UTC)
  • @Kookdans:, что вы хотите? Создать свойство для ссылки на РФС? --Infovarius (talk) 20:21, 15 August 2019 (UTC)
  • Infovarius, да --Kookdans (talk) 07:40, 16 August 2019 (UTC)

query.wikidata returns a Property instead of an entityEdit

Running the follwing query in

   SELECT ?item  WHERE {
     ?item wdt:P1556 "boersma.johannes".

returns 2 results:


where the first one makes no sense, since it is a "property", that does not exist, and ist just made out of the identifier of the (correct) entity Q4244119.

Probably related: in some wikidata entity profiles there is a "violated distinct values constraint" for the property wdt:P1556, indicating as conflicting values something like Qxxxxx (correct) and Pxxxxx. For example, currently:

This bug should be fixed, let me know if it's still happening. Lea Lacroix (WMDE) (talk) 08:50, 16 August 2019 (UTC)