Wikidata:Report a technical problem/Archive/2022/04
|
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion. |
"Random Lexeme"
Can we change this link to "Random lexeme" to comply with the site style? All the best: Rich Farmbrough, 11:37, 18 March 2022 (UTC).
- Hi Richard, just to be clear, are you referring to changing the capitalized L to lowercase l ? -Mohammed Sadat (WMDE) (talk) 10:36, 23 March 2022 (UTC)
- Exactly so. All the best: Rich Farmbrough, 08:52, 30 March 2022 (UTC).
- Actually we're trying to harmonize the spelling of the words Items & Lexemes so they are spelled with first letter capitalized. Do you have a different capitalization style format you think we should follow? -Mohammed Sadat (WMDE) (talk) 09:31, 4 April 2022 (UTC)
- @Mohammed Sadat (WMDE): I don’t see any reason to capitalize these words. They are just regular common nouns, aren’t they? Common nouns are capitalized only in German, not in English. We also write Wikipedia articles (and not Wikipedia Articles), create Commons categories (and not Commons Categories), similarly we should have Wikidata items and lexemes, not Wikidata Items and Lexemes. —Tacsipacsi (talk) 23:50, 5 April 2022 (UTC)
- Wikidata is known for its insistence on lower case - cf. Help:Label#Capitalization, Help:Description#Capitalization - and its documentation has long eschewed the idea that 'item' should be capitalised - see the text of Help:Items. And the house style for EN wikipedia, at least, is sentence-case rather than title-case. Ideally WMDE would know this and not try to go in a diametrically opposed direction, as if completely unfamiliar with the tenets of its own product & WMF platforms more generally. --Tagishsimon (talk) 00:04, 6 April 2022 (UTC)
- I don't think this snark is warranted or ok. Please don't do that. Lydia Pintscher (WMDE) (talk) 07:37, 6 April 2022 (UTC)
- @Lydia Pintscher (WMDE): WD & more generally wikimedia does not do capitalisation of the sort you are proposing. WDME is going in a diametrically opposed direction by treating things that are not proper nouns as proper nouns. WMDE should not, ideally, go in a different direction from its community. Dismissing pushback - I'm the third voice here against the idea - as snark is fallacious. You need to face up to the indications that the community does not like the idea. --Tagishsimon (talk) 07:48, 6 April 2022 (UTC)
- I don't think this snark is warranted or ok. Please don't do that. Lydia Pintscher (WMDE) (talk) 07:37, 6 April 2022 (UTC)
- We are treating them as proper nouns to distinguish the concept of a general item (e.g. "item in a list") from the concept of an Item on Wikidata (e.g. "the Item Q42"). Same for Property and Lexeme, which have more common noun counterparts. Lydia Pintscher (WMDE) (talk) 07:35, 6 April 2022 (UTC)
- I also ask that you instead listen to the community. I see nowhere the community writes Item, Lexeme or Property, and it isn't as far as know customary in English to treat specialized meanings of nouns as proper nouns. --Dipsacus fullonum (talk) 09:50, 6 April 2022 (UTC)
- Wikidata is known for its insistence on lower case - cf. Help:Label#Capitalization, Help:Description#Capitalization - and its documentation has long eschewed the idea that 'item' should be capitalised - see the text of Help:Items. And the house style for EN wikipedia, at least, is sentence-case rather than title-case. Ideally WMDE would know this and not try to go in a diametrically opposed direction, as if completely unfamiliar with the tenets of its own product & WMF platforms more generally. --Tagishsimon (talk) 00:04, 6 April 2022 (UTC)
- @Mohammed Sadat (WMDE): I don’t see any reason to capitalize these words. They are just regular common nouns, aren’t they? Common nouns are capitalized only in German, not in English. We also write Wikipedia articles (and not Wikipedia Articles), create Commons categories (and not Commons Categories), similarly we should have Wikidata items and lexemes, not Wikidata Items and Lexemes. —Tacsipacsi (talk) 23:50, 5 April 2022 (UTC)
- Actually we're trying to harmonize the spelling of the words Items & Lexemes so they are spelled with first letter capitalized. Do you have a different capitalization style format you think we should follow? -Mohammed Sadat (WMDE) (talk) 09:31, 4 April 2022 (UTC)
- Exactly so. All the best: Rich Farmbrough, 08:52, 30 March 2022 (UTC).
Add a lua function "getBadges"
We have a usecase on frwiki that apparently add a category depending on a bagde on Wikidata.
Problem, getting the bagde currently seem to require to load the whole entity which in some items requires a lot of memory. This can cause lua error.
Should we add a ticket to get a lua function "getBadges" that get a badge, similar to "getSitelinks" (that does return a sitelink, but no badge) author TomT0m / talk page 18:30, 3 April 2022 (UTC)
- Thanks for bringing this here @TomT0m. We created a ticket, if it doesn't describe the problem you reported well feel free to edit it. -Mohammed Sadat (WMDE) (talk) 17:25, 4 April 2022 (UTC)
The property discussion home page no longer displays the number of currently discussed proposals other than those that are ready to be created. In addition, since February, the bot has stopped automatic archiving of properties. Could you correct the mistakes? MasterRus21thCentury (talk) 08:10, 7 April 2022 (UTC)
- Unfortunately the bot owner, User:Pasleim, hasn’t edited since January, so the chances for getting the bot fixed quickly are low. I think the bot was broken by Wikidata:Property proposal/Commons being turned into a redirect (the timing seems to confirm this: the turning into a redirect happened on 13 February, and the last successful update to Wikidata:Property proposal/count was on 12 February). So the hotfix may be to change the hard redirect to a soft redirect (
{{Soft redirect}}) until the bot is fixed. —Tacsipacsi (talk) 14:47, 8 April 2022 (UTC)- Do other Wikidata administrators have the same bots that would replace DeltaBot? MasterRus21thCentury (talk) 06:44, 9 April 2022 (UTC)
- First, bots are not necessarily run by adminstrators, the bot ownership is independent from the admin right, so anyone who has the necessary technical knowledge can operate bots (if the community supports them). Second, all scripts are listed don User:DeltaBot, so theoretically any other bot owner can take it over. However, it could lead to issues if DeltaBot gets fixed and both bots operate at the same time. Since DeltaBot seems to run on Wikimedia Toolforge, the abandoned tool policy can be used to take it over, provided that Pasleim doesn’t respond in reasonable time and someone else volunteers to adopt the bot. —Tacsipacsi (talk) 18:18, 9 April 2022 (UTC)
- Do other Wikidata administrators have the same bots that would replace DeltaBot? MasterRus21thCentury (talk) 06:44, 9 April 2022 (UTC)
Wikidata Query Builder fails to produce results
I tried producing data of human who are alive but somehow it always produces an error. But if I remove (date of death or place of death) then the query is able to produce results. Here is the URL to reproduce - https://w.wiki/563X - DownTownRich (talk) 21:12, 23 April 2022 (UTC)
- @DownTownRich: Have you tried the
Show IDs instead of labels (may prevent timeout)
option? That seems to work for me. Lucas Werkmeister (WMDE) (talk) 08:35, 25 April 2022 (UTC)- I tried it out also, still getting a timeout error and the I was trying to utilize the labels from the results. DownTownRich (talk) 10:39, 25 April 2022 (UTC)
- I saw it quickly without labels. This could be an issue in `SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE]". }`. BTW, there is no development activity in Wikidata Query Builder. YFdyh000 (talk) 00:21, 27 April 2022 (UTC)
- The linked query above has marked the field "Include related values in the search (recommended)". That is unnecessary for humans (Q5), and will only make the query slower with no gain. The help text could be better for that field as it doesn't mention subclasses at all, or that for certain values of instances (P31) like humans, subclasses are not used. --Dipsacus fullonum (talk) 12:14, 27 April 2022 (UTC)
- I saw it quickly without labels. This could be an issue in `SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE]". }`. BTW, there is no development activity in Wikidata Query Builder. YFdyh000 (talk) 00:21, 27 April 2022 (UTC)
- I tried it out also, still getting a timeout error and the I was trying to utilize the labels from the results. DownTownRich (talk) 10:39, 25 April 2022 (UTC)