Wikidata:Contact the development team

From Wikidata
Jump to: navigation, search
Shortcut: WD:DEV

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 2015/03.

Why are the triangles vanished[edit]

so that I cannot move up or down the claims/statements. This happens with all items, with Safari and FF. Oursana (talk) 23:04, 10 February 2015 (UTC)

I thought these were broken. They will probally return. Sjoerd de Bruin (talk) 23:13, 10 February 2015 (UTC)
Thank you. Taking long? Oursana (talk) 01:49, 11 February 2015 (UTC)
Sjoerddebruin is correct. Ordering as a whole was pretty badly broken. We'll bring it back as part of the statement section redesign. Hopefully won't be too long. --Lydia Pintscher (WMDE) (talk) 07:11, 11 February 2015 (UTC)
Sorting vanished without any announcement. That's bad. The feature was not well implemented but could be used if you know the trick (page reload). --Succu (talk) 22:14, 12 February 2015 (UTC)
Yes. That was my fuckup. I'm sorry about that. It simply slipped through that this was going to be in this deployment and not the next one :( --Lydia Pintscher (WMDE) (talk) 07:44, 13 February 2015 (UTC)
„My fuckup“. I don't think so. I think not many people do care about sorting. Is there any chance to get an API call to reorder claims without to rewrite the entirely item? --Succu (talk) 22:58, 19 February 2015 (UTC)
How about skipping the sorting based on items to sorting based on user interface? I mean why not let the user let define the order of properties and every item is sorted according to some predefined or later to some user defined rules? Sorting should be a job for machines not for the users. For sure it is not convenient to have date of birth (P569) separated from place of birth (P19) and after date of death (P570). Sorting items is very time consuming and there are no general rules for it, so it is very much left to the taste of users. De gustibus non est disputandum (this is a very old rule and in general a very usefull one). --Giftzwerg 88 (talk) 23:37, 19 February 2015 (UTC)
If you can come up with a decently sorted list of all properties based on which _all_ items should be sorted I'd personally love to make this work. I am just not sure we can agree on this list. If we can I think that would be the best solution. --Lydia Pintscher (WMDE) (talk) 11:16, 1 March 2015 (UTC)
Is there any kind of order in the resonator tool? For persons we can follow the steps of the "Missing properties" tool. I´m quite sure Magnus has some kind of preference we can use as long as there are no user defined algorithms for sorting. At least we then have just one kind of sorting instead of completely unsorted items. May be a hand full of users can discuss the predefined order and make a proposal that works for most users at a later stage to refine the system. --Giftzwerg 88 (talk) 12:09, 5 March 2015 (UTC)

First one has to distinguish the type of item, for persons I propose the sort order:

- see also tl:Person properties, with changing positions (views should be last, General n0.7, and family no.4) -

  1. image (P18)
  2. position held (P39)
  3. followed by (P156)
  4. follows (P155)
  5. occupation (P106)
  6. field of work (P101)
  7. employer (P108)
  8. award received (P166)
  9. doubles titles (P1130)
  10. singles titles (P1131)
  11. father (P22)
  12. mother (P25)
  13. spouse (P26)
  14. cohabitant (P451)
  15. child (P40)
  16. brother (P7)
  17. sister (P9)
  18. stepfather (P43)
  19. stepmother (P44)
  20. relative (P1038)
  21. godparent (P1290)
  22. date of birth (P569)
  23. date of baptism in early childhood (P1636)
  24. date of death (P570)
  25. place of birth (P19)
  26. residence (P551)
  27. location of creative working (P937)
  28. place of death (P20)
  29. location of burial (P119)
  30. grave picture (P1442)
  31. cause of death (P509)
  32. manner of death (P1196)
  33. killed by (P157)
  34. surname (P734)
  35. given name (P735)
  36. birth name (P1477)
  37. name in native language (P1559)
  38. pseudonym (P742)
  39. instrument (P1303)
  40. voice type (P412)
  41. position played on team (P413)
  42. shooting handedness (P423)
  43. languages spoken or published (P1412)
  44. convicted of (P1399)
  45. canonization status (P411)
  46. religion (P140)
  47. sexual orientation (P91)
  48. ethnic group (P172)
  49. affiliation (P1416)
  50. member of (P463)
  51. participant of (P1344)
  52. member of sports team (P54)
  53. country for sport (P1532)
  54. member of political party (P102)
  55. noble family (P53)
  56. noble title (P97)
  57. honorific prefix (P511)
  58. military branch (P241)
  59. commander of (P598)
  60. conflict (P607)
  61. military rank (P410)
  62. educated at (P69)
  63. academic degree (P512)
  64. doctoral advisor (P184)
  65. doctoral student (P185)
  66. student of (P1066)
  67. student (P802)
  68. official residence (P263)
  69. coat of arms image (P94)
  70. coat of arms (P237)
  71. feast day (P841)
  72. notable works (P800)
  73. filmography (P1283)
  74. pet (P1429)
  75. signature (P109)
  76. recording of the subject's spoken voice (P990)
  77. country of citizenship (P27)
  78. sex or gender (P21)
  79. instance of (P31) human (Q5)
  80. Commons category (P373)
  81. Commons Creator page (P1472)
  82. BMLO (P865) (alpabetical)
  83. GND identifier (P227)
  84. VIAF identifier (P214)
  85. LCNAF identifier (P244)
  86. NTA identifier (Netherlands) (P1006)
  87. VIAF identifier (P214)

