Wikidata:Report a technical problem/Archive/2023/04

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

Improvement in merge gadget to avoid data duplication

Tracked in Phabricator
Task T334197

See request. Thanks, --Epìdosis 21:13, 21 March 2023 (UTC)

@Epìdosis: Thanks for your message. MediaWiki:Gadget-Merge.js is a community maintained tool. Have you tried using Special:Merge? -Mohammed Sadat (WMDE) (talk) 13:57, 4 April 2023 (UTC)

@Mohammed Sadat (WMDE): thanks for the suggestion. I tried now Special:MergeItems and, as you can see from this merge, it has exactly the same problem of the merge gadget. It would be good solving it in both systems, the gadget and the special page. Thanks, --Epìdosis 18:04, 4 April 2023 (UTC)

I created a ticket so we can look into this. -Mohammed Sadat (WMDE) (talk) 10:52, 6 April 2023 (UTC)

Merger

Hello,

Could the items Q320283 and Q2910609 be merged? They are a duplicate; the second is simply a version linked to the related article on Dutch Wikipedia.

Thank you. 2A01:CB04:121:F200:4D27:CC4E:4528:6F9C 00:34, 2 April 2023 (UTC)

 Merged --Matěj Suchánek (talk) 13:54, 2 April 2023 (UTC)

New federated query service

I want to know about the procedure for registering a new sparql enpoint service (external source).

