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 2019/01.






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)
    @Jura1: to update signature to hold up bot auto-archiving you can just replace the old one, learn me. --Liuxinyu970226 (talk) 11:02, 29 September 2018 (UTC)

Edit filter to track and possibly disable changes to referenced statements[edit]

Can you add something to for this type of edit? It changes a satement supported by 5 references. --- Jura 09:39, 28 December 2018 (UTC)

Hello, the abuse filters are defined by community members. I ping @Matěj Suchánek: who made a lot of them. Lea Lacroix (WMDE) (talk)
This is an endless loop. I was the one who pointed out this hasn't been possible with abuse filters... Matěj Suchánek (talk) 09:08, 30 December 2018 (UTC)
  • Matej says it can't be done with that and the signed statement feature isn't going to solve it either. --- Jura 16:51, 28 December 2018 (UTC)
Thanks for your answers. We'll follow up on that in the next weeks. Lea Lacroix (WMDE) (talk) 12:50, 30 December 2018 (UTC)
I think we need to define what we want here. Do you want an edit tag? Do you want a pop-up in the UI that nudges the editor? Something completely different? --Lydia Pintscher (WMDE) (talk) 14:59, 30 December 2018 (UTC)
My preference would be disabling such an edit but this could become another subject to glitches, misunderstandings or so. Perhaps a pop-up with a confirmation? At least for newbies. An edit tag could also work. Matěj Suchánek (talk) 16:05, 30 December 2018 (UTC)
  • It should be made possible to access these edits in the edit filters. There it can be decided what to do. In general, one can probably still add qualifiers, but shouldn't change the main value. --- Jura 08:20, 31 December 2018 (UTC)

Image can't be find with exact title[edit]

Hello, I have reported this bug a while ago and I thought it was corrected, but I have it again. When trying to add File:Route entre Barcelonnette et le col de la Cayolle (D902) -7.JPG to Q38656180, I select image (P18), paste "Route entre Barcelonnette et le col de la Cayolle (D902) -7.JPG" but can't find the right image in the list... Ayack (talk) 10:55, 8 January 2019 (UTC)

Hello Ayack, and thanks for pinging us again about this issue. We included it in our workflow for the incoming weeks. Lea Lacroix (WMDE) (talk) 08:56, 10 January 2019 (UTC)
Merci Léa ! Ayack (talk) 09:38, 10 January 2019 (UTC)

Undoing a revision leads to dupplicate of values for a statement[edit]

I can't find a bug tracker so please let me know if it is not the right place to put this issue. I undo an 'instance of' value of Q845774. It replaces this 'instance of' by the one existing at this moment (Q194188), which leads to a dupplicate since this item already had this value for this statement. 1. I think it is a wrong behaviour, the Q194188 should not have been added since it was already there. If you agree, can a fix be made? 2. I can delete one or the other but which one preferably in order to save history? Thanks for your support.

I general, the software is not preventing the user to add two times the same value in a statement. The fact that you can, by undoing an edit, arrive to the result where two values are identical in the statement, is also not prevented by the software.
Did I correctly understand your question?
Are you suggesting that the interface should not allow users to enter two times the same value in a statement?
Thanks, Lea Lacroix (WMDE) (talk) 13:38, 10 January 2019 (UTC)
Thanks for the feedback. I've nothing against the fact that a value can be set twice (I did not think about any implication at the moment) but it leads to the point where I'm not sure which one to delete (one is linked to another member edit, one is linked to my undo). I deleted the last one of the list thinking that if there is no clue then it is safe to delete whichever we want. Yes the question is answered.

Interface administrator right on test.wikidata[edit]

Hey. Could a bureaucrat on give me the interface administrator right overthere? I would like to test out some fixes related to Wikidata:Tours. --Pasleim (talk) 14:35, 14 January 2019 (UTC)

@Pasleim: Should be done now :) Let me know if you encounter issues. Lea Lacroix (WMDE) (talk) 10:46, 15 January 2019 (UTC)
Thanks. --Pasleim (talk) 10:49, 15 January 2019 (UTC)

Remove all redirects from watchlist[edit]

Hi! I'm not sure it's the right place, excuse me if it's not. I have a question about Watchlist: is there any way to remove all the redirects from the Watchlist in one click? If not, would it be possible creating it? I have more than 50k pages in my Watchlist, so I'm not able to open Special:EditWatchlist in order to manually remove them, and I don't know other ways. Thank you very much, --Epìdosis 11:21, 16 January 2019 (UTC)

Hey @Epìdosis:, I don't have the answer to this question, so I'm going to investigate and hopefully come back to you soon :) Lea Lacroix (WMDE) (talk) 10:05, 17 January 2019 (UTC)
Hello again!
So: there is no easy feature that would allow you to remove all the redirects from the watchlist. I've been looking for some alternatives you can use.
  • you can add a small css hack to your common.js, highlightling the redirects, which would help you removing them progressively when they appear in your watchlist
  • you can access the raw list of you watchlist, save it into a file, an then run a script that would query the mediawiki-API to check if each page is a redirect, and remove all of them
  • you can look at the code from the Pywikibot watchlist feature that could help you achieve that
I hope that helps a bit! Lea Lacroix (WMDE) (talk) 13:21, 17 January 2019 (UTC)

@Epìdosis: Open PetScan. Copy your raw watchlist→Other sources→insert to manual list→set wiki as Wikidata→Page properties→all namespaces→set redirects as no→Categories→choose Wikidata→Do it! The result will be your watchlist without redirects. Bencemac (talk) 09:51, 19 January 2019 (UTC)

@Bencemac: Thank you, it worked perfectly! And thank you also @Lea Lacroix (WMDE):. Bye, --Epìdosis 10:09, 19 January 2019 (UTC)