Wikidata:Contact the development team/Archive/2015/03

From Wikidata
Jump to navigation Jump to search
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

Inconsistent date formats

  • 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

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)

rdfs:comment

There is a rdfs:comment [1] 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

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.
Robin van der Vliet (talk) (contribs) 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?
Robin van der Vliet (talk) (contribs) 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. Robin van der Vliet (talk) (contribs) 20:33, 2 March 2015 (UTC)

mixed data type

It is possible to have mixed data type string-items?, for example [2] 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)

Data Import

I'm trying to experiment with Wikibase/Wikidata but its difficult to work with an entirely empty WikiData instance, is there an established pipeline to import wikidata database dumps into a new wikidata instance? TechDragon (talk) 11:28, 6 March 2015 (UTC)

We currently don't but we need it for other things as well. We have phabricator:T90148 for it. --Lydia Pintscher (WMDE) (talk) 11:41, 6 March 2015 (UTC)

Q2782419

What is the problem? It is impossible to add anything. Tostarpadius (talk) 23:29, 5 March 2015 (UTC)

I see you were able to edit the item now. I assume this was a caching issue again. We found the reason for it recently and have a patch up. It should be fixed here in the coming weeks. --Lydia Pintscher (WMDE) (talk) 08:29, 6 March 2015 (UTC)
Now there is the same problem with Q637750. Tostarpadius (talk) 22:18, 10 March 2015 (UTC)

Error when adding links from Wikipedia

Hello, a bug which I thought to be solved, has resurfaced. In the past (a year ago or so), I often got an error message when I wanted to add a language interwiki link from Wikipedia and clicked on 'Add links'. The message said something like "You need to be logged in to access the central link repository", even when I was already logged on at both Wikipedia and Wikidata. The strange thing is that I learned to get around the problem by logging off and making the jump from Wikipedia to Wikidata as an anonymous user. It always happened with pages which had no language links yet. I do not know if it mattered if there was already a corresponding Wikidata item (with only 1 sitelink) for those Wikipedia pages.

Because I did not encounter the error message for a while, I thought the problem had been solved, but last month, a colleague mentioned the same error. In this case, there was already an item. Bever (talk) 18:09, 9 March 2015 (UTC)

Thanks. I'll look into it. --Lydia Pintscher (WMDE) (talk) 11:49, 10 March 2015 (UTC)

qualificator with a long name

Hello! When i using a property with a long name as qualificator, it overlaps with next one. E.g. switch into Russian and look at the qualificators for "издание или перевод" (P747) in Q19190739. The name "файл с отсканированными данными" (P996) overlaps with next "предыдущее по порядку" (P155). If a qualificator have enough values, then it displays fine (three values of P996 in Q19595481). -- Sergey kudryavtsev (talk) 10:02, 16 March 2015 (UTC)

PS: I use Chome v. 41.0.2272.89. -- Sergey kudryavtsev (talk) 10:05, 16 March 2015 (UTC)

Hey :) This will be fixed with the current work we are doing on redesigning the statement section. Thanks for the report! --Lydia Pintscher (WMDE) (talk) 10:08, 16 March 2015 (UTC)

Aliases

If you enter aliases they appear with an underline. The underline disappears when you save. I can not see the usefulness of the underlines.--Giftzwerg 88 (talk) 15:53, 17 March 2015 (UTC)

Existing aliases don't have them, I think it is to disambiguate them. Sjoerd de Bruin (talk) 16:26, 17 March 2015 (UTC)
This will be different in the new header that is coming next week. The alias section will need some more work though over the next weeks. I'll take your feedback into account. --Lydia Pintscher (WMDE) (talk) 10:26, 18 March 2015 (UTC)

Failed link in Q2397212

In record Q2397212 the IMDb link does not work. It is using the identifier "ev0000709/2001", that should create a link http://www.imdb.com/event/ev0000709/2001 . At the moment however it is pointing to http://www.imdb.com/find?q=ev0000709/2001&s=nm -- Suas Ghlanadh (talk) 13:09, 18 March 2015 (UTC)

This is nothing developers could do something with. The problem is, you are misusing the property. See its talk page for correct use. Matěj Suchánek (talk) 14:10, 18 March 2015 (UTC)

Suggest list bug

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. 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 "http://books.google.com/books?id=BGwHAAAAQAAJ&pg=PA61".
  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:

  • Seite(n) = 62
  • Digitalisat = Neue Gedichte (Heine) 062.gif
  • URL = http://books.google.com/books?id=BGwHAAAAQAAJ&pg=PA62
  • 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

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)

Why are the triangles vanished

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. P1130 (P1130)
  10. P1131 (P1131)
  11. father (P22)
  12. mother (P25)
  13. spouse (P26)
  14. unmarried partner (P451)
  15. child (P40)
  16. P7 (P7)
  17. P9 (P9)
  18. P43 (P43)
  19. P44 (P44)
  20. relative (P1038)
  21. godparent (P1290)
  22. date of birth (P569)
  23. date of baptism (P1636)
  24. date of death (P570)
  25. place of birth (P19)
  26. residence (P551)
  27. work location (P937)
  28. place of death (P20)
  29. place of burial (P119)
  30. image of grave (P1442)
  31. cause of death (P509)
  32. manner of death (P1196)
  33. killed by (P157)
  34. family name (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 / speciality (P413)
  42. shooting handedness (P423)
  43. languages spoken, written or signed (P1412)
  44. convicted of (P1399)
  45. canonization status (P411)
  46. religion or worldview (P140)
  47. sexual orientation (P91)
  48. ethnic group (P172)
  49. affiliation (P1416)
  50. member of (P463)
  51. participant in (P1344)
  52. member of sports team (P54)
  53. country for sport (P1532)
  54. member of political party (P102)
  55. family (P53)
  56. noble title (P97)
  57. honorific prefix (P511)
  58. military branch (P241)
  59. commander of (DEPRECATED) (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 work (P800)
  73. filmography (P1283)
  74. has pet (P1429)
  75. signature (P109)
  76. audio 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 ID (P865) (alpabetical)
  83. GND ID (P227)
  84. VIAF ID (P214)
  85. Library of Congress authority ID (P244)
  86. Nationale Thesaurus voor Auteursnamen ID (P1006)
  87. VIAF ID (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)

Property-valued property

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) Wikidata property (P1687) place 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)

Cannot add a label

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

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 View with SQID. (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)

Male not seen

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)
I've been thinking about this more and discussed it. The outcome is phabricator:T94404. --Lydia Pintscher (WMDE) (talk) 13:26, 30 March 2015 (UTC)

Hem...

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)
I understand yeah. But I don't think we can release a new data type on Wikidata without allowing to edit it through the UI :/ --Lydia Pintscher (WMDE) (talk) 13:28, 30 March 2015 (UTC)

cache-problem when adding label?

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)

Which label did you try to change initially to what? Do you remember which item was in conflict? --Lydia Pintscher (WMDE) (talk) 13:29, 30 March 2015 (UTC)

Date input bug

I tried to add a date qualifier here. I type "1905", I saved, it showed "1905". But actually it saved "19" and that only showed after I reloaded the item. It does not happen all the time, but it is not the first time I have exeperienced this. --Zolo (talk) 11:18, 30 March 2015 (UTC)

A fix is being worked on in phabricator:T92831. --Lydia Pintscher (WMDE) (talk) 13:31, 30 March 2015 (UTC)
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Contact_the_development_team/Archive/2015/03&oldid=209727846"