According to this page there is a list of federated endpoints from mediawiki, and it includes the one I need (https://opendata.aragon.es/sparql) but it I think it doesn't work from wikidata endpoint

e.g. query

Response is:

Service URI https://opendata.aragon.es/sparql is not allowed Dportolesr (talk) 15:35, 24 March 2023 (UTC)

@Dportolesr: Please watch out for an update about this issue on Wikidata:Report a technical problem/WDQS and Search#New federated query service. -Mohammed Sadat (WMDE) (talk) 11:20, 13 April 2023 (UTC)

Fallback language of European languages

Wikidata has multiple English variants, where "English" is US-English (since the only language options are "English", "British English" and "Canadian English"). This means that for European languages that fall back to English (even if it isn't the first step) should rather fall back to British English first. British English is used for, for example, European titles of media that differs from US-titles of media (if UK also used the same title). But since European languages don't fall back to British English, when an entry for such language is missing, it will display the US-title instead of the expected European title. Some examples of objects with different US and European titles: Q10676, Q2713289, Q7712517. For example, using Hungarian for the second object will display the US-title instead of the European title. Pon Pon the bon bon (talk) 18:24, 7 April 2023 (UTC)

"This means that for European languages that fall back to English (even if it isn't the first step) should rather fall back to British English first." - Why that? GeoGQL (talk) 21:51, 7 April 2023 (UTC)

Just to clarify, it should fall back to British English right before English, if there's other steps before English, those should still appear before British English and English as usual.

The reason why it should be British English before English for European languages, is because the British English title is more likely the more correct title for an object than the English (US) title. Using Q2713289 as the example, the original title is "Scream Team", but in Europe it is "Scare Island", therefore British English is using the European title. The Danish title is missing, so it falls back to English, and not British English, and is therefore showing the US-title rather than the European title. I found a Danish copy, so the Danish title can be entered as "Monsters Inc.: Skræmmeøen", which is translated from the European title, and it's using the European cover-style. Having Danish fall back to British English before English would make sense here.

There are other examples as well, such as Q828224 kilometre, which is using the description "unit of length equal to 1,000 meters". So since, for example, Welsh is missing a description, it falls back to using English and not British English, using the spelling "meters" instead of "metres". The British English spelling is usually the official spelling for European countries. For example, the Swedish Transport Administration is using British English "metre" in their documents as can be seen here. 26 usages of "metre", although one usage of "meter", likely a typo. Pon Pon the bon bon (talk) 13:23, 8 April 2023 (UTC)

"en" is the code for English in general, not for US-English - it shouldn't be assumed that it is always the American English specific label or that American names get priority.

There is an option to add en-US labels, as this has been a supported language variant since 2021 (phab:T154589) - see eg this edit. Because it was a late addition, it's hardly used at all (see User:Mr. Ibrahem/Language statistics for items) Andrew Gray (talk) 13:56, 8 April 2023 (UTC)

Regex problem for Freebase-identificationcode?

The item Olga Tuktareva (Q117037607) has the value /m/011bzyd7 for Google Knowledge Graph-identificationcode. Because the first letter is not a 'g' but a 'm' that is not the Google Knowledge Graph-identificationcode but the Freebase-identificationcode. I tried to change that but for some reason when I start adding a Freebase-identificationcode and I enter /m/011bzyd7 in the input box the last character (the '7') is automatically removed before I can click on the publish link. First I thought it has to do with the regex rules for Freebase-identificationcode but changing the regex ( [1] ) didn't help. Then my hope was that it could be some caching issue so the problem might be over after waiting a few days. Unfortunately the problem is still there. Does anybody understand what is going wrong here? - Robotje (talk) 14:08, 2 April 2023 (UTC)

There is a redundancy with Property:P646#P646$6674B7F2-4C15-42F6-9EF3-3C1BE3B84E6C that probably needs to be updated as well. --Matěj Suchánek (talk) 20:10, 2 April 2023 (UTC)

@Robotje: When we tested it in the sandbox, it worked as expected, so there might be another factor at play that is interfering with the input box and causing the issue. Have you tried disabling any gadgets or userscripts to see if that resolves the issue? -Mohammed Sadat (WMDE) (talk) 16:37, 13 April 2023 (UTC)

Just like Matěj Suchánek mentioned in the edit above on 2 April, after this change I still had to do this edit. Once that was done, the problem was over. Thanks for the good advice. - Robotje (talk) 17:45, 13 April 2023 (UTC)

Feature request: geopandas on PAWS

Since there are a lot of geographical data in the wikisphere/wikitubes it would make a lot of sense to make available on PAWS the geopandas library with dependencies. Infrastruktur (talk) 20:38, 2 April 2023 (UTC)

As long as this is not available by default, you can temporarily install missing libraries: run %pip install geopandas in a cell at the beginning of your script; dependencies will also be temporarily installed. Be aware that the library will disappear when you end your PAWS session (probably logout/session lost). —MisterSynergy (talk) 20:48, 2 April 2023 (UTC)

@Infrastruktur: Thank you for the suggestion. Unfortunately, we don't have control over PAWS as it is managed by a separate team at the WMF. You may want to try contacting the Wikimedia Cloud Services team for more information. -Mohammed Sadat (WMDE) (talk) 16:46, 13 April 2023

Thanks to MrSynergy's reply I think I'm covered since I rarely operate on geospatial data. I am however a significant user of regular pandas, which so happened to have a major release in March this year. In the case some infrastructure peeps happens to frequent this forum I would rather ask for an upgrade to pandas version 2.0 than anything else. Infrastruktur (talk) 18:55, 14 April 2023 (UTC)

Well, %pip install pandas==2.0.0 should have you covered (maybe you need to restart the kernel once). As much as I am aware, pandas 2 is not yet offered as an update for existing installations since it is still very experimental. —MisterSynergy (talk) 19:02, 14 April 2023 (UTC)

Depicts on Commons versus What_links_here at Wikidata

Tracked in Phabricator
Task T334352

When I look at "Items portrayed in this file" at Commons I can see Wikidata entries. I can't see the reverse from Wikidata, this is a flaw. We should, when we click What_links_here, be able to see those same "Items portrayed in this file" at Commons from Wikidata. That would let me know that a person is mentioned in Commons when I am in Wikidata, if there is no category for the item. RAN (talk) 22:59, 9 April 2023 (UTC)

@Richard Arthur Norton (1958- ): Thanks for bringing this up. We are aware of the issue and we have a ticket for it already. It's on our radar. - Mohammed Sadat (WMDE) (talk) 16:20, 13 April 2023 (UTC)

Javascript, jshint and eshint

I used to add /*eshint esversion: 8 */ in js to be able to use more modern features of javascript like async/await, alas there is now an error message "incompatible values for the 'esversion' and 'esnext' linting options (0% scanned)" which is a bummer and entails errors in script that used to not be there and make saving difficult … Is this Wikidata specific or should I report this elsewhere ? author  TomT0m / talk page 19:50, 25 April 2023 (UTC)

Nevermind, it seems that adding a ",esnext:false" option does the trick and removes all warnings. author  TomT0m / talk page 20:16, 25 April 2023 (UTC)