Oursana (talk) 00:56, 11 March 2015 (UTC)

Makes no sense to me, Oursana. --Succu (talk) 10:34, 11 March 2015 (UTC)
Sorting= A logical order for given informations gets important as we have more claims and it is easier to quickly find the information/claim you need. Oursana (talk) 11:10, 11 March 2015 (UTC)
Sure, but I see no logic in your proposal. Grouping claims (basic/extended/authority/mediawiki related/ etc.) via statements on properties could be a start. Options to filter the UI view another. --Succu (talk) 21:51, 11 March 2015 (UTC)
This is doing the sorting based on classes. As I said above I am against doing that because it opens a _huge_ can of worms. We need a list that works for everything. --Lydia Pintscher (WMDE) (talk) 10:35, 11 March 2015 (UTC)
But the items e.g. (persons, works, organizations) have different applicable properties anyway.
For better overview perhaps one could also think about main/basic informations, which are always shown and supplementary informations which are shown foldable on demand Oursana (talk) 11:10, 11 March 2015 (UTC)
Just an interesting though, but you could probably start by bunching different claim types (number (with units), date, string, item) together. --Izno (talk) 21:10, 11 March 2015 (UTC)
As we see now with instance of (P31) colors also help to mark properties and group of properties. This could be extended.
I am really waiting for the sorting Oursana (talk) 19:23, 25 March 2015 (UTC)

Suggest list bug[edit]

While adding several qualificators in one operation, the suggest list for property name and value holds multiple "ещё" (in Russian UI, "more" in English). See screenshot for P966 value editor — nine qualificators added → nine "ещё". The childish bug... It should be fixed.

PS: I use Chrome v. 41.0.2272.89 -- Sergey kudryavtsev (talk) 13:13, 19 March 2015 (UTC)

PS2: It's related to not only Commons File editor, but wikidata item editor too. -- Sergey kudryavtsev (talk) 13:29, 19 March 2015 (UTC)

I just tried and I can not reproduce this in Chrome. Can someone else please try? I might be missing something. --Lydia Pintscher (WMDE) (talk) 11:04, 21 March 2015 (UTC)

Ok, especially for you i switch to Deutsch UI. There is step-by-step instruction:

  1. Open Q19152057 (Q19152057). Scroll to the end, locate "Ausgabe (Edition)" = "Neue Gedichte (1. Auflage, 1844)" and press "bearbeiten".
  2. Press [Qualifikator hinzufügen]
  3. Type "Se", wait for dropdown list (note one "mehr"), select "Seite(n)", type 61 as value.
  4. Press [Qualifikator hinzufügen]
  5. Type "Di", wait for dropdown list (note two "mehr"), select "Digitalisat", paste "Neue Gedichte (Heine) 061.gif", wait for dropdown list (note two "mehr")
  6. Press [Qualifikator hinzufügen]
  7. Type "U", wait for dropdown list (note three "mehr"), select "URL", paste "".
  8. Press [Qualifikator hinzufügen]
  9. Type "Vor", wait for dropdown list (note four "mehr"), select "Vorgänger", paste "Q19152057", wait for dropdown list (note three "mehr"), select "Das ist eine weiße Möve..."
  10. Press [Qualifikator hinzufügen]
  11. Type "Nac", wait for dropdown list (note four(?) "mehr"), select "Nachfolger", paste "Q19598414", wait for dropdown list (note three(?) "mehr"), select "Daß du mich liebst, das wußt’ ich..."
  12. Press "speichern". The end!

You can try on next, Q19152057 (Q19152057):

  • Seite(n) = 62
  • Digitalisat = Neue Gedichte (Heine) 062.gif
  • URL =
  • Vorgänger = Q19152057
  • Nachfolger = Q19598531

The full TOC of Neue Gedichte von Heine is in User:Sergey kudryavtsev/Wikisource#Новые стихотворения, page number you can get in linked pages of German Wikisource. -- Sergey kudryavtsev (talk) 05:40, 22 March 2015 (UTC)

