Shortcut: WD:DEV

Wikidata:Contact the development team

From Wikidata
Jump to navigation Jump to search

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 2018/09.






a query

for deletions

for comment


for permissions


for deletion

and imports



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

Monolingual string language code ("cnr")[edit]

Please add "cnr" for Q7700307#P1705. I found it on the enwiki article about Montenegrin (Q8821).
--- Jura 11:54, 25 January 2018 (UTC)

I've created T185800 for this and patch will follow soon. But before it can be merged, approval by LangCom is needed. Mbch331 (talk) 10:30, 27 January 2018 (UTC)
@Millosh: what do you think ? It's a request for a language code at Wikidata (not a new wiki/interface language).
--- Jura 17:20, 28 January 2018 (UTC)
It's a valid language code (per [1]) and I see no reason why it shouldn't be added. --Millosh (talk) 19:14, 2 February 2018 (UTC)
Is that a personal statement or an official statement from the langcom? If the latter, please add a statement to phab:T185800. Mbch331 (talk) 20:15, 2 February 2018 (UTC)
@Mbch331: thanks for the patch. I think you can go ahead with it @Millosh: is the m:Language_committee#Current member knowledgeable about this language (or closely related ones). --
--- Jura 07:20, 3 February 2018 (UTC)
@Jura1: My part of the work is done anyway. I don't have the right to merge patches. That's only to the WDME devs. I'm just a volunteer dev that submits patches. Mbch331 (talk) 07:23, 3 February 2018 (UTC)
  • It still needs to be addressed.
    --- Jura 10:33, 12 March 2018 (UTC)
    • I've added a comment to the ticket that there is Langcom approval. Mbch331 (talk) 13:02, 12 March 2018 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Patch for T185800 has been merged. Next passing of the train it will be live. Mbch331 (talk) 18:42, 15 March 2018 (UTC)

{{Section resolved|1=--Lydia Pintscher (WMDE) (talk) 08:23, 23 April 2018 (UTC)}}

  • Finally, what was it?
    --- Jura 11:14, 24 April 2018 (UTC)
We're still working on solving this issue. It's a tough one. Lea Lacroix (WMDE) (talk) 12:24, 24 April 2018 (UTC)
  • It actually works. So what was needed to make it work?
    --- Jura 09:42, 1 May 2018 (UTC)
    • Still open.
      --- Jura 09:00, 31 May 2018 (UTC) --- Jura 09:42, 1 May 2019 (UTC)

Placement in identifier section[edit]

