Wikidata:Contact the development team/Archive/2016/11

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.

IMSLP ID string not showing

Tracked in Phabricator
Task T150403

In items like Waltzes, Op. 64 (Q16742080), or Bourrée No. 1 (Q16765125) the string for ISMLP ID appears as empty. However the link works, and when clicking edit, it shows. Is it a bug? --Micru (talk) 12:44, 5 November 2016 (UTC)

Thanks for your report, I can reproduce the bug. We will check it soon. Lea Lacroix (WMDE) (talk) 09:05, 10 November 2016 (UTC)

Can't reject proposed claim, Firefox & Edge

Tracked in Phabricator
Task T150520

When Universe (Q1) is viewed in Firefox, there are properties, point in time (P585), having the values 1807 and 1847, with a medium blue background and options to "approve claim", "reject claim", "approve reference", and "reject reference". When one of the rejects are clicked, some little grey and black boxes flash next to where one clicked, and just keep going for a while, and then "Set statement to wrong failed" appears in a pink box. Firefox is v. 49.0.2 and is installed in Windows 10.

When Edge is used to view Universe (Q1) the above-mentioned behavior is the same (also Windows 10). Jc3s5h (talk) 13:02, 10 November 2016 (UTC)

Hello,
Thanks for the report. I can't reproduce the bug on my own Firefox. Can you make a screenshot, maybe check the gadgets you enabled to see if one of them could disfunction? Lea Lacroix (WMDE) (talk) 13:53, 10 November 2016 (UTC)
I can reproduce it. It's about proposed statements by the primary source gadget which can't be rejected. --Pasleim (talk) 14:50, 10 November 2016 (UTC)

Parser function: #statement