PS: My experinent shows that number of "mehr" is not arithmetical progression, there is more factors realted to this bug. Sorry, but i'm a professional programmer with 19 years experience... ;-) -- Sergey kudryavtsev (talk) 05:51, 22 March 2015 (UTC) PS2: You may email me for additional information, i can send screenshots or something else... -- Sergey kudryavtsev (talk) 06:02, 22 March 2015 (UTC)

Thanks a lot for the detailed steps. I could now reproduce it. I have filed phabricator:T93571. --Lydia Pintscher (WMDE) (talk) 10:24, 23 March 2015 (UTC)

Remove bug[edit]

If you edit a property, open the section for the value, delete the contained text of the value and then push remove, the message "Removing…" is shown, but then it hangs. The value is not removed when the item is reloaded. --Giftzwerg 88 (talk) 09:23, 22 March 2015 (UTC)

Thanks. I can reproduce the issue and have filed phabricator:T93570 for it. --Lydia Pintscher (WMDE) (talk) 10:10, 23 March 2015 (UTC)

Property-valued property[edit]

How can one to enter property as a target of a property? By label? By number? By "p119"? By "P:P119"? I've tried these all but I've failed to add location of burial (Q18857007) main property (P1687) location of burial (P119). --Infovarius (talk) 18:20, 25 March 2015 (UTC)

It worked for me (by name). The problem there might have been that one can't switch over from "no value" to "custom value". --- Jura 18:24, 25 March 2015 (UTC)

Male not seen[edit]

I have been clearing some of the Wikidata:The Game/Flagged items and adding 'instance of:human', 'sex or gender:male' to lots of items and it really could be easier.

If an item has no statements then when you click to add a statement the software doesn't suggest any properties. Can you please suggest instance of (P31) and subclass of (P279) and maybe part of (P361). I think nearly all items should have one of these.

When you type 'male' in the value box for sex or gender (P21) then male ( Q6581097) doesn't appear anywhere in the search suggestions - you have to use the 'more' button to scroll down to find it on the second page. This seems wrong. Surely the search function should know that male ( Q6581097) is one of the most used values on wikidata - especially for this property. Filceolaire (talk) 05:12, 26 March 2015 (UTC)

Yeah. We're looking into it. --Lydia Pintscher (WMDE) (talk) 13:50, 26 March 2015 (UTC)

Cannot add a label[edit]

With the new header design, I can't add a label to an item. When I click on [edit], the text "No label defined yet" stay in grey and I can't edit it. — Ayack (talk) 08:08, 26 March 2015 (UTC)

You can change all labels, description and aliases in the "In more languages" box which is slightly below the "No label defined yet" box. - Hoo man (talk) 09:08, 26 March 2015 (UTC)
You're right, thanks. I hadn't seen it. It is not user friendly at all... :/ — Ayack (talk) 15:09, 26 March 2015 (UTC)

Copy / paste from quick search widget no longer put item's uri[edit]

Hi, I don't know if it's a feature of a bug but it breaks some of my usecase, so I mention it here : when I dragged/dropped from item suggestion box, the URI of the item where pasted into the discussion text, for example.

Now I get this kind of results Earththird planet closest to the Sun in the Solar System

Is it wanted ?

I used to made some changes such that {{Q'}} templates family could use uris as parameters and it was convenient to just drag/drop ... it's not possible with current code ear (Q7362) (View with Reasonator). (but it seems that I can "copy link url", which is also cool, maybe more convenient). TomT0m (talk) 12:13, 27 March 2015 (UTC)

I can look into it but to be honest it is not very high on the priority list :/ --Lydia Pintscher (WMDE) (talk) 15:33, 27 March 2015 (UTC)


Hello. Sorry to ask again but I just wanted to know if you have scheduled something for the implementation of the quantity datatype with unit. I know you have your own priorities but it is often a little frustrating to discuss about WD potentials with WP contributors and at the end of the discussion to have to say "please wait until the development of WD allowing the addition of values with unit." (see en:Wikipedia_talk:WikiProject_Chemistry#Paper: Wikipedia Chemical Structure Explorer). Thanks Snipre (talk) 12:44, 27 March 2015 (UTC)

Daniel worked on the backend. That is only missing a minor thing. After that the user interface part is still to be done. --Lydia Pintscher (WMDE) (talk) 15:34, 27 March 2015 (UTC)
Ok, thanks. The UI is not the main feature we are looking for. We can use bots to manage data import on small data sets. Snipre (talk) 16:09, 27 March 2015 (UTC)

cache-problem when adding label?[edit]

In James Ferguson (Q445158) I now tried to add a new label to the item about James Ferguson. I could not directly change the label, since the software claimed another item had the same label and description. I then changed the sv-description (which maybe was wrong) and thereafter tried to change the label. I could not do that directly, I had to reload the page several times before I was able to add the new label. -- Innocent bystander (talk) 03:07, 30 March 2015 (UTC)