To detail a point brought up earlier, is it possible to add an option to place statements of a few properties (e.g. P1036, sample use: Q64#P1036) in the identifier section of pages (in the sample Q64#identifiers). Currently the sort seems to be based exclusively on datatype.
--- Jura 06:52, 17 February 2018 (UTC)

Why not simply change P1036 to external-id datatype? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:51, 17 February 2018 (UTC)
Dewey Decimal Classification (P1036) is not an identifier but classifier. An identifier identifies an unique instance of class. In contrast, a classifier is used to tag all instances of a class. For example the code 813.54 means American narrative prose from 1945 to 1999. If P1036 is an identifier, we would add that code to the item about the class of American narrative prose from 1945 to 1999. But since P1036 is used as classifier, we add the code to all instances of that class. --Pasleim (talk) 14:10, 17 February 2018 (UTC)
would be more useful to have such classes on Wikidata and to use this property only on the class item. This would allow us to encode the class definition as statements in Wikidata and to infer instances automatically, for example with {{Implied instances}}. Or to add automatically the statements in the class item to the explicit instances of it without having to put the logic into the bot (or an out wiki inference rule). author  TomT0m / talk page 14:17, 17 February 2018 (UTC)
In one sense, certainly; but we have plenty of other external-id properties on Wikidata that "identify" classes of things. Do we really add Dewey codes to every item about a book with that code? The examples on the property page certainly do not suggest that. I also note that, in the property proposal, User:Merrilee of OCLC said "The Dewey identifiers are just that -- identifiers... I had an in depth conversation with the Dewey Editor, Michael Panzer, last week and this use of Dewey identifiers as free for all to use lines up with his understanding as well.". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:17, 17 February 2018 (UTC)
  • I think the datatype of one or the other properties for which this can apply should be discussed elsewhere. I think there is a general need for this.
    --- Jura 08:24, 20 February 2018 (UTC)
  • It is currently possible to create a section based on a list of datatypes or on a list of properties but not both. And I don't think we can spend time on it without having a good reason why these properties can't just be converted to external identifier. --Lydia Pintscher (WMDE) (talk) 16:26, 7 March 2018 (UTC)
    • What could we do about exact match (P2888)? There are obviously some that could be converted, but others that can't. There is also the group of identifiers that emerged during the conversion discussion and remained with string datatype.
      --- Jura 08:54, 13 March 2018 (UTC)
      • I'd say as a next step the discussions about the remaining ones need to be concluded. I am not sure what they are held up on. --Lydia Pintscher (WMDE) (talk) 10:45, 15 March 2018 (UTC)
        • Even for the ones that are already in the "not to be converted section", some are identifiers and have formatter urls. BTW exact match (P2888) has url datatype and I think it should be in the identifier section.
          --- Jura 11:34, 15 March 2018 (UTC)
          • @Lydia Pintscher (WMDE): can we move ahead with this?
            --- Jura 07:01, 19 April 2018 (UTC)
            • I am not sure what I can do. It needs editor consensus and then I can move ahead with scheduling the conversion. Or am I missing something? --Lydia Pintscher (WMDE) (talk) 08:25, 23 April 2018 (UTC)
              • What would you want to convert exact match (P2888) into?
                --- Jura 11:15, 24 April 2018 (UTC)
                • It seems fine to me as it is but I might be missing something. In general this is a decision I'd like the editors to come to rough consensus on and if that doesn't work I can make a decision but only then. It takes me time to get into the details of the discussion and make the right overall decision and I'd rather not do that if not absolutely needed. --Lydia Pintscher (WMDE) (talk) 09:45, 26 July 2018 (UTC)
                  • Other than you, I don't think anyone wanted to convert exact match (P2888) to another datatype (currently URL). The request here is to place it in the identifier section. The same goes for some of the properties with string datatype. It seems fairly trivial as a request. I get the impression that Wikidata development might have been absorbed by lexemes.
                    --- Jura 07:56, 27 July 2018 (UTC)
  • Seems this is still open.
    --- Jura 09:05, 31 May 2018 (UTC)
    --- Jura 11:15, 24 April 2019 (UTC)

Formatter url and string datatype[edit]

A problem brought up further up on this page. It seems that this works sometimes and sometimes it doesn't. What's is the development status on this? I think ideally this would work as for "external id"-datatype when the url is set on a property.
--- Jura 08:30, 20 February 2018 (UTC)

I checked and it is possible to do. Can you give me 2 or 3 examples where this would hold and not be an external identifier? I need to look into some of the details because of the RdF export before someone can work on it. --Lydia Pintscher (WMDE) (talk) 10:59, 15 March 2018 (UTC)
Full list:
--- Jura 11:41, 15 March 2018 (UTC)
Ok should be doable. Can you open a ticket for it? Or Léa? --Lydia Pintscher (WMDE) (talk) 14:34, 13 April 2018 (UTC)
Léa? That would be helpful. Apparently, I can't write tickets. Besides, I surely wouldn't find it if someone had already opened one.
--- Jura 14:53, 13 April 2018 (UTC)
done, phabricator:T192188 --Pasleim (talk) 00:25, 14 April 2018 (UTC)

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Lydia Pintscher (WMDE) (talk) 08:26, 23 April 2018 (UTC)
  • The point that might be missing in the phab ticket is that when the formatter url is qualified with a regex, then this should be taken into account. What would be the next steps?
    --- Jura 11:17, 24 April 2018 (UTC)
  • Seems this is still open.
    --- Jura 09:05, 31 May 2018 (UTC)
    --- Jura 11:15, 24 April 2019 (UTC)

Some annoying little bugs[edit]

  • When you click "Edit" in the "Other sites" box, focus is not set to the input field. You have to click in it to type "Commons". Tab is not working either. By the way, since no other site is available in this is box, and will not be in the next years (if I'm not wrong), "Commons" should be filled in by default or at least suggested when you click in the input field.
  • When you add or modify a date statement, drop down list for precision is not translated (when loggued in French at least).
  • Sometime items take many time to load (and don't fully load when opening tab in the background) and if you click too soon on "edit" for the labels, alias and description box, you arrive on which is really annoying. Would it be possible to grey out or hide this edit link until the item is fully load?

Thanks in advance. — Ayack (talk) 09:13, 5 September 2018 (UTC)

There are other sites available in the "Other sites" section: Wikispecies, MetaWiki, MediaWiki and Wikidata itself. - Nikki (talk) 10:11, 5 September 2018 (UTC)
Ok, my bad, I've never seen them on an item. — Ayack (talk) 10:19, 5 September 2018 (UTC)
  • Another one: when you paste the name of an image with the "File:" prefix and click on publish, you've got an error message and then you can't correct the name of the file, you have to click on "cancel" and add the full statement again. — Ayack (talk) 17:00, 5 September 2018 (UTC)

Notability data for items[edit]

I'm trying to develop a measure of "notability" for Wikidata items, and I wondered what we're using to rank search results. Is that documented somewhere? Bovlb (talk) 19:55, 5 September 2018 (UTC)

Usually we use a mix of various factors for rank items. These include number of statements, sitelinks, labels, incoming links from other items. Smalyshev (WMF) (talkcontribslogs) might be able to point to the exact factors and weightings for Special:Search. --Lydia Pintscher (WMDE) (talk) 19:29, 8 September 2018 (UTC)
Lydia Pintscher (WMDE) Thanks. I have been using a very similar measure. I was thinking about switching to something based on pageviews, but I'm finding that there is some work involved in mapping that onto Wikidata items. Cheers, Bovlb (talk) 19:36, 8 September 2018 (UTC)
Right now Special:Search does not include statement rank into scoring. In fact, unless you use haswbstatement, right now even statement values are not included into Special:Search, only labels and descriptions. But this may change, see task phab:T163642. Smalyshev (WMF) (talk) 19:34, 9 September 2018 (UTC)
Smalyshev (WMF) Thanks for replying. I think we may be talking at cross purposes. When I say "rank search results", I am not referring to claim ranks (e.g. preferred, deprecated), but to the information retrieval sense, whereby search results are arranged in some order. Bovlb (talk) 23:00, 10 September 2018 (UTC)
@Bovlb: I see what you mean. We do have metrics that try to figure out if one item is "better" than the other, based on number of labels, incoming links, etc. It is not documented really, the reason being we're tweaking it from time to time so the docs will get stale pretty soon. You can look at the current profiles in the source: - look for rescoreFunctionChains there. Smalyshev (WMF) (talk) 00:12, 13 September 2018 (UTC)
(I really think this kind of thing should be influenced by pageviews. See phab:T174981 for adding the counts to WDQS.) --Yair rand (talk) 20:01, 17 September 2018 (UTC)
Thanks, @Yair rand:. That's exactly the sort of thing I'm looking for. Bovlb (talk) 20:36, 20 September 2018 (UTC)

Country and city attribution of geolocated item[edit]

I am trying to make use of GeoData API to perform aforementioned task.

I found GeoData API very clean, simple and user friendly in retrieving various data according to geo location of the item. But there are difficulties with retrieving country/city affiliation of the item. While country can theoretically be get in a single request (also not always but only if being specified and not in name format but rather by its alphabetic designation), the city is possible to be get only for items which are cities by themselves. Let's imagine I want to determine in one request providing the coordinates of the Sagrada Familia temple the name of the item and that it is located in Barcelona, Spain. As far as I understood there is no way to do that. From the second hand this information does exist for every geo tagged item and is available for example through WikiData SPARQL query service. But then I'll need to perform a second request to WikiData which I would have liked to avoid by all means.

Looking on advice on the optimal strategy to perform the desired. If not is it possible to add the country/city attributes to GeoData list=geosearch attributes?

Ideally, the location of the city should not be applied to the building, because it is not the same location. The building should have its own statement with location.
If it is not available, your solution of doing to requests seems the right way to go. Lea Lacroix (WMDE) (talk) 12:13, 17 September 2018 (UTC)

Book and Work[edit]

Here is the problem: Q56540154 and Q16529226 are Work and Book. They are two different items. There is one work and there are many books of this work issued later. Still they all use the field Wikipedia link, which is not possible to do right now. — VadimVMog (talk) 08:02, 9 September 2018 (UTC)

Hello @VadimVMog:, what do you want to do? If you want to put the same Wikipedia link in both items, it's not possible. For more details about how to structure data about books, feel free to ask Wikidata talk:WikiProject Books. Lea Lacroix (WMDE) (talk) 12:16, 17 September 2018 (UTC)

Strange work SPARQL[edit]

Hi! If I include class body of water (Q15324) and him subclass watercourse (Q355304), request working fine: [2]. But if I include only body of water (Q15324), request is dead (time stop): [3]. Мастер теней (master of shadows), 18:47, 16 September 2018 (UTC)

@Smalyshev (WMF): any idea? Lea Lacroix (WMDE) (talk) 12:17, 17 September 2018 (UTC)

Can a language in Wikimedia incubator test get wikidata code,?[edit]

Can language code [mni] of Meetei(meitei)language will be able to get Wikidata code. Awangba Mangang (talk) 16:32, 20 September 2018 (UTC)