Maybe it was suggested somewhere, but I cannot find it. I have an idea to expand the new proposed parser function with two extra parameters: {{#statement:...|novalue=...|somevalue=...}}. Their names explain their purpose. They allow to replaces two special values in the statement with given wikitext. I think it might be very useful in infoboxes in some circumstances, when specific description would be required instead of empty text. Paweł Ziemian (talk) 20:14, 31 October 2016 (UTC)

Do you have a concrete case where you would use this? --Lydia Pintscher (WMDE) (talk) 10:55, 15 November 2016 (UTC)
There were some experiments to provide infobox for languages in plwiki with access to Wikidata and there is used writing system (P282), which sometimes consists of claims with "novalue". To show demo just use {{Język infobox/temp|Q=Q56636}} in any sandbox in plwiki. The infobox is already Lua based ({{#invoke:Infobox|Wiersz|...}}), but #statement might be much easier to use in most cases. There is more people that can write standard templates (and infoboxes) than those who knows how to write modules in Lua. Paweł Ziemian (talk) 16:40, 15 November 2016 (UTC)

Partial JSON dumps

The actual JSON dump compressed is more than 6 Gigabyte so, it's possible to create json dumps with only item changed from the previous week/dump? This allows for smaller files, and then you need less time to download and decompression. Useful for those who have slow connections. --ValterVB (talk) 18:51, 4 November 2016 (UTC)

Some opinion? --ValterVB (talk) 07:08, 11 November 2016 (UTC)
Please see phabricator:T72246. --Lydia Pintscher (WMDE) (talk) 10:56, 15 November 2016 (UTC)

Unable to edit items on Firefox

Tracked in Phabricator
Task T150401

Whenever I load an item on Firefox 49.0.2 there are no edit links on the item, yesterday it was working fine. Reloading doesn't help. It works on Chrome though.--Micru (talk) 07:25, 10 November 2016 (UTC)

Hello,
Thanks for your report, this is embarrassing. Apparently it's related to the gadget PopupsFix (phab:T150401) For now you can desactivate the gadget to have the links back. We'll find a better solution soon. Lea Lacroix (WMDE) (talk) 08:57, 10 November 2016 (UTC)
The gadget has been disabled for all users for now. Sjoerd de Bruin (talk) 10:58, 10 November 2016 (UTC)

This is fixed now! Lea Lacroix (WMDE) (talk) 11:21, 11 November 2016 (UTC)

Development feedback re climate data

@Lea Lacroix (WMDE): would you arrange to provide the community with project development feedback on the problem outlined at https://phabricator.wikimedia.org/T147049 ?
--- Jura 14:18, 22 October 2016 (UTC)

The best is to work on a solution for high density data: for data with a mxn format where m is the number of lines and n the number of columns and n>2, we need a new data type. Snipre (talk) 19:36, 23 October 2016 (UTC)
Hello,
Here's a quick feedback from my colleagues.
Time series data type is not desirable. This is out of the scope of both the Wikibase software and the Wikidata project. Continuous time series could for example be stored in a dedicated database outside of Wikidata and linked to.
Derived numbers like monthly averages are OK (similar to population, also a number that typically changes once per year).
One question remains: Multiple property for min/max/average, or one property (and then specify with qualifiers)? This is not a question we (the devs) can answer. This is a community decision. From our point of view both are fine.
Hope this answers our question. Lea Lacroix (WMDE) (talk) 11:06, 28 October 2016 (UTC)
  • Not really, I'm not quite sure if this was clear: To be meaningful, the numbers should be on a monthly basis. An entire set of 12 would generally make up a meaningful unit (with references/rank etc). To generate diagrams at Wikipedia, one would need to store the data somewhere at WMF (at Commons or Wikidata).
    Population numbers are only partially comparable, as there is generally only one value that needs to be retrieved at once. However, already there it's starts getting difficult when multiple values based on different methodologies need to be handled.
    I would expect Wikidata development to formulate a recommendation (use existing functionality) or plan development for this type of series (even if it's in 2020).
    --- Jura 11:21, 28 October 2016 (UTC)

I think we need to talk about this more. Léa: Let's discuss how to move forward when I am back in the office. --Lydia Pintscher (WMDE) (talk) 14:30, 28 October 2016 (UTC)

@Jura1: A possible option could be to store the temperatures as tabular data in Commons (see T148745) and then link it from Wikidata with a dedicated property. Tabular data example --Micru (talk) 15:33, 5 November 2016 (UTC)

Language support

Wikidata has English (en), "British English" (en-gb; superfluous, same as en), and Canadian English (en-ca). But it does not support other variants of English, notably American (en-us), but also Australian (en-au), Indian (en-in), New Zealand (en-nz), South African (en-za) and perhaps others. Many plants and animals have different names in one or more of these languages, but until they are enabled, it is not possible to indicate usage. Could these be added, please? Thanks! - MPF (talk) 18:20, 9 November 2016 (UTC)

Hello, here's the process to add new language codes :) If you encounter any problem, please ask some help. Lea Lacroix (WMDE) (talk) 10:55, 10 November 2016 (UTC)
Thanks! From there, "If you don't want to or can't use Phabricator, add your request to Wikidata:Contact the development team" - well, I fear I don't know how to use 'Phabricator' (I don't even know what it is!) - so I hereby add my request here, for American (en-us), Australian English (en-au), Indian English (en-in), New Zealand English (en-nz), and South African English (en-za) to be added, please. Thanks! - MPF (talk) 23:55, 10 November 2016 (UTC)
Was there somewhere consensus reached to claim en=en-gb? My current understanding is that "en" can be used for all language variants and is not restricted to en-gb. --Pasleim (talk) 09:42, 11 November 2016 (UTC)
My understanding (although I can't say why) is that en=en-us. Thryduulf (talk) 16:20, 12 November 2016 (UTC)
@Pasleim: not sure any consensus is necessary? English is the language of English people, the people found in England. @Thryduulf: absolutely not. - MPF (talk) 23:47, 12 November 2016 (UTC)
Consensus is necessary because it is a controversial change. Many user will not agree when you say en=en-gb. Please get wider community input by starting a discussion on WD:PC or WD:RFC. --Pasleim (talk) 09:32, 14 November 2016 (UTC)
I'd agree this is indeed controversial :-). It's also worth noting that going down the en-XX route at all rather than just a single "en" code (as on Wikipedia) may be more trouble than it's worth. I agree there are some circumstances where it is useful to distinguish UK/US names for a thing, but relatively few - and enabling many different English variants just allows for massive fragmentation and inconsistency in all the *other* labels, potentially a huge maintenance burden in order that we can get "colour" right on a few items. We had an inconclusive RFC discussion on this years ago but perhaps it's time to look at it again. Andrew Gray (talk) 12:59, 16 November 2016 (UTC)
It's only a maintenance burden because the interface isn't yet good enough. If we had something where we could edit all varieties of English, German, etc simultaneously for the many cases where they're the same while still being able to modify them individually when they differ, it would be a vast improvement. - Nikki (talk) 20:37, 17 November 2016 (UTC)
This seems to be yet another version of the macro languages, but this time with an area tag. [1] I believe e need a better solution, perhaps with macro languages. Jeblad (talk) 11:06, 16 November 2016 (UTC)

Pinged by rollback

This is not a Wikibase-bug, but rather something else...

This edit pinged me! -- Innocent bystander (talk) 08:02, 19 November 2016 (UTC)

What notification? Reverted, page-linked, mention? Matěj Suchánek (talk) 08:11, 19 November 2016 (UTC)
"mention" -- Innocent bystander (talk) 08:29, 19 November 2016 (UTC)
Same here. author  TomT0m / talk page 09:55, 19 November 2016 (UTC)
Me too: "Mention" --ValterVB (talk) 10:18, 19 November 2016 (UTC)
Seems to be a Echo-bug. Its a bug bug bug… Jeblad (talk) 13:06, 19 November 2016 (UTC)
And now repinged, by the same diff. -- Innocent bystander (talk) 19:04, 19 November 2016 (UTC)
Sorry, see phab:T148949 and phab:T150913. Sjoerd de Bruin (talk) 19:38, 20 November 2016 (UTC)

Language names

There are a number of language names (as displayed for labels and monolingual text) which are not showing an English name, for example here bxr is shown as "буряад" rather than "Buryat".

Who can change those? Should I just make a Phabricator ticket with a list of ones I think should be changed?

- Nikki (talk) 18:08, 19 November 2016 (UTC)

Hello, I encounter the same problem. Feel free to create the ticket, otherwise I can do it :) Lea Lacroix (WMDE) (talk) 09:35, 21 November 2016 (UTC)
I've created phab:T151269. :) - Nikki (talk) 23:39, 21 November 2016 (UTC)

Error in formula displaying

Tracked in Phabricator
Task T150737

See Talk:Q45867. --Infovarius (talk) 08:48, 15 November 2016 (UTC)

Thanks for reporting! Lea Lacroix (WMDE) (talk) 10:11, 15 November 2016 (UTC)
Hello @Infovarius:, this should be fixed now. If you still see the error, please purge the page's cache. Lea Lacroix (WMDE) (talk) 10:56, 23 November 2016 (UTC)

Dump file structure

Hello,

I'm interested in DUMP file structure and mechanism of it creation.

1. does the dump file cover all Wikipedia articles?

2. If the answer to 1 = no how are the articles selected to go in to the dump file?


I'm not a programmer myself so please for a adequate answer.

Many thanks in advance, Bartosz  – The preceding unsigned comment was added by 80.82.28.2 (talk • contribs) at 16:41, 17 November 2016‎ (UTC).

The Wikidata dumps cover all Wikidata items (which should cover almost all Wikipedia articles), the dumps of the individual Wikipedias cover all relevant content of these Wikipedias. Cheers, Hoo man (talk) 11:53, 23 November 2016 (UTC)

instance of human : would be Linked Data Fragments a solution ?

You might get very lucky once if the query is cached or so This is a comment from Magnus about the timeout of queryes of type "instance of human" This made we wonder : could Linked Data Fragment be a solution for this problem ? I see on blazegraph homepage that there is blazegraph-based solutions like https://github.com/laurensdv/BlazegraphBasedTPFServer for LDF. Could our instance of Blazegraph use this as a cache for this query, for example ? With something like locally federated query ... Just an idea. author  TomT0m / talk page 13:51, 23 November 2016 (UTC)

Well, we're actually working on integrating linked data fragments, it's almost ready and will be announced and deployed in the next days :) Lea Lacroix (WMDE) (talk) 13:53, 23 November 2016 (UTC)
Cool :) And that would help with this kind of problem ? author  TomT0m / talk page 20:06, 24 November 2016 (UTC)

Problem getting date properties

Hello! In Basque Wikipedia (eu:wp) when we get a date property (tested date of birth (P569) and date of death (P570)) via Wikidata list template this dates are formatted as YYYY-MM-DD, so we can parse them using {{#time}} magic word. But when we get them using {{#property:P569}} the format is DD month name in basque YYYY, so we can't parse it in any way. How could I solve this problem? -Theklan (talk) 22:40, 26 November 2016 (UTC)

You should use Lua then. And Wikidata list template doesn't have to do anything with {{#property:}}. It could output also as DD.MM.YYYY, if Magnus wanted to :) --Edgars2007 (talk) 15:04, 27 November 2016 (UTC)

Probleme mit Doppelvokalen

Irgendwie klappt bei der Eingabe von zwei Vokalen hintereinander die Selbstergänzung nicht.

Bei Eingabe des Items "Staatangehörigkeit" wird daraus "Ståtangehörigkeit", der Vorname "Michael" wird automatisch zu "Michäl"

Es gibt den Workaround erst falsch weiterzuschreiben und dann einzelne Buchstaben zu ändern, aber das ist natürlich Murks. --Eingangskontrolle (talk) 20:47, 23 November 2016 (UTC)

@Eingangskontrolle: Bei welchem Eingabefeld genau tritt dieses Problem auf? Am Rand von fast allen Eingabefeldern wird dir, wenn du sie auswählt, eine kleine Tastatur angezeigt. Wenn du auf sie klickst, ist dann "Native Tastatur verwenden" ausgewählt? Wenn nicht, dann wähle das mal aus und probiere deine Beispieleingaben nochmals. Grüße, Hoo man (talk) 00:51, 24 November 2016 (UTC)
Ich pflege meine eigene Tastatur zu benutzen, die funktioniert sonst überall. --Eingangskontrolle (talk) 09:19, 24 November 2016 (UTC)
Falls aa zu å und ae zu ä wird, hast du Schwedisch bei den Eingabeeinstellungen ausgewählt, hier findest du welche Ersetzungen dies durchführt. Um das zu deaktivieren, öffne den Universal Language Selector (oben rechts ) und klicke auf Eingabeeinstellungen -> Native Tastatur verwenden -> Einstellungen anwenden. --Pasleim (talk) 09:54, 24 November 2016 (UTC)

ːI only understand fractions of the above, but I think I know which feature you are discussing. Would it be possible to ask for a gadget to deactivate this feature completely. I found it very frustrating, and I fail to remember how to turn it of every time it reoccur. -- Innocent bystander (talk) 08:03, 29 November 2016 (UTC)

Correcting false data

Someone added wrong information to my father's page, Léo Sauvage From the date of his death, which was actually October 30, 1988, to the name of the woman he married (my mother) who was not Barbara Pisar, to the fact that my dad had 3 kids, Pierre born in Le Chambon , and twins (Michel, and myself, Marianne) born in New York. A lot is missing too. My father was a theatre critic too.2607:FB90:2200:787E:78EB:2281:A922:D969 14:37, 27 November 2016 (UTC)

Thanks for reporting these errors. I have done the following:
I have not created items about yourself or your brother Michel since I'm not sure you have the required notability, nor would these items fulfill a structural need (i.e. they would not serve to link together other existing items). Mushroom (talk) 23:41, 27 November 2016 (UTC)
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Contact_the_development_team/Archive/2016/11&oldid=415186279"