Wikidata:Report a technical problem: Difference between revisions

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 2024/09.

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day.

Use this page to report a technical problem! If the problem you encounter is about the Wikidata Query Service or Search, please report it at WDQS and Search.

Start a new discussion

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

@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)[reply]

@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)[reply]

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

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)[reply]

@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)[reply]

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)[reply]

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

1. 2019-10-15 Property talk:P1461#Change datatype to external-id
2. 2022-09-07 Property talk:P1815#Change datatype to external-id
3. 2022-09-07 Property talk:P2410#Change datatype to external-id

GeoGQL (talk) 11:58, 2 April 2023 (UTC)[reply]

@GeoGQL Thank you for your message. We do not see any blockers to changing P1461 and P1815 to external-id. As for P2410, I'd like to hear from Andra or Egon before moving forward with a ticket. - Mohammed Sadat (WMDE) (talk) 13:12, 4 April 2023 (UTC)[reply]

Regarding the last sentence: Why? GeoGQL (talk) 15:45, 4 April 2023 (UTC)[reply]

@LennardHofmann: since you were involved in the first and proposed the two from 2022-09-07 you might be interested. GeoGQL (talk) 15:50, 4 April 2023 (UTC)[reply]

I replied about WikiPathways ID (P2410): yes, external-id but keeping it as P2410 seems a good way forward. About asking me (that last sentence), generally, asking people involved in the original proposal and/or external database is always a good way to do. That last sentence did not give me a decision right, but just asked for my contribution. --Egon Willighagen (talk) 07:30, 6 April 2023 (UTC)[reply]

"asking people involved in the original proposal and/or external database is always a good way to do" - User:Mohammed Sadat (WMDE) didn't yet specify a reason and he didn't do what you desribe for the other two in the above list of three. But thanks, now his "blocker" for not fulfilling the request ("I'd like to hear from Andra or Egon before moving forward with a ticket.") is on the way to be removed. As he wrote "I'd like to hear ..." can you post directly on his user talk page, to ensure he did "hear" you? He didn't reply to my question from 2023-04-04 15:45 despite editing in Wikidata, even on this page, 2023-04-06 10:52 [1]. GeoGQL (talk) 21:49, 7 April 2023 (UTC)[reply]

Thanks Egon.

@GeoGQL: Sometimes, it may take a little time to respond to messages due to capacity. I did see Egon's update (and their response was what I had in mind) but I couldn't get to it before the holidays. I've created a ticket to move forward with changing the datatype. -Mohammed Sadat (WMDE) (talk) 08:37, 11 April 2023 (UTC)[reply]

Thank you. GeoGQL (talk) 22:31, 12 April 2023 (UTC)[reply]

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 ( [2] ) 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)[reply]

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)[reply]

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)[reply]

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)[reply]

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)[reply]

"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)[reply]

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)[reply]

"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)[reply]

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)[reply]

@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)[reply]