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)


There is a cache problem, when I rollback an edited label or description on other languages i don't see any change even I reload page on browser

Step to reproduce

  1. go to item page with wrong label or description displayed on in other languages
  2. click view history
  3. click rollback or undo
  4. return on the item you don't see any change


firefox on linux

Rippitippi (talk) 22:25, 18 February 2015 (UTC)

Hi, that is a known bug... purging the respective pages should fix it. - Hoo man (talk) 08:31, 19 February 2015 (UTC)
Purge don't fix it, only way to see right label-descriptions values in item pages is click edit on other languages, with choromium it is ok --Rippitippi (talk) 14:17, 19 February 2015 (UTC)
This sounds like a known bug of the browser software cache. I´ve reported that a long time ago.--Giftzwerg 88 (talk) 14:30, 19 February 2015 (UTC)
I don't think is only a browser bug --Rippitippi (talk) 02:48, 20 February 2015 (UTC)


this user has created four items with the same wikilink [1] invalid ID (Q19322409) invalid ID (Q19322391) invalid ID (Q19322381) invalid ID (Q19322327) --Rippitippi (talk) 02:45, 20 February 2015 (UTC)

Thank you. I will look into it. --Lydia Pintscher (WMDE) (talk) 10:12, 22 February 2015 (UTC)

Can't save edits[edit]

When I try to add new sitelinks the save link doesn't work. What am I doing wrong? Lophotrochozoa (talk) 21:40, 21 February 2015 (UTC)

You're not alone! -- Innocent bystander (talk) 08:41, 22 February 2015 (UTC)
@Lophotrochozoa: What sitelink? Of what project? To which item? Matěj Suchánek (talk) 10:00, 22 February 2015 (UTC)
@Matěj Suchánek: I think I tried to add to Q19340321, but it also happened other times. Lophotrochozoa (talk) 17:08, 24 February 2015 (UTC)
What page (on which wiki) did you try to link? Can you also paste the error you received (if any)? Cheers, Hoo man (talk) 20:29, 24 February 2015 (UTC)

Inconsistent date formats[edit]

  • English: "24 February 1463" (correct)
  • Italian: "24 feb 1463" (should be "24 febbraio 1463" instead)

--Ricordisamoa 03:48, 28 February 2015 (UTC)

This is phabricator:T50962. --Lydia Pintscher (WMDE) (talk) 11:14, 1 March 2015 (UTC)

Labels are update much more slowly than statements in Wikipedia[edit]

When adding a new statement, it usually update almost immediately in Wikipedia. But adding a label takes much longer. Compare:

  • frNihonbashi Mitsui Tower, the "Style architectural" was updated immediatley in the article.
  • fr:Intempo, the "adresse" line of the infobox still shows a Qid rather than a label, even though the label was added yesterday.

I guess it could be because the label is from another item, so it does not trigger any update in Wikipedia. You can reproduce by adding translations from articles in fr:Catégorie:Page utilisant des données de Wikidata à traduire and see that it does not update immeditely. --Zolo (talk) 14:28, 28 February 2015 (UTC)

Your guess is correct for all I know. This should be solved when we have usage tracking working on all projects. --Lydia Pintscher (WMDE) (talk) 11:18, 1 March 2015 (UTC)


There is a rdfs:comment [2] which could be pretty cool to include in the statements together with sources and qualifiers. I guess it would be like an additional comment field at the bottom of the statement, and it could contain a more verbal explanation of whats in the statement and why it is set up just like so. For example that some statistics has a discontinuity, or that the length of a road is weird because it has multiple endpoints (like European route E16 (Q642043)). To really make it freaking fun it could even contain wikitext (it has some scary implications). :D Jeblad (talk) 14:37, 28 February 2015 (UTC)

Wikidata should be usable regardless of what language you speak. So I am against making something like this an integral part of it. --Lydia Pintscher (WMDE) (talk) 11:19, 1 March 2015 (UTC)
I would support this but I think we should wait till we have a multilingual data type so it is straightforward to add translations for these comments. Either way it is not up to the developers to decide. If you want this then make a property proposal for the users to consider. Filceolaire (talk) 15:54, 2 March 2015 (UTC)
Sure it can always be a property. That's why I said I don't want it to be an integral part of the software as was suggested. I still think it'd not be good to do it with a property but that's up to the editors to decide. --Lydia Pintscher (WMDE) (talk) 16:00, 2 March 2015 (UTC)

New language request[edit]

According to this blog post all languages are admissible for use on Wikidata if it has an ISO 639-3 code.
I would like to request the Talossan language, the ISO 639-3 code of Talossan is tzl.
Talossan is a left-to-right constructed language using the Latin script, the name of the language is "Talossan" in both English and Talossan.
Robin0van0der0vliet (talk) (contributions) 23:03, 1 March 2015 (UTC)

Hey :) Please get the ok for this from the language committee. Then we can add it. --Lydia Pintscher (WMDE) (talk) 07:52, 2 March 2015 (UTC)
Where should I get this approval? I couldn't find a suitable place to request this. This doesn't look like the right place according to this other request. (See PiRSquared17 second message.)
And why does it need additional approval? Didn't they approve every language which has an ISO 639-3 code in that blog post?
Robin0van0der0vliet (talk) (contributions) 19:59, 2 March 2015 (UTC)
For all I know this is the right place. GerardM is the guy to talk to :) It needs approval again because what was approved was that in principal any of these languages can be added but each of them needs an ok again. --Lydia Pintscher (WMDE) (talk) 20:02, 2 March 2015 (UTC)
I just requested it here. Robin0van0der0vliet (talk) (contributions) 20:33, 2 March 2015 (UTC)

mixed data type[edit]

It is possible to have mixed data type string-items?, for example [3] his sons or parents are not notable is only an addictional information, why we are forced to create items for each of them --Rippitippi (talk) 18:35, 2 March 2015 (UTC)

Yes, this would be very useful. But apparently it is not likely to become possible. - Brya (talk) 18:41, 2 March 2015 (UTC)
But is a very simple task if the item exist take the item id otherwise the string --Rippitippi (talk) 18:47, 2 March 2015 (UTC)
Based on how the code in the items look like, I think it's possible to create a flexible datatype, but it has been denied here before. In (65407) 2002 RP120, at the bottom of the page, you see the navigation-template. No Wiki-project has any article about asteroid "(65406) 2002 RS112" or "(65408) 2002 RM136". I think they would have been regarded as non-notable on enwp, but I am not sure in other projects. I have here at WD created items for these asteroids, without any article linked to them. The Swedish labels in these items are used in the page at svwp. If you delete these items, the template on svwp will change. The alternative would be to make the WP-templates flexible, that they allow both manual edits locally on WP or based on properties here at WD. The navigation-template in this page is actually flexible in that manner. I can override P155 and P156 here in WD by adding the parameters "förra" and "nästa" in the template on svwp. -- Innocent bystander (talk) 19:42, 2 March 2015 (UTC)
This would be as (mis)using a word processor (Q54277) as a database (Q8513). --Succu (talk) 20:12, 2 March 2015 (UTC)
I am against this because identifying concepts correctly is at the very core of Wikidata. Say we allow people to add strings instead of links to items when referring to a person. How are we supposed to find out when this person actually does get an item? Or how are we going to sort out if this John Smith is the same as this other John Smith? Having clearly identifyable items for this is extremely important. What we can do is make it easier to create new items for things that do not exist yet. We don't have that yet for two reasons: It being too easy to create duplicates because of missing labels (should be solvable with more work on language fallbacks) and not enough dev time. --Lydia Pintscher (WMDE) (talk) 19:48, 2 March 2015 (UTC)
Your objection is not valid because even now is too easy to create duplicates because of missing labels when the items dont have a wikipedia link and for example Carlo Verdi is notable only because Giuseppe Verdi (Q7317) father --Rippitippi (talk) 20:12, 2 March 2015 (UTC)
I am not saying it is not easy now. But it'd be even easier if we made it very easy to create new items right in place at the moment. Once we have put more work into language fallbacks that should be fine. --Lydia Pintscher (WMDE) (talk) 20:16, 2 March 2015 (UTC)
Lydia if I create 10 items with Carlo Verdi the fallback is useless. If you have mixed data type the only problem is you do not have the items connected, but now you have many junk items and duplicates--Rippitippi (talk) 20:30, 2 March 2015 (UTC)
Fallback language does not solve very much, I'm afraid. I remember a discussion on svwiki about a 1912 olympic champion. Not very much was known about him, but suddenly somebody made a very deep search and discovered that he had a second career as a diplomat 30 years later. Both the olympic and the diplomat had articles, but they did not have the same name. The articles were later merged, not because of metadata or fallback language, but because the articles about early olympics was proposed to be deleted since we did not know their full names, place and time of birth and death. -- Innocent bystander (talk) 08:15, 3 March 2015 (UTC)
You are forced to create items for all of them because, semantic web... I am 100% against a mixed data type for this use case. Also per WD:N the items you would have to create are fine to remain as they fulfil some structural need! ·addshore· talk to me! 22:40, 2 March 2015 (UTC)
Wikidata is flexible, you could also use statements like child (P40): somevalue (qualifier birth name (P1477): the_child's_name or quantity (P1114): how_many_children_they_had). Matěj Suchánek (talk) 18:31, 3 March 2015 (UTC)