Community Wishlist Survey 2023/Wikidata
Prevent data duplication
- Problem: Wikidata allows in various ways to add duplicate data: this makes the maintenance of the items more difficult and uselessly increases the size of Wikidata (which is bad for the SPARQL query service, storage space etc.).The cases I consider are: duplications between labels and aliases in the same language; duplications of date-statements (due to different encode of the same date); duplications of references (two exactly identical references, or the two references identical except for a different retrieval date)
- Proposed solution: make it impossible on server-side to save exactly duplicate data; make it more difficult (e.g. show a message before saving the edit) to add nearly duplicate data (this regards the case of references identical except for a different retrieval date)
- Who would benefit: Wikidata community (the maintenance of items becomes a slightly smaller task); SPARQL query service (the size of the items becomes slightly smaller)
- More comments:
- Phabricator tickets:
- T157774: Make it impossible to set the same content in the same language for label and alias
- T310981: Duplication of dates due to different encode
- T224333: It's possible to save a statement with duplicate references
- T270375: Saving identical references with different retrieval dates should be more difficult
- T44325: Prevent creation of items having the same sitelinks (duplicates)
- Proposer: Epìdosis 09:45, 29 January 2023 (UTC)
Discussion
- There are also duplicated items on Wikidata that cannot be merged. https://www.wikidata.org/wiki/Property:P2959 C933103 (talk) 05:44, 7 February 2023 (UTC)
- Also see https://phabricator.wikimedia.org/T44325 M2k~dewiki (talk) 08:54, 7 February 2023 (UTC)
- Permanent duplicates are a slightly different problem, caused by the fact that an item cannot have two sitelinks for the same Wikimedia project; truly unpleasant, but I would leave it out from this task. Same sitelink in two items is relevant, I add it above! --Epìdosis 10:41, 9 February 2023 (UTC) P.S. I would, but it seems it's too late. Anyway, it is another sure case of possible data duplication. --Epìdosis 10:44, 9 February 2023 (UTC)
- Also see https://phabricator.wikimedia.org/T44325 M2k~dewiki (talk) 08:54, 7 February 2023 (UTC)
- Note: you can also very easily add a new Wikidata item via Wikishootme. It is a great tool, but when there are no geocoordinates in an already existing Wikidata item about the same subject, then you do not see it in Wikishootme. So you always have to check first before you use the Wikishootme tool for making a new Wikidata item; but who does that? So in that tool the automatic check should also be implemented. --JopkeB (talk) 12:36, 11 February 2023 (UTC)
Voting
- Support --M2k~dewiki (talk) 18:45, 10 February 2023 (UTC)
- Support —2dk (talk) 19:22, 10 February 2023 (UTC)
- Support Strainu (talk) 20:22, 10 February 2023 (UTC)
- Support MHM (talk) 21:59, 10 February 2023 (UTC)
- Support Geert Van Pamel (WMBE) (talk) 22:14, 10 February 2023 (UTC)
- Support NMaia (talk) 00:00, 11 February 2023 (UTC)
- Support ··· 🌸 Rachmat04 · ☕ 02:42, 11 February 2023 (UTC)
- Support * Pppery * it has begun 04:03, 11 February 2023 (UTC)
- Support EpicPupper (talk) 05:34, 11 February 2023 (UTC)
- Support I have seen many data duplication problems so good suggestion. Goliv04053 (talk) 06:43, 11 February 2023 (UTC)
- Support Gohan 07:17, 11 February 2023 (UTC)
- Support HHill (talk) 08:30, 11 February 2023 (UTC)
- Support Muted Red Tulip (talk) 09:17, 11 February 2023 (UTC)
- Support Plaga med (talk) 11:19, 11 February 2023 (UTC)
- Support JopkeB (talk) 12:29, 11 February 2023 (UTC)
- Support Nw520 (talk) 12:32, 11 February 2023 (UTC)
- Support RVA2869 (talk) 14:54, 11 February 2023 (UTC)
- Support FinixFighter (talk) 15:17, 11 February 2023 (UTC)
- Support Betseg (talk) 03:45, 12 February 2023 (UTC)
- Support HLFan (talk) 08:57, 12 February 2023 (UTC)
- Support Ameisenigel (talk) 09:15, 12 February 2023 (UTC)
- Support Bencemac (talk) 20:23, 12 February 2023 (UTC)
- Support Elena moz (talk) 10:35, 13 February 2023 (UTC)
- Support Behnam N (talk) 13:12, 13 February 2023 (UTC)
- Support Syunsyunminmin 🗨️talk 14:07, 13 February 2023 (UTC)
- Support Libcub (talk) 02:42, 14 February 2023 (UTC)
- Support --Alexmar983 (talk) 10:37, 14 February 2023 (UTC)
- Support Ottawajin (talk) 09:24, 15 February 2023 (UTC)
- Support Jaider Msg 22:11, 15 February 2023 (UTC)
- Support Aishik Rehman (talk) 08:46, 16 February 2023 (UTC)
- Support Steam Flow (talk) 22:10, 16 February 2023 (UTC)
- Support DobryBrat (talk) 10:20, 17 February 2023 (UTC)
- Support DoublePendulumAttractor (talk) 05:59, 18 February 2023 (UTC)
- Support Kpjas (talk) 07:59, 18 February 2023 (UTC)
- Support --Yining Chen (Talk) 10:05, 18 February 2023 (UTC)
- Support Wikisaar (talk) 11:36, 18 February 2023 (UTC)
- Support We should prevent the duplication problem. Thingofme (talk) 16:09, 18 February 2023 (UTC)
- Support Gdafs (talk) 16:26, 18 February 2023 (UTC)
- Support Albinfo (talk) 22:13, 18 February 2023 (UTC)
- Support Elucches (talk) 23:10, 18 February 2023 (UTC)
- Support Scewing (talk) 21:06, 19 February 2023 (UTC)
- Support Czupirek (talk) 21:36, 19 February 2023 (UTC)
- Support Niskka2 (talk) 22:00, 19 February 2023 (UTC)
- Support — Omegatron (talk) 16:25, 20 February 2023 (UTC)
- Support Watty62 (talk) 17:50, 20 February 2023 (UTC)
- Support Nashona (talk) 18:18, 20 February 2023 (UTC)
- Support T. Wirbitzki (talk) 18:46, 20 February 2023 (UTC)
- Support cyrfaw (talk) 18:49, 20 February 2023 (UTC)
- Support +s MartinPoulter (talk) 13:36, 21 February 2023 (UTC)
- Support Serieminou (talk) 23:06, 21 February 2023 (UTC)
- Support Alessandra.Moi (talk) 16:00, 23 February 2023 (UTC)
- Support Bargioni (talk) 19:10, 23 February 2023 (UTC)
- Support --Deinocheirus (talk) 14:46, 24 February 2023 (UTC)
- Support Mutawakkilite (talk) 17:45, 24 February 2023 (UTC)
More languages for editing label
- Problem: When editing a label, only a few preselected languages appear. Finding how to choose these available languages in a pain (I found it once somewhere in the options, but I could not find it anymore).
- Proposed solution: When editing the label, add a button "Add more languages" or "Edit languages" under the few preselected languages.
- Who would benefit: People who edit in several languages.
- More comments:
- Phabricator tickets: phab:T126510
- Proposer: Sovxx (talk) 13:13, 29 January 2023 (UTC)
Discussion
- It could be done through d:Special:SetLabelDescriptionAliases and, more comfortably, labelLister in Special:Preferences#mw-prefsection-gadgets; probably we could just enable labelLister by default. --Epìdosis 14:59, 29 January 2023 (UTC)
- And link under box about all entered languages. --Wargo (talk) 21:25, 13 February 2023 (UTC)
- Currently, the babel box is the place where the language list is set. It's not easy to discover but it's an existing feature. ChristianKl ❪✉❫ 16:01, 30 January 2023 (UTC)
- Yes, but it was a very strange discovery for me: I wouldn't expect that list of languages I know = list of languages I would like to edit. — Draceane talkcontrib. 20:25, 8 February 2023 (UTC)
- I recently made a script to make it easier to add more languages: d:User:Nikki/AddTermboxLanguage.js. We really shouldn't need gadgets and scripts to be able to do it though. - Nikki (talk) 00:27, 13 February 2023 (UTC)
- Does this expand to include scripts? And the type of transliteration rules? In the case of Chinese language, the PINYIN transliteration could only apply to the modern texts (ie after 1950s). Older texts were either Wade-Giles or some others. Currently, there is none to specify in Wikidata . When simply applying "zh" code will show a display "中文" (zhōngwén), the scripts for Chinese characters. Thank you. ShiehJ (talk) 19:24, 15 February 2023 (UTC)
Voting
- Support Ja, detta tycker jag vore en klar förbättring av Wikidatas användarvänlighet Sabelöga (talk) 23:43, 10 February 2023 (UTC)
- Support It would be good having the ability to choose what languages to show by default. --Tinker Bell ★ ♥ 23:49, 10 February 2023 (UTC)
- Support NMaia (talk) 23:59, 10 February 2023 (UTC)
- Support ·addshore· talk to me! 00:12, 11 February 2023 (UTC)
- Support Gohan 07:08, 11 February 2023 (UTC)
- Support Martin-78 (discutailler) 08:34, 11 February 2023 (UTC)
- Support Muted Red Tulip (talk) 09:14, 11 February 2023 (UTC)
- Support Oltrepier (talk) 10:06, 11 February 2023 (UTC)
- Support And I agree with Tinker Bell. CaféBuzz (talk) 10:57, 11 February 2023 (UTC)
- Support Ecritures (talk) 11:10, 11 February 2023 (UTC)
- Support Having the list match the babe boxes is clever, but it would be nice to have a way to explicitly define these via the preferences (which would be more discoverable and intuitive). Waldyrious (talk) 11:32, 11 February 2023 (UTC)
- Support DerFussi 12:26, 11 February 2023 (UTC)
- Support Nw520 (talk) 12:32, 11 February 2023 (UTC)
- Support --Malvoört (talk) 13:41, 11 February 2023 (UTC)
- Support Кирилл С1 (talk) 14:36, 11 February 2023 (UTC)
- Support Perhaps a solution to this could be to make it easier to edit one's Babel box from a UI element available from every page? OwenBlacker (Talk) 15:17, 11 February 2023 (UTC)
- Support I agree with User:Waldyrious. Mbkv717 (talk) 17:02, 11 February 2023 (UTC)
- Support Betseg (talk) 03:43, 12 February 2023 (UTC)
- Support Matěj Suchánek (talk) 09:09, 12 February 2023 (UTC)
- Support Ameisenigel (talk) 09:15, 12 February 2023 (UTC)
- Support Mehman 09:41, 12 February 2023 (UTC)
- Support self supporting :) Sovxx (talk) 12:33, 12 February 2023 (UTC)
- Support Sun8908 (talk) 18:07, 12 February 2023 (UTC)
- Support Nikki (talk) 00:30, 13 February 2023 (UTC)
- Support Thomas Kinz (talk) 01:03, 13 February 2023 (UTC)
- Support Izno (talk) 08:10, 13 February 2023 (UTC)
- Support Wargo (talk) 21:21, 13 February 2023 (UTC)
- Support I thought this was a good idea in 2016 when I commented on the ticket and I still think it's a good idea 7 years (!) later. Tfmorris1 (talk) 23:34, 13 February 2023 (UTC)
- Support Libcub (talk) 02:39, 14 February 2023 (UTC)
- Support ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 17:38, 16 February 2023 (UTC)
- Support DoublePendulumAttractor (talk) 05:58, 18 February 2023 (UTC)
- Support --Yining Chen (Talk) 10:06, 18 February 2023 (UTC)
- Support We should add more languages for the label. Thingofme (talk) 16:12, 18 February 2023 (UTC)
- Support --Zache (talk) 05:00, 19 February 2023 (UTC)
- Support Jklamo (talk) 12:14, 19 February 2023 (UTC)
- Support Czupirek (talk) 21:36, 19 February 2023 (UTC)
- Support Mbrickn (talk) 03:14, 20 February 2023 (UTC)
- Support — Draceane talkcontrib. 12:46, 20 February 2023 (UTC)
- Support cyrfaw (talk) 18:43, 20 February 2023 (UTC)
- Support Tris T7 (talk) 19:36, 21 February 2023 (UTC)
Scientific papers: Sort authors by their own rank
- Problem: Sometimes the article is created with only authors with the property P2093 (only text without link), then some of them (all at the end...) are transfered to the property P50 (link to the good author page) but the authors are showned in the order of their addition to the page not to their own rank (P1545). It will be better, especially when there is a lot of authors, to have a sorting by this property. See for example this page with 14 authors currently showned as 2; 7; 1; 3; 5; 6; 9; 10; 11; 12; 13; 14 - and the last ones on the right order because I added by. [Sorry for my poor english!]
- Proposed solution: Add a sorting on the P1545 property for the field P50 and an another one for the field P2093.
- Who would benefit:
- More comments:
- Phabricator tickets: T173432
- Proposer: Givet (talk) 10:21, 24 January 2023 (UTC)
Discussion
- @Givet: You forgot to link "this page" !! —TheDJ (talk • contribs) 11:07, 24 January 2023 (UTC)
- @TheDJ: Thank you so much! Sorry for that. I just corrected. Givet (talk) 15:37, 24 January 2023 (UTC)
- This proposal seems to be too much focused on a single problem. While the problem exists, the solution should be more broadly applicable to user cases of sorting statements as well. ChristianKl ❪✉❫ 15:49, 24 January 2023 (UTC)
- @ChristianKl Yeah, this seems like a bot request (albeit very good) rather than a feature request.--Vojtěch Dostál (talk) 17:36, 25 January 2023 (UTC)
- I agree — I'd support a wish for a more general statement sort functionality (e.g. chronologically-sorted values like software releases, educated at, residence, etc.) Waldyrious (talk) 20:05, 11 February 2023 (UTC)
- Please link the Properties in the proposal too. Egon Willighagen (talk) 06:13, 11 February 2023 (UTC)
- In general I think that would be quite a useful functionality, but I think that this is a really specific niche problem that would not justify such changes in the general UI. However I can imagine this being an feature in the RearrangeValues Gadget. Once you activate the gadget on a property, it will also look for common qualifiers for the statements of that property and offer an option to sort the statements accordingly. That would than also work for other qualifiers, such as start time or end time. @Tohaomg:, do you have any thought on that idea? --DFichtmueller (talk) 12:32, 15 February 2023 (UTC)
Voting
- Support Geert Van Pamel (WMBE) (talk) 22:16, 10 February 2023 (UTC)
- Support LD (talk) 03:14, 11 February 2023 (UTC)
- Support Tgr (talk) 04:01, 11 February 2023 (UTC)
- Support Sorting by 'series ordinal' sounds useful to me, not just for authors, actually. Egon Willighagen (talk) 06:14, 11 February 2023 (UTC)
- Support Transient-understanding (talk) 07:58, 11 February 2023 (UTC)
- Support Bluerasberry (talk) 15:13, 11 February 2023 (UTC)
- Support I feel the same, I work with authors and it annoys me when I leave an item in a "messy" order. It's just a visual thing, I know I don't have to delete and add on purpose but it looks "shabby".--Alexmar983 (talk) 01:30, 12 February 2023 (UTC)
- Support Lt2818 (talk) 04:19, 12 February 2023 (UTC)
- Support Fvtvr3r (talk) 13:45, 12 February 2023 (UTC)
- Support Czupirek (talk) 11:27, 14 February 2023 (UTC)
- Support //Lollipoplollipoplollipop::talk 13:45, 14 February 2023 (UTC)
- Support Zblace (talk) 07:38, 18 February 2023 (UTC)
- Support This feature should be added. Thingofme (talk) 16:15, 18 February 2023 (UTC)
- Support cyrfaw (talk) 18:51, 20 February 2023 (UTC)
- Support This would be very usefull. Some of the users say Wikidata is just the database, so sorting doesn't matter. But I disagree with that. Wikidata is a database and also a resource of information. E.g. when you edit the article on another project, you may want to generate citations from Wikidata. Or when you are doing outreach trying to negotiate data from another database it would be helpful to show the name list in the order of their position on the paper. Juandev (talk) 11:15, 23 February 2023 (UTC)
Popup to link to or create a new Wikidata item after creating an article
- Problem: The problem of connecting newly created articles to existing objects respectivley creating new objects for unconnected pages (when, how, by whom, ...) for hundreds of newly created articles per day in different language versions, and how to avoid duplicates amongst the currently 105 million objects, has been discussed for years again and again without a real solution, for example at d:Wikidata:Requests for permissions/Bot/RegularBot 2
- Proposed solution: At d:Wikidata:Contact the development team/Archive/2020/09#Connecting newly created articles to existing objects resp. creating new object - additional step when creating articles, categories, etc. a possible solution has been discussed:
An additional step after saving a newly created article etc. to present to the user a list of possible matching wikidata objects (e.g. a list of persons with the same name; could be a similar algorithm as the duplicate check / suggestion list in PetScan, see for example this duplicity example
or the option to create a new object if no one matches (depending one the type of the object, some values could be already be pre-filled and pulled from the article, e.g. from categories or infoboxes). From my point of view, one current problem is, that a lot of creators of articles, categories, navigational items, templates, disambiguations, lists, commonscats, etc. are either not aware of the existance of wikidata or did forget to connect a newly created article etc. to an already existing object or to create a new one if not yet existing, which might lead to (more) duplicates, if this creation respectivley connection is not done manually, but by a bot instead, which have to be merged manually afterwards.
This pop-up should be presented for:
- newly created articles in the article namespace
- articles that have been moved from user/draft namespace to article namespace
- articles, that have been expanded from a redirect
- newly created categories
- In addition, there could be specialized (depending on the type of the objects, e.g. one bot for humans, one for films, one for buildings, etc.) bots, which are for example able to check for various IDs (like GND, VIAF, LCCN, IMDb, monument-IDs ...) in order to avoid creating duplicates and creates new items or connects matching items based on IDs.
Also, if someone uses the "translation function" to create a translated article in another language version, then the new translated article could be connected automatically to the object of the original article. And after a version import (after a translation), at the moment often the link to the Wikidata object gets lost and the article has to be reconnected again a second time manually.
Also see:
- Community Wishlist Survey 2021/Wikidata/Creation of new objects resp. connecting to existing objects while avoiding duplicates
- Community Wishlist Survey 2022/Wikidata/Creation of new objects resp. connecting to existing objects while avoiding duplicates
- Community Wishlist Survey 2022/Wikidata/Autosuggest linking Wikidata item after creating an article
- and
- d:Wikidata:Project_chat/Archive/2022/11#Reducing_the_backlog_of_unconnected_pages_on_a_regular_base
- de:Benutzer:M2k~dewiki/FAQ#Technische_Wünsche_/_Wunschliste_/_Wishlist
- de:Benutzer:M2k~dewiki/FAQ#Wie_finde_ich_ein_bestehendes_Wikidata-Objekt_zu_einem_Artikel?
- de:Benutzer:M2k~dewiki/FAQ#Warum_fehlen_die_von_mir_gewünschten_Informationen_im_neu_erstellten_Wikidata-Objekt?
Statistics of unconnected articles:
- https://wikidata-todo.toolforge.org/duplicity.php?mode=stats&wiki=enwiki
- https://wikidata-todo.toolforge.org/duplicity.php?mode=stats&wiki=itwiki
- https://wikidata-todo.toolforge.org/duplicity.php?mode=stats&wiki=plwiki
- https://wikidata-todo.toolforge.org/duplicity.php?mode=stats&wiki=nowiki
- https://wikidata-todo.toolforge.org/duplicity.php?wiki=trwiki&mode=stats
- https://wikidata-todo.toolforge.org/duplicity.php?wiki=jawiki&mode=stats
- https://wikidata-todo.toolforge.org/duplicity.php?wiki=ukwiki&mode=stats
- https://wikidata-todo.toolforge.org/duplicity.php?wiki=ruwiki&mode=stats
- https://wikidata-todo.toolforge.org/duplicity.php?
- Who would benefit: Improved data quality, i.e. less duplicates ; users are able to switch beetween languages and projects
- More comments:
- Phabricator tickets: T308059, T178249, T312927
- Proposer: M2k~dewiki (talk) 18:26, 23 January 2023 (UTC)
This wish now has a project page. Please consult it for development updates. –– STei (WMF) (talk) 10:50, 24 April 2024 (UTC)
Discussion
- See also another idea on linking new pages to Wikidata items: phab:T178249. — putnik 22:05, 23 January 2023 (UTC)
- Doesn't a bot already do this for unattached articles? Also if this pops up after a new article creation, it's unlikely to have any of the identifiers to avoid creating duplicate entries (speaking from experience). I generally create Wikidata entries but I always have to search first as it's unpredictable what's already in the system. czar 22:27, 29 January 2023 (UTC)
- Hello @Czar:, for a bot it is hard to decide if two articles in different languages actually described the same entity (the same movie, building, sport event/sport season, organisation, mountain, river, city, taxon, chemical substance, flight incident, ...). A bot might use some IDs for this (e.g. CAS-ID for chemicals, ASN-ID for flight incidents, VIAF for persons, various country dependent monument IDs for monuments, SANDRE-ID for rivers in France, IMDb for movies, ...) to match articles in different languages (if it is able to extract this IDs from the articles in various languages at all, e.g. if these IDs are used in templates). Even for wikidata objects for persons its is hard to decide if two articles describe the same person, due to different spellings of the name even in the same language (especially for people who lived centuries ago, as well as different languages/alphabets as russian, japanese, korean, greek, ...). So, if an author does research for writing an article, he/she might have already found out, that there is already an article in other languages, so some information and sources from these articles might have been used for the newley created article. When publishing such an article, the author only has to connect to the existing object/articles he/she has found during researching for writing the article. In my opinion, if done manually, the probabilty to create duplicates is far lower than if this is done by a bot, although there always will be some duplicates with both methods. From my point of view, a lot of (new) authors do not know about the existance of Wikidata and the possibility to link/connect a new article to other languages. The pop-up might be a way, that authors are informed automatically about this possibility. M2k~dewiki (talk) 23:38, 29 January 2023 (UTC)
- The absence of a pop up, a bot for connecting to existing objects, or some other mechanism regularly leads to backlogs with some thousands of unconnected articles:
- https://wikidata-todo.toolforge.org/duplicity.php?mode=stats&wiki=enwiki
- https://wikidata-todo.toolforge.org/duplicity.php?mode=stats&wiki=itwiki
- https://wikidata-todo.toolforge.org/duplicity.php?mode=stats&wiki=plwiki
- https://wikidata-todo.toolforge.org/duplicity.php?mode=stats&wiki=nowiki
- https://wikidata-todo.toolforge.org/duplicity.php?wiki=trwiki&mode=stats
- https://wikidata-todo.toolforge.org/duplicity.php?wiki=jawiki&mode=stats
- https://wikidata-todo.toolforge.org/duplicity.php?wiki=ukwiki&mode=stats
- https://wikidata-todo.toolforge.org/duplicity.php?wiki=ruwiki&mode=stats
- A bot mainly can create new objects for unconnected articles (independent of the existence in other languages), but hardly can decided, if an existing objects in one language describes the same entity in another language. Therefore, objects created by a bot might have to be merged afterwards manually at least more often, than objects where a human decided, if this subject already might exist in other languages or not. M2k~dewiki (talk) 23:49, 29 January 2023 (UTC)
- The absence of a pop up, a bot for connecting to existing objects, or some other mechanism regularly leads to backlogs with some thousands of unconnected articles:
- Hello @Czar:, for a bot it is hard to decide if two articles in different languages actually described the same entity (the same movie, building, sport event/sport season, organisation, mountain, river, city, taxon, chemical substance, flight incident, ...). A bot might use some IDs for this (e.g. CAS-ID for chemicals, ASN-ID for flight incidents, VIAF for persons, various country dependent monument IDs for monuments, SANDRE-ID for rivers in France, IMDb for movies, ...) to match articles in different languages (if it is able to extract this IDs from the articles in various languages at all, e.g. if these IDs are used in templates). Even for wikidata objects for persons its is hard to decide if two articles describe the same person, due to different spellings of the name even in the same language (especially for people who lived centuries ago, as well as different languages/alphabets as russian, japanese, korean, greek, ...). So, if an author does research for writing an article, he/she might have already found out, that there is already an article in other languages, so some information and sources from these articles might have been used for the newley created article. When publishing such an article, the author only has to connect to the existing object/articles he/she has found during researching for writing the article. In my opinion, if done manually, the probabilty to create duplicates is far lower than if this is done by a bot, although there always will be some duplicates with both methods. From my point of view, a lot of (new) authors do not know about the existance of Wikidata and the possibility to link/connect a new article to other languages. The pop-up might be a way, that authors are informed automatically about this possibility. M2k~dewiki (talk) 23:38, 29 January 2023 (UTC)
- How would this work for non-Wikipedia projects? Wikisource items are editions of specific works, that have their own publication data, and they usually should not be added to any existing Wikidata item because they have their own publication data (specific to that edition) that needs to be recorded in a data item for that edition. Would this pop-up recognize the difference between needing a Wikidata item for an edition (specific to Wikidata and to the scan of that edition on Commons) versus a Wikidata item for the work itself, which would link to Wikipedia articles, Commons Categories (not scans), and Wikiquote? Or will the pop-up look for closely-matching items regardless of these issues? The very fact that this proposal is about "articles" shows that it doesn't consider the issues inherent with non-Wikipedia projects. --EncycloPetey (talk) 20:16, 23 January 2023 (UTC)
- This functionality could be available on a project base respectivley on a language base, so every community of every project and language version could decide, if this feature should be (de)activated. --M2k~dewiki (talk) 20:42, 23 January 2023 (UTC)
- That response does not address the problem I raised. If Wikipedia has it active, but they are adding links for works to editions items, that's a problem, because Wikipedia is then adding information incorrectly to data items. Likewise, if a Wikisource has this active, but it puts links for an edition into a work data item, then it's added the information incorrectly. If English Wikisource has this active, and it causes English edition links for an English edition to be added to a data item for a French edition, then the information has been added incorrectly. Your response does not address these issues. --EncycloPetey (talk) 16:08, 25 January 2023 (UTC)
- Editions could be filtered out in the result sets presented by for example duplicity: https://wikidata-todo.toolforge.org/duplicity.php?wiki=dewiki&norand=1&page=Vasco%5FCordeiro --M2k~dewiki (talk) 16:12, 25 January 2023 (UTC)
- Then how would links be added if the desired target is to be an edition? If it is information for a specific publication, then it's an edition. 99% of data items for Wikisource projects are editions. When a published reference is to be cited, it's a specific edition. And the example link you provided makes no sense in terms of the context of this discussion. Do you understand the difference between a work and an edition? --EncycloPetey (talk) 16:20, 25 January 2023 (UTC)
- Editions could be filtered out in the result sets presented by for example duplicity: https://wikidata-todo.toolforge.org/duplicity.php?wiki=dewiki&norand=1&page=Vasco%5FCordeiro --M2k~dewiki (talk) 16:12, 25 January 2023 (UTC)
- That response does not address the problem I raised. If Wikipedia has it active, but they are adding links for works to editions items, that's a problem, because Wikipedia is then adding information incorrectly to data items. Likewise, if a Wikisource has this active, but it puts links for an edition into a work data item, then it's added the information incorrectly. If English Wikisource has this active, and it causes English edition links for an English edition to be added to a data item for a French edition, then the information has been added incorrectly. Your response does not address these issues. --EncycloPetey (talk) 16:08, 25 January 2023 (UTC)
- I've merged "Add interlanguage links" interface should let users input sister wiki pages into this proposal, because it looks like both can be solved with a system of presenting possible existing Wikidata items (and optionally creating a new one with the sitelink already added). These tasks are what the AutosuggestSitelink gadget is aiming to solve, so I'd suggest that we'd look at adding any missing functionality there. For example, when creating a new Wikisource edition page, often there is no item for the edition but we could prompt to find the appropriate work item and if one exists create the edition item with all links as appropriate. (Details t.b.d. of course! Hopefully I'm not handwaving away something impossible there.) SWilson (WMF) (talk) 07:17, 1 February 2023 (UTC)
- Hello @SWilson (WMF): thanks for the information about the AutosuggestSitelink gadget, which I just have activated:
- and tried to connect
- to an object ( https://www.wikidata.org/wiki/Q75243783 has been already existing), but got the error message:
- Something went wrong: Unable to parse the messages page meta:MediaWiki:Gadget-AutosuggestSitelink-messages/de. There may have been a recent change that contains invalid JSON.
- Also, in my opinion there should be no (error) message at all when creating a redirect.
- Are there any plans to activate the AutosuggestSitelink gadget for a broader range of users per default after a test phase or does every single user explicitly have to activate the gadget? M2k~dewiki (talk) 19:52, 1 February 2023 (UTC)
- @M2k~dewikiThank you for taking a look at this new AutosuggestSitelink gadget. I just posted on the proposal's talk page from the Wishlist Survey 2022. We are currently taking feedback. We'll take a look at error you experienced and please let us know if the talk page if you find any further issues. Do you mind updating this proposal so that the problem and solution is about the improvements you'd like to see in this new AutosuggestSitelink gadget? Thank you! HMonroy (WMF) (talk) 21:10, 1 February 2023 (UTC)
Voting
- Support Exilexi (talk) 09:13, 11 February 2023 (UTC)
- Support Muted Red Tulip (talk) 09:22, 11 February 2023 (UTC)
- Support Shizhao (talk) 13:55, 11 February 2023 (UTC)
- Support Кирилл С1 (talk) 14:35, 11 February 2023 (UTC)
- Support Bluerasberry (talk) 15:14, 11 February 2023 (UTC)
- Support OwenBlacker (Talk) 15:14, 11 February 2023 (UTC)
- Support CROIX (talk) 15:18, 11 February 2023 (UTC)
- Support --NGC 54 (talk|contribs) 01:08, 12 February 2023 (UTC)
- Support Mauricio V. Genta (talk) 08:02, 12 February 2023 (UTC)
- Support Bencemac (talk) 20:27, 12 February 2023 (UTC)
- Support Husky (talk) 21:13, 12 February 2023 (UTC)
- Support Libcub (talk) 02:59, 14 February 2023 (UTC)
- Support Ottawajin (talk) 09:22, 15 February 2023 (UTC)
- Support Lupe (talk) 21:20, 15 February 2023 (UTC)
- Support Fuchs B (talk) 20:11, 17 February 2023 (UTC)
- Support ArthurPSmith (talk) 20:59, 17 February 2023 (UTC)
- Support Zblace (talk) 07:36, 18 February 2023 (UTC)
- Support This is extremely needed!!! Thingofme (talk) 16:17, 18 February 2023 (UTC)
- Support Albinfo (talk) 22:11, 18 February 2023 (UTC)
- Support Jklamo (talk) 12:17, 19 February 2023 (UTC)
- Support — Draceane talkcontrib. 12:44, 20 February 2023 (UTC)
- Support Nashona (talk) 18:13, 20 February 2023 (UTC)
- Support cyrfaw (talk) 18:43, 20 February 2023 (UTC)
- Support Serieminou (talk) 23:13, 21 February 2023 (UTC)
- Support Kalendar (talk) 06:37, 22 February 2023 (UTC)
- Support Carsrac (talk) 12:52, 22 February 2023 (UTC)
- Support Dajasj (talk) 13:54, 22 February 2023 (UTC)
- Support Rots61 (talk) 14:11, 22 February 2023 (UTC)
- Support Gusfriend (talk) 00:33, 23 February 2023 (UTC)
- Support JiriMatejicek (talk) 09:39, 24 February 2023 (UTC)
- Support Matěj Suchánek (talk) 17:05, 24 February 2023 (UTC)
Improve handling of dates in languages other than English
- Problem: Wikidata does not display dates correctly in many languages. When entering data, it also cannot parse many common forms of dates in other languages. This makes Wikidata difficult to use in other languages. e.g. 1997-02-01 is displayed in Chinese and Japanese as "1 2 1997" instead of "1997年2月1日". When editing, it does not understand "1997年2月1日" even when the interface is in Japanese. In Spanish, it can parse "11 mayo 1961" but not "11 de mayo de 1961". In German it can parse "1. März 2000" but not "1. märz 2000". It can parse "01.02.1997" if the language is Slovak, but not if the language is Czech.
- Proposed solution: Display dates using the date format from MediaWiki. Improve the parsing of dates so that it can understand dates written in the usual format for that language.
- Who would benefit: Non-English speakers using Wikidata
- More comments: This is a long-standing problem which has been proposed here multiple times in the past:
- Phabricator tickets: phab:T63958, phab:T221097, phab:T214002, phab:T65732, phab:T260699
- Proposer: Nikki (talk) 13:25, 5 February 2023 (UTC)
Discussion
- As I was told, phab:T221097 should be fixed in the following days. The bugfix only concerns parsing, though. --Matěj Suchánek (talk) 14:11, 5 February 2023 (UTC)
- Long-standing problem. I can just add two personal experiences with Italian interface: it parses months with lowercase initial (e.g. 22 marzo 2022) but not with less common (but sometimes used) uppercase initial (e.g. 22 Marzo 2022); since in Italy the most-common usage is dd mm yyyy, I can say that dd-mm-yyyy and dd mm yyyy are interpreted correctly, whilst dd/mm/yyyy is interpreted wrongly as mm/dd/yyyy (which can cause errors, if the user doesn't notice the problem when saving). I think this inversion of month and day is a problem perceived also in other languages: probably, in ambiguous cases (e.g. 01/02/2022), the system should just present the two options to the user and ask them to choose, in order to avoid misinterpretations. --Epìdosis 18:46, 5 February 2023 (UTC)
- + phab:T167788 Ayack (talk) 08:22, 13 February 2023 (UTC)
- It is likely a super challenge (a pipe dream) asking for an ability to translate dates from lunisolar calendar to the Gregorian system. It is an unfortunate task for editors who tried to decipher dates from a primary source that deployed an emperor's era. For instance,"清高宗乾隆丁亥四月十九日" (transliteration: Qing Gaozong Qianlong Ding hai si yue shijiu ri; translated to Gaozong of Qing, Qianlong Emperor, 32nd year, 4th month, 19th day) to the Gregorian date, 1767 May 16. Nevertheless, if somehow a system could push forward a year, such as 民國一百一十二年 (minguo 112) to 2023. That would be a great start! Is that even possible? Thank you. ShiehJ (talk) 19:39, 15 February 2023 (UTC)
- For everyone following this discussion, there is an upcoming Bug Triage Hour on dates input that may be of interest to you all. On March 13th, we will be following up on an issue with date parsing in the Czech language (T221097) that was fixed in February. During the Bug Triage Hour, we will be looking at the changes induced by this fix together, checking how the date input parsing works in different languages, and identifying any possibly remaining issues. This may be a great opportunity for those concerned with the handling of dates in languages other than English to get involved and provide feedback. -Mohammed Sadat (WMDE) (talk) 10:39, 6 March 2023 (UTC)
Voting
- Support Strainu (talk) 20:20, 10 February 2023 (UTC)
- Support TLSOSLT (talk) 21:23, 10 February 2023 (UTC)
- Support Joalpe (talk) 21:45, 10 February 2023 (UTC)
- Support عُثمان (talk) 23:34, 10 February 2023 (UTC)
- Support NMaia (talk) 00:01, 11 February 2023 (UTC)
- Support ·addshore· talk to me! 00:13, 11 February 2023 (UTC)
- Support - PKM (talk) 00:17, 11 February 2023 (UTC)
- Support ··· 🌸 Rachmat04 · ☕ 02:41, 11 February 2023 (UTC)
- Support HHill (talk) 08:33, 11 February 2023 (UTC)
- Support --Epìdosis 08:42, 11 February 2023 (UTC)
- Support Envlh (talk) 09:17, 11 February 2023 (UTC)
- Support Oltrepier (talk) 10:08, 11 February 2023 (UTC)
- Support Nw520 (talk) 12:33, 11 February 2023 (UTC)
- Support Кирилл С1 (talk) 14:36, 11 February 2023 (UTC)
- Support OwenBlacker (Talk) 15:15, 11 February 2023 (UTC)
- Support Mbkv717 (talk) 16:59, 11 February 2023 (UTC)
- Support Abzeronow (talk) 19:18, 11 February 2023 (UTC)
- Support --NGC 54 (talk|contribs) 01:07, 12 February 2023 (UTC)
- Support Ahkei (talk) 01:49, 12 February 2023 (UTC)
- Support Betseg (talk) 03:44, 12 February 2023 (UTC)
- Support Mauricio V. Genta (talk) 08:02, 12 February 2023 (UTC)
- Support HLFan (talk) 08:52, 12 February 2023 (UTC)
- Support Ameisenigel (talk) 09:13, 12 February 2023 (UTC)
- Support Mehman 09:41, 12 February 2023 (UTC)
- Support QuickQuokka [talk • contribs] 16:58, 12 February 2023 (UTC)
- Support Bencemac (talk) 20:21, 12 February 2023 (UTC)
- Support Thomas Kinz (talk) 01:01, 13 February 2023 (UTC)
- Support Xayala Mammadli (talk) 05:35, 13 February 2023 (UTC)
- Support Ayack (talk) 08:15, 13 February 2023 (UTC)
- Support — putnik 08:41, 13 February 2023 (UTC)
- Support TiagoLubiana (talk) 18:47, 13 February 2023 (UTC)
- Support Excellence (talk) 20:25, 13 February 2023 (UTC)
- Support JAn Dudík (talk) 21:53, 13 February 2023 (UTC)
- Support Libcub (talk) 02:51, 14 February 2023 (UTC)
- Support Mikxth (talk) 12:10, 14 February 2023 (UTC)
- Support Elilopes (talk) 17:06, 14 February 2023 (UTC)
- Support doesn't seem that hard BrokenSegue 22:30, 14 February 2023 (UTC)
- Support Ottawajin (talk) 09:21, 15 February 2023 (UTC)
- Support Moebeus (talk) 12:43, 15 February 2023 (UTC)
- Support ShiehJ (talk) 19:25, 15 February 2023 (UTC)
- Support --Polarlys (talk) 21:36, 15 February 2023 (UTC)
- Support --Melderick (talk) 21:53, 15 February 2023 (UTC)
- Support ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 17:39, 16 February 2023 (UTC)
- Support Husky22 (talk) 19:22, 16 February 2023 (UTC)
- Support Steam Flow (talk) 22:10, 16 February 2023 (UTC)
- Support I didn't realize it was this bad, but yes this should be fixed. ArthurPSmith (talk) 20:58, 17 February 2023 (UTC)
- Support --Yining Chen (Talk) 10:07, 18 February 2023 (UTC)
- Support Fabius Lector (talk) 10:40, 18 February 2023 (UTC)
- Support Herbert Ortner (talk) 14:28, 18 February 2023 (UTC)
- Support Vulcan❯❯❯Sphere! 16:14, 18 February 2023 (UTC)
- Support This should be fixed to improve dates handling. Thingofme (talk) 16:19, 18 February 2023 (UTC)
- Support Christian (talk) 20:27, 18 February 2023 (UTC)
- Support Jklamo (talk) 12:16, 19 February 2023 (UTC)
- Support Niskka2 (talk) 21:59, 19 February 2023 (UTC)
- Support Mule hollandaise (talk) 05:25, 20 February 2023 (UTC)
- Support Matěj Suchánek (talk) 08:26, 20 February 2023 (UTC)
- Support — Draceane talkcontrib. 12:44, 20 February 2023 (UTC)
- Support cyrfaw (talk) 18:52, 20 February 2023 (UTC)
- Support Higa4 (talk) 03:38, 21 February 2023 (UTC)
- Support Serieminou (talk) 23:08, 21 February 2023 (UTC)
- Support Tris T7 (talk) 02:18, 22 February 2023 (UTC)
- Support Computerz4 (talk) 17:45, 22 February 2023 (UTC)
- Support Morten Haan (talk) 18:50, 22 February 2023 (UTC)
- Support --Tchoř (talk) 10:17, 23 February 2023 (UTC)
Ability to reorder statements
- Problem: Wikidata statements for the same property are shown in the order they are added to Wikidata. In many cases, there's a natural order that can derivate from the order in which the statements were added.
A user that wants to fix the order has to delete and recreate the statement which is undesirable. While external data users can configure their scripts to use a property like "point in time" to order the statements, users within Wikidata have no way to order them.
- Proposed solution: Add a feature that exchanges the position of two statements which use the same property within an item.
- Who would benefit: All users who access items that are currently unordered directly within the Wikidata UI.
- More comments:
- Phabricator tickets: T173432
- Proposer: ChristianKl ❪✉❫ 15:46, 24 January 2023 (UTC)
Discussion
- @ChristianKl: Have you checked the Rearrange Values gadget? Ayack (talk) 08:35, 25 January 2023 (UTC)
- I just checked the gadget list, and you are right that the gadget solves the problem. So this wishlist item can be closed. I don't know whether there's a process for withdrawing wishlist entries.ChristianKl ❪✉❫ 19:30, 26 January 2023 (UTC)
- I am against withdrawing it, since this feature should be built in Wikibase UI.--GZWDer (talk) 23:39, 8 February 2023 (UTC)
- Agreed. The gadget works well and I use it all the time, but this should be implemented natively.
- Waldyrious (talk) 20:09, 11 February 2023 (UTC)
- I am against withdrawing it, since this feature should be built in Wikibase UI.--GZWDer (talk) 23:39, 8 February 2023 (UTC)
- I just checked the gadget list, and you are right that the gadget solves the problem. So this wishlist item can be closed. I don't know whether there's a process for withdrawing wishlist entries.ChristianKl ❪✉❫ 19:30, 26 January 2023 (UTC)
- WD is so very open. I wonder if this can be customized by associating with username in the preferences setup? In addition, hopefully, also making its way to Wikibase for local implementation? Thanks. ShiehJ (talk) 13:38, 17 February 2023 (UTC)
Voting
- Support Sabelöga (talk) 23:58, 10 February 2023 (UTC)
- Support NMaia (talk) 00:04, 11 February 2023 (UTC)
- Oppose If some set of statements has a particular order, they should be marked with P1545, P1352, or another applicable property, I think we don't rely on Wikidata implementation to mark this info. On the other hand, I think it would be good that UI show the data already arranged, based on the qualifiers if these exists, but not modifying the statements. --Tinker Bell ★ ♥ 00:06, 11 February 2023 (UTC)
- I agree with Tinker Bell. Maybe have a property for properties like “Sort statements by qualifier” = Reason for preference/Rank 1, Point in time/Rank 2, Start/Rank 3, End/Rank 4, Reason for deprecation/Rank 5, …. --Nw520 (talk) 12:38, 11 February 2023 (UTC)
- Hello @Tinker Bell and Nw520: it is already possible to re-arrange the order of the values within a single property, for example the actors in a movie, using the Rearrange Values gadget .
- M2k~dewiki (talk) 12:43, 11 February 2023 (UTC)
- IMHO the order of values should be a front-end-only property and automatically set by Mediawiki using a statement's qualifiers. Making users manually do that feels like wasted (hu)man-power (and makes watchlists even more bloated). --Nw520 (talk) 12:51, 11 February 2023 (UTC)
- I agree with Tinker Bell. Maybe have a property for properties like “Sort statements by qualifier” = Reason for preference/Rank 1, Point in time/Rank 2, Start/Rank 3, End/Rank 4, Reason for deprecation/Rank 5, …. --Nw520 (talk) 12:38, 11 February 2023 (UTC)
- Support * Pppery * it has begun 04:03, 11 February 2023 (UTC)
- Support Franz.wohlkoenig (talk) 06:29, 11 February 2023 (UTC)
- Support Joseph (talk) 13:26, 11 February 2023 (UTC)
- Support Betseg (talk) 03:44, 12 February 2023 (UTC)
- Support Will make it much easier to find the relevant properties when looking at items. Ɱ (talk) 02:25, 14 February 2023 (UTC)
- Support Thibaultmol (talk) 18:07, 14 February 2023 (UTC)
- Support DFlhb (talk) 19:31, 16 February 2023 (UTC)
- Support Steam Flow (talk) 22:09, 16 February 2023 (UTC)
- Support Kpjas (talk) 08:09, 18 February 2023 (UTC)
- Support There should be a way to reorder statements. Thingofme (talk) 16:10, 18 February 2023 (UTC)
- Oppose I am probably repeating myself or others, but in fact Wikibase data model says nothing about the order of data. So this wish is asking for management of something that does not exist. Different contexts may require different ordering (e.g., by surname vs. by level of contribution), that's even more complexity to be added to the system. Otherwise, we need to change the data model and implement proper support in APIs. --Matěj Suchánek (talk) 11:28, 19 February 2023 (UTC)
- Oppose the ability to manually sort will lead users to think that this manual sorting actually works. In reality, the industry-accepted data interface is RDF/JSON-LD/SPARQL, all of which do not support property sorting. To clarify: I'm not against improving visualization, let javascript sort by "start date" or "sequential number" qualifier for example, but it shouldn't be done by the editors. --Lockal (talk) 06:38, 20 February 2023 (UTC)
- Support Ebukadneza (talk) 10:54, 20 February 2023 (UTC)
- Support — Draceane talkcontrib. 12:45, 20 February 2023 (UTC)
- Support cyrfaw (talk) 18:48, 20 February 2023 (UTC)
- Support User:Bahnmoeller —Preceding undated comment added 13:50, 22 February 2023 (UTC).
- Support Juandev (talk) 11:20, 23 February 2023 (UTC)
- Oppose per Lockal; also, a gadget exists already and I don't think this needs further development (see other gadgets like moveClaim or dataDrainer). ~~~~
User:1234qwer1234qwer4 (talk) 17:57, 24 February 2023 (UTC)
Default collapse statements when they have many values
- Problem: Some Wikidata items have a huge number of statements for some properties. A few examples are populations on human settlements and administrative areas (e.g. d:Q183#P1082), versions on software (e.g. d:Q83#P348) and number of deaths on COVID-19 items (e.g. d:Q87477462#P1120) but there are many more. This makes these items very tedious to navigate, as they require an excessive amount of scrolling. This was discussed on Wikidata four years ago, and resurfaced last fall (connected to a larger issue).
- Proposed solution: If a statement has more than just a few values, perhaps even as low as three, the entire statement could be "collapsed" to just show the property name, how many values it has, and a way to expand it. A nice-to-have is if expanding a property is "remembered" across items, as it is not unusual to work on the same property on a number of items and repeatedly having to unfold it then also would be tedious. Also, since a small number of editors working on these kinds of properties might not want to have this behavior at all, it should be possible to turn it off in the preferences (or by turning off the gadget, if that is how it is implemented).
- Who would benefit: Editors and readers of Wikidata.
- More comments:
- Phabricator tickets: Tickets:
- Foldable/Collapsable statements for multivalued properties (T239820).
- Also related to the problem is Provide a way to avoid loading all statements when opening a new Wikidata item (T158182) although that is a bit more far-stretching proposal.
- Proposer: ♥Ainali talkcontributions 19:14, 29 January 2023 (UTC)
Discussion
- As a workaround, the updown.js user script adds clickable arrows to jump to the last or first value of such statements. Dexxor (talk) 09:24, 11 February 2023 (UTC)
- In addition to completely collapsing those lists of values, they could have a max height shown by default, which would then need to be manually expanded to show the entire list. --Waldyrious (talk) 19:23, 11 February 2023 (UTC)
Voting
- Support Onthewings (talk) 21:22, 10 February 2023 (UTC)
- Support Tom Ja (talk) 21:40, 10 February 2023 (UTC)
- Support Joshbaumgartner (talk) 23:03, 10 February 2023 (UTC)
- Support عُثمان (talk) 23:33, 10 February 2023 (UTC)
- Support NMaia (talk) 00:05, 11 February 2023 (UTC)
- Support PKM (talk) 00:21, 11 February 2023 (UTC)
- Support Poslovitch (talk) 00:24, 11 February 2023 (UTC)
- Support EijiroSaito (talk) 01:03, 11 February 2023 (UTC)
- Support ··· 🌸 Rachmat04 · ☕ 02:42, 11 February 2023 (UTC)
- Support Tgr (talk) 04:03, 11 February 2023 (UTC)
- Support Franz.wohlkoenig (talk) 06:27, 11 February 2023 (UTC)
- Support Gohan 07:11, 11 February 2023 (UTC)
- Support --Epìdosis 08:43, 11 February 2023 (UTC)
- Support Muted Red Tulip (talk) 09:28, 11 February 2023 (UTC)
- Support to improve performance on big items Dexxor (talk) 09:36, 11 February 2023 (UTC)
- Support CaféBuzz (talk) 10:56, 11 February 2023 (UTC)
- Support Waldyrious (talk) 11:33, 11 February 2023 (UTC)
- Support Nw520 (talk) 12:31, 11 February 2023 (UTC)
- Support Joseph (talk) 13:25, 11 February 2023 (UTC)
- Support RVA2869 (talk) 14:53, 11 February 2023 (UTC)
- Support JackPotte (talk) 15:01, 11 February 2023 (UTC)
- Support Bluerasberry (talk) 15:14, 11 February 2023 (UTC)
- Support Bigbossfarin (talk) 17:00, 11 February 2023 (UTC)
- Support Ahkei (talk) 01:49, 12 February 2023 (UTC)
- Support Betseg (talk) 03:44, 12 February 2023 (UTC)
- Support HLFan (talk) 08:52, 12 February 2023 (UTC)
- Support Mehman 09:40, 12 February 2023 (UTC)
- Support Fvtvr3r (talk) 13:44, 12 February 2023 (UTC)
- Support QubeCube (talk) 14:38, 12 February 2023 (UTC)
- Support LevandeMänniska (talk) 14:39, 12 February 2023 (UTC)
- Support Arvelius (talk) 14:41, 12 February 2023 (UTC)
- Support My preferred behaviour would be to show the preferred value in the collapsed state. ProbabilityCollapse (talk) 17:49, 12 February 2023 (UTC)
- Support Bencemac (talk) 20:18, 12 February 2023 (UTC)
- Support Husky (talk) 21:13, 12 February 2023 (UTC)
- Support Thomas Kinz (talk) 01:07, 13 February 2023 (UTC)
- Support TiagoLubiana (talk) 18:45, 13 February 2023 (UTC)
- Support JAn Dudík (talk) 21:49, 13 February 2023 (UTC)
- Support Gillum (talk) 22:46, 13 February 2023 (UTC)
- Support +1 YjM (talk) 23:09, 13 February 2023 (UTC)
- Support Libcub (talk) 02:44, 14 February 2023 (UTC)
- Support Just N. (talk) 14:46, 14 February 2023 (UTC)
- Support VIGNERON * discut. 19:53, 14 February 2023 (UTC)
- Support DFichtmueller (talk) 12:01, 15 February 2023 (UTC)
- Support Aishik Rehman (talk) 08:45, 16 February 2023 (UTC)
- Support Steam Flow (talk) 22:08, 16 February 2023 (UTC)
- Support Fexpr (talk) 09:09, 17 February 2023 (UTC)
- Support DobryBrat (talk) 10:37, 17 February 2023 (UTC)
- Support DoublePendulumAttractor (talk) 05:59, 18 February 2023 (UTC)
- Support Zblace (talk) 07:37, 18 February 2023 (UTC)
- Support Kpjas (talk) 08:10, 18 February 2023 (UTC)
- Support --Yining Chen (Talk) 10:08, 18 February 2023 (UTC)
- Support Herbert Ortner (talk) 14:04, 18 February 2023 (UTC)
- Support Vulcan❯❯❯Sphere! 16:13, 18 February 2023 (UTC)
- Support Support as the number of statements can be extremely large to get through. Thingofme (talk) 16:16, 18 February 2023 (UTC)
- Oppose Christian (talk) 20:30, 18 February 2023 (UTC)
- Support Jklamo (talk) 12:15, 19 February 2023 (UTC)
- Support Matlin (talk) 13:33, 19 February 2023 (UTC)
- Support Jotamide (talk) 15:34, 19 February 2023 (UTC)
- Support β16 - (talk) 10:38, 20 February 2023 (UTC)
- Support Ebukadneza (talk) 10:54, 20 February 2023 (UTC)
- Support — Draceane talkcontrib. 12:45, 20 February 2023 (UTC)
- Support Watty62 (talk) 17:48, 20 February 2023 (UTC)
- Support Nashona (talk) 18:14, 20 February 2023 (UTC)
- Support cyrfaw (talk) 18:47, 20 February 2023 (UTC)
- Support Tris T7 (talk) 02:16, 22 February 2023 (UTC)
- Support Dajasj (talk) 13:54, 22 February 2023 (UTC)
- Support Juandev (talk) 11:23, 23 February 2023 (UTC)
Optional native language label language name
- Problem: In the label box on Wikidata, all names are printed in Swedish, this bothers me a bit as I want to be able to read them in the native language instead, for example Deutsch instead of German, français instead of French, etc.
- Proposed solution: Introducing the technical possibility to change the display language of the labels so that you can choose whether you want translated or native names on the labels
- Who would benefit: People who mostly edit in a few languages and don't necessarily want to see them translated into the interface language.
- More comments: See my other suggestions on how to improve the label list on Wikidata: Show Wikimedias language code and language name in Wikidata label box, Sort label box by language name on Wikidata
- Phabricator tickets:
- Proposer: Sabelöga (talk) 21:23, 23 January 2023 (UTC)
Discussion
Does this also include scripts? Thank you. ShiehJ (talk) 19:17, 15 February 2023 (UTC)
Voting
- Support —2dk (talk) 19:21, 10 February 2023 (UTC)
- Support They all show in English for me despite that not being my interface language so that would be an improvement. عُثمان (talk) 23:32, 10 February 2023 (UTC)
- Support OwenBlacker (Talk) 15:15, 11 February 2023 (UTC)
- Support Mike bzh (talk) 15:45, 11 February 2023 (UTC)
- Support --NGC 54 (talk|contribs) 01:10, 12 February 2023 (UTC)
- Support ProbabilityCollapse (talk) 17:45, 12 February 2023 (UTC)
- Support Libcub (talk) 02:48, 14 February 2023 (UTC)
- Support Ottawajin (talk) 09:26, 15 February 2023 (UTC)
- Support No concerns for the proposal. Thingofme (talk) 16:11, 18 February 2023 (UTC)
- Support unless technically difficult to implement. Concept14 (talk) 21:34, 20 February 2023 (UTC)
- Support cyrfaw (talk) 11:39, 21 February 2023 (UTC)
- Support Computerz4 (talk) 17:50, 22 February 2023 (UTC)
- Support Wargo (talk) 22:38, 23 February 2023 (UTC)
Show Wikimedias language code and language name in Wikidata label box
- Problem: When using LabelLister or similar systems to add labels in new languages or want to find a specific language but don't want to go through 300+ languages, it can be useful to know by which language code the languages are sorted after all.
- Proposed solution: Introduced the ability to print the languages' language code in the label box, preferably before the language name so that editors know what that language's language code is.
- Who would benefit: Editors who contribute in multiple languages
- More comments: See my other suggestions on how to improve the label list on Wikidata: Optional native language label language name, Sort label box by language name on Wikidata
- Phabricator tickets:
- Proposer: Sabelöga (talk) 23:02, 25 January 2023 (UTC)
Discussion
This is how it looks for me now: https://imgur.com/a/TyCp4Va. This is a mockup on how I want it to look: https://imgur.com/a/U7JeJgW.
Voting
- Support NMaia (talk) 23:59, 10 February 2023 (UTC)
- Support Кирилл С1 (talk) 14:37, 11 February 2023 (UTC)
- Support Sovxx (talk) 12:44, 12 February 2023 (UTC)
- Support Gillum (talk) 22:47, 13 February 2023 (UTC)
- Support Libcub (talk) 02:55, 14 February 2023 (UTC)
- Support Yug (talk) 10:30, 17 February 2023 (UTC)
- Support This should be added to the wiki. Thingofme (talk) 16:06, 18 February 2023 (UTC)
- Support Christian (talk) 20:30, 18 February 2023 (UTC)
- Support Mbrickn (talk) 03:13, 20 February 2023 (UTC)
- Support — Draceane talkcontrib. 12:45, 20 February 2023 (UTC)
- Support cyrfaw (talk) 18:42, 20 February 2023 (UTC)
Sort label box by language name on Wikidata
- Problem: The label box is now sorted by Wikimedia's internal language code which usually, but not necessarily, follows ISO 639 codes. This is not shown to the users so the list appears quite arbitrary to those who do not know the logic behind why languages are where they are.
- Proposed solution: Introduced the ability to sort the labels by language name or Wikimedia's internal language code
- Who would benefit: Editors who contribute in multiple languages.
- More comments: Also see my other suggestions for improvements to the label box on Wikidata: Optional native language label language name, Wikimedias språkkod i etikettrutan på Wikidata jämte språknamnet
- Phabricator tickets:
- Proposer: Sabelöga (talk) 20:58, 26 January 2023 (UTC)
Discussion
Voting
- Support Libcub (talk) 03:06, 14 February 2023 (UTC)
- Support Makes sense for usability but low priority compared to others Wd-Ryan (talk) 20:12, 17 February 2023 (UTC)
- Support This make sense for usability. Thingofme (talk) 16:14, 18 February 2023 (UTC)
- Support – ideally it could be changed in user preferences in case editors prefer the current sorting order. –FlyingAce✈hello 01:48, 20 February 2023 (UTC)
- Support cyrfaw (talk) 11:39, 21 February 2023 (UTC)
Adding statements on mobile devices
- Problem: On mobile devices it's only possible to add and edit interwikilinks, labels, descriptions and alias. But it's not possible to edit or add statements.
- Proposed solution:
- Who would benefit: Users, who:
- don't have a PC available at any time
- prefer to use mobile devices
- More comments: This change would make editing Wikidata more accessible, time- and devices-independent. Previously proposed in the 2016 Wishlist Survey.
- Phabricator tickets: T95878
- Proposer: Yuriklim (talk) 10:58, 24 January 2023 (UTC)
Discussion
- @Yuriklim: I fixed typo of the name page. Tryvix1509 (talk) 10:01, 24 January 2023 (UTC)
- I strongly support this proposal. I mainly contribute to Wikidata and Wikipedia with my mobile phone. When editing Wikidata I switch between the web mobile interface (known as Minerva) to write wikitext, labels and interwiki links and the desktop interface (I use Timeless) to add statements. It's quite difficult. I think that something that half of the traffic on the Web comes from people using mobile devices. Those people should have a solution to quickly contribute to Wikidata. PAC2 (talk) 21:42, 24 January 2023 (UTC)
- Strongly support. Would also support a separate Wikidata app, or the option to edit Wikidata in the existing Wikipedia app. CvZ (talk) 02:47, 29 January 2023 (UTC)
- Like this idea. This will be help contributors to quickly add new information as soon as they find relevant information. John Samuel 18:34, 29 January 2023 (UTC)
- This would be a great step forward. Robby (talk) 21:56, 29 January 2023 (UTC)
- Yes. I often navigate by WikiShootMe to find photo targets and it isn't there, so I walk around and find the target, but entering the correct location is not really practical until I get home to the big computer. WD items and their statements are individually small and self contained, so they ought to be easily edited on small screen. ̴̃Jim.henderson (talk) 08:22, 19 February 2023 (UTC)
Voting
- Support As per my comment above. John Samuel 18:45, 10 February 2023 (UTC)
- Support Daieuxetdailleurs (talk) 18:58, 10 February 2023 (UTC)
- Support Strainu (talk) 20:21, 10 February 2023 (UTC)
- Support Joalpe (talk) 21:45, 10 February 2023 (UTC)
- Support Yirba (talk) 22:16, 10 February 2023 (UTC)
- Support PAC2 (talk) 22:26, 10 February 2023 (UTC)
- Support The biggest thing preventing new contributors from joining. عُثمان (talk) 23:33, 10 February 2023 (UTC)
- Strong support --Tinker Bell ★ ♥ 23:52, 10 February 2023 (UTC)
- Support Sabelöga (talk) 23:58, 10 February 2023 (UTC)
- Support NMaia (talk) 00:02, 11 February 2023 (UTC)
- Support ·addshore· talk to me! 00:13, 11 February 2023 (UTC)
- Support - PKM (talk) 00:18, 11 February 2023 (UTC)
- Support Poslovitch (talk) 00:22, 11 February 2023 (UTC)
- Support ··· 🌸 Rachmat04 · ☕ 02:41, 11 February 2023 (UTC)
- Support Tgr (talk) 04:02, 11 February 2023 (UTC)
- Support * Pppery * it has begun 04:03, 11 February 2023 (UTC)
- Support EpicPupper (talk) 05:34, 11 February 2023 (UTC)
- Support Gohan 07:07, 11 February 2023 (UTC)
- Support Janhrach (talk) 07:26, 11 February 2023 (UTC)
- Support Plaga med (talk) 11:19, 11 February 2023 (UTC)
- Support Smetanakaviar (talk) 12:12, 11 February 2023 (UTC)
- Support DerFussi 12:27, 11 February 2023 (UTC)
- Support Nw520 (talk) 12:32, 11 February 2023 (UTC)
- Support Кирилл С1 (talk) 14:35, 11 February 2023 (UTC)
- Support Ayack (talk) 15:11, 11 February 2023 (UTC)
- Support Simeon (talk) 17:38, 11 February 2023 (UTC)
- Support Conny (talk) 18:11, 11 February 2023 (UTC)
- Support Edu! (talk) 21:54, 11 February 2023 (UTC)
- Support --NGC 54 (talk|contribs) 01:12, 12 February 2023 (UTC)
- Support Betseg (talk) 03:43, 12 February 2023 (UTC)
- Support Mauricio V. Genta (talk) 08:02, 12 February 2023 (UTC)
- Support Arnd (talk) 08:44, 12 February 2023 (UTC)
- Support HLFan (talk) 08:51, 12 February 2023 (UTC)
- Support Ameisenigel (talk) 09:12, 12 February 2023 (UTC)
- Support Tryvix t 09:14, 12 February 2023 (UTC)
- Support Wiki-uk (talk) 09:25, 12 February 2023 (UTC)
- Support Mehman 09:40, 12 February 2023 (UTC)
- Support Sovxx (talk) 12:42, 12 February 2023 (UTC)
- Support Will be a pretty big undertaking, but definitely be very good for the community Husky (talk) 21:14, 12 February 2023 (UTC)
- Support Thomas Kinz (talk) 01:04, 13 February 2023 (UTC)
- Support Natalius (talk) 04:43, 13 February 2023 (UTC)
- Support Izno (talk) 08:09, 13 February 2023 (UTC)
- Support I strongly support because mostly when you organize training for new people especially students who don't have laptops or computers, switching to desktop mode is always hectic as they have to continuously zoom in and out just to do stuff. I think if this is enabled, it is going to make our lives easier. Dnshitobu (talk) 09:03, 13 February 2023 (UTC)
- Support Crazy1880 (talk) 18:34, 13 February 2023 (UTC)
- Support Yes!! Please, more mobile support is crucial for increasing Wikidata usage, at least in Brazil TiagoLubiana (talk) 18:46, 13 February 2023 (UTC)
- Support JAn Dudík (talk) 21:50, 13 February 2023 (UTC)
- Support Wargo (talk) 22:53, 13 February 2023 (UTC)
- Support YjM (talk) 23:08, 13 February 2023 (UTC)
- Support Libcub (talk) 02:49, 14 February 2023 (UTC)
- Support Czupirek (talk) 11:27, 14 February 2023 (UTC)
- Support //Lollipoplollipoplollipop::talk 13:38, 14 February 2023 (UTC)
- Support Thibaultmol (talk) 18:06, 14 February 2023 (UTC)
- Support VIGNERON * discut. 19:50, 14 February 2023 (UTC)
- Support Ottawajin (talk) 09:24, 15 February 2023 (UTC)
- Support DFichtmueller (talk) 12:00, 15 February 2023 (UTC)
- Support Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:49, 15 February 2023 (UTC)
- Support —MdsShakil (talk) 18:15, 15 February 2023 (UTC)
- Support WhatamIdoing (talk) 18:29, 15 February 2023 (UTC)
- Support --Polarlys (talk) 21:36, 15 February 2023 (UTC)
- Support আফতাবুজ্জামান (talk) 00:33, 16 February 2023 (UTC)
- Support Sadads (talk) 01:24, 16 February 2023 (UTC)
- Support Vis M (talk) 06:36, 16 February 2023 (UTC)
- Support Aishik Rehman (talk) 08:44, 16 February 2023 (UTC)
- Support ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 17:39, 16 February 2023 (UTC)
- Support Steam Flow (talk) 22:09, 16 February 2023 (UTC)
- Support This would really help users who love to edit Wikidata while commuting or being outdoor. Currently, there is a constant need to switch the interface to desktop view while on mobile (which is still not responsive). Fexpr (talk) 08:41, 17 February 2023 (UTC)
- Support Luzz (talk) 09:06, 17 February 2023 (UTC)
- Support DobryBrat (talk) 10:38, 17 February 2023 (UTC)
- Support Kurmanbek 💬 17:15, 17 February 2023 (UTC)
- Support —CX Zoom (A/अ/অ) (let's talk|contribs) 19:40, 17 February 2023 (UTC)
- Support Would love to edit Wikidata on mobile Wd-Ryan (talk) 20:10, 17 February 2023 (UTC)
- Support Robby (talk) 15:07, 18 February 2023 (UTC)
- Support This should make editing Wikidata more accessible. Thingofme (talk) 16:07, 18 February 2023 (UTC)
- Support Christian (talk) 20:29, 18 February 2023 (UTC)
- Support Albinfo (talk) 22:10, 18 February 2023 (UTC)
- Support WD on mobile could be easy Jim.henderson (talk) 08:22, 19 February 2023 (UTC)
- Support Lupe (talk) 11:23, 19 February 2023 (UTC)
- Support Ambrosia10 (talk) 16:55, 20 February 2023 (UTC)
- Support strongly support Watty62 (talk) 17:45, 20 February 2023 (UTC)
- Support cyrfaw (talk) 18:50, 20 February 2023 (UTC)
- Support AllyD (talk) 08:21, 21 February 2023 (UTC)
- Support Tris T7 (talk) 19:37, 21 February 2023 (UTC)
- Support Very much needed. Serieminou (talk) 23:08, 21 February 2023 (UTC)
- Support Amir E. Aharoni (talk) 12:06, 22 February 2023 (UTC)
- Support Dajasj (talk) 13:55, 22 February 2023 (UTC)
- Support Morten Haan (talk) 18:49, 22 February 2023 (UTC)
Support for non-Gregorian and non-Julian calendar models on Wikidata
- Problem: Wikidata does not support calender models other than Gregorian and Julian, but there are a vast amount of data described in other calender models like Hijri, Hebrew, Bengali etc., which don't get incorporated into Wikidata.
- Proposed solution: Provide a system to include other calender models so that users can input data accordingly.
- Who would benefit: Non-Western communities who have data in these other calender models but have no option to include them in current system.
- More comments:
- Phabricator tickets: T252627
- Proposer: Bodhisattwa (talk) 06:35, 31 January 2023 (UTC)
Discussion
- Good point; already mentioned in Community Wishlist Survey 2021/Wikidata/Time and date handling improvements, which aggregated also other tickets related to the handling of dates in Wikidata. --Epìdosis 20:17, 31 January 2023 (UTC)
- It would help to enter into Wikidata event of dates that are known in local calendar but the calendar's conversion to Gregorian calendar remain uncertain. C933103 (talk) 05:46, 7 February 2023 (UTC)
Voting
- Support Onthewings (talk) 21:22, 10 February 2023 (UTC)
- Support NMaia (talk) 00:04, 11 February 2023 (UTC)
- Support --Tinker Bell ★ ♥ 00:08, 11 February 2023 (UTC)
- Support HHill (talk) 08:29, 11 February 2023 (UTC)
- Support --Epìdosis 08:41, 11 February 2023 (UTC)
- Support It is a good suggestion. Akbarali (talk) 08:58, 11 February 2023 (UTC)
- Support OwenBlacker (Talk) 15:14, 11 February 2023 (UTC)
- Support CROIX (talk) 15:19, 11 February 2023 (UTC)
- Support JrawX (talk) 15:44, 11 February 2023 (UTC)
- Support Wotheina (talk) 16:01, 11 February 2023 (UTC)
- Support Mbkv717 (talk) 16:50, 11 February 2023 (UTC)
- Support Mahir256 (talk) 18:09, 11 February 2023 (UTC)
- Support It is a very good suggestion Von Uebigau (talk) 19:01, 11 February 2023 (UTC)
- Support Erfil (talk) 19:16, 11 February 2023 (UTC)
- Support Abzeronow (talk) 19:19, 11 February 2023 (UTC)
- Support Just to be clear, it's a problem of Non-Western communities. The problem exists also with Western calendars: for example Pisa and Florence started their years both on March, 25th but with a precise gap of one unit. We need more flexible entries, and if we had worked with these issues properly in the past, adapting to other systems would have been much faster. --Alexmar983 (talk) 21:09, 11 February 2023 (UTC)
- Support --NGC 54 (talk|contribs) 01:09, 12 February 2023 (UTC)
- Support Ahkei (talk) 01:49, 12 February 2023 (UTC)
- Support Marine 69-71 (talk) 04:03, 12 February 2023 (UTC)
- Support बडा काजी (talk) 23:42, 12 February 2023 (UTC)
- Support Izno (talk) 08:10, 13 February 2023 (UTC)
- Support Elena moz (talk) 12:40, 13 February 2023 (UTC)
- Support Gillum (talk) 17:53, 13 February 2023 (UTC)
- Support Libcub (talk) 03:05, 14 February 2023 (UTC)
- Support Ottawajin (talk) 09:27, 15 February 2023 (UTC)
- Support ShiehJ (talk) 19:15, 15 February 2023 (UTC)
- Support Aishik Rehman (talk) 08:47, 16 February 2023 (UTC)
- Support ··· 🌸 Rachmat04 · ☕ 12:13, 16 February 2023 (UTC)
- Support DFlhb (talk) 19:31, 16 February 2023 (UTC)
- Support ~ Amory (u • t • c) 16:40, 17 February 2023 (UTC)
- Support DoublePendulumAttractor (talk) 05:59, 18 February 2023 (UTC)
- Support Fabius Lector (talk) 10:38, 18 February 2023 (UTC)
- Support Herbert Ortner (talk) 14:30, 18 February 2023 (UTC)
- Support Vulcan❯❯❯Sphere! 16:15, 18 February 2023 (UTC)
- Support It should be added to the calendar. Thingofme (talk) 16:22, 18 February 2023 (UTC)
- Support -- Ferien (talk) 16:24, 18 February 2023 (UTC)
- Support Mbrickn (talk) 03:12, 20 February 2023 (UTC)
- Support β16 - (talk) 10:39, 20 February 2023 (UTC)
- Support Ambrosia10 (talk) 16:58, 20 February 2023 (UTC)
- Support Nashona (talk) 18:17, 20 February 2023 (UTC)
- Support cyrfaw (talk) 18:56, 20 February 2023 (UTC)
- Support Darellur (talk) 21:44, 20 February 2023 (UTC)
- Support +s MartinPoulter (talk) 13:34, 21 February 2023 (UTC)
- Support Computerz4 (talk) 17:49, 22 February 2023 (UTC)
- Support Morten Haan (talk) 18:48, 22 February 2023 (UTC)
- Support ~~~~
User:1234qwer1234qwer4 (talk) 17:56, 24 February 2023 (UTC)
Clickable map for coordinate locations
- Problem: When creating new item user must copy values for coordinate location (P625) from other websites - geolocator, OSM, Google, mapy.cz, etc.
- Proposed solution: Provide map (with visible details like mapnik, mapy.cz, not googlish wmf maps) for selecting correct place and copy coordinates with click to P625.
- Who would benefit: Editors, readers
- More comments:
- Phabricator tickets: phab:T329852
- Proposer: JAn Dudík (talk) 14:20, 6 February 2023 (UTC)
Discussion
- Until something like this has been implemented, you might consider using the tool Wikishootme: make there a new Wikidata item, then go to Wikidata, search for the new item (might take one or two minutes), which has now the geocoordinates of the place you clicked on, and then add supplementing data. --JopkeB (talk) 12:53, 11 February 2023 (UTC)
- Wikishootme is fine, but even if I have selected Czech as my language, new items have always English label. And unfortunatelly there is WMF map only. JAn Dudík (talk) 21:52, 13 February 2023 (UTC)
- Albeit I would also like this feature, I believe you understand shortcomings and side-effects this can bring. E.g. users changing P625 values (moving features) because they appear slightly off on the map, while the original value was more precise than the map.
Voting
- Support Strainu (talk) 20:22, 10 February 2023 (UTC)
- Support Rtfroot (talk) 20:53, 10 February 2023 (UTC)
- Support Onthewings (talk) 21:20, 10 February 2023 (UTC)
- Support Pi.1415926535 (talk) 21:58, 10 February 2023 (UTC)
- Support MHM (talk) 22:02, 10 February 2023 (UTC)
- Support Graham11 (talk) 23:48, 10 February 2023 (UTC)
- Support --Tinker Bell ★ ♥ 23:55, 10 February 2023 (UTC)
- Support NMaia (talk) 00:03, 11 February 2023 (UTC)
- Support ·addshore· talk to me! 00:13, 11 February 2023 (UTC)
- Support Poslovitch (talk) 00:23, 11 February 2023 (UTC)
- Support ··· 🌸 Rachmat04 · ☕ 02:43, 11 February 2023 (UTC)
- Support Goliv04053 (talk) 06:39, 11 February 2023 (UTC)
- Support A333 (talk) 07:53, 11 February 2023 (UTC)
- Support Martin-78 (discutailler) 08:35, 11 February 2023 (UTC)
- Support Exilexi (talk) 09:15, 11 February 2023 (UTC)
- Support Envlh (talk) 09:17, 11 February 2023 (UTC)
- Support Oltrepier (talk) 10:08, 11 February 2023 (UTC)
- Support Ecritures (talk) 11:10, 11 February 2023 (UTC)
- Support Plaga med (talk) 11:21, 11 February 2023 (UTC)
- Support DerFussi 12:28, 11 February 2023 (UTC)
- Support Nw520 (talk) 12:33, 11 February 2023 (UTC)
- Support --Crosstor (talk) 13:48, 11 February 2023 (UTC)
- Support RVA2869 (talk) 14:55, 11 February 2023 (UTC)
- Support Ayack (talk) 15:12, 11 February 2023 (UTC)
- Support Bluerasberry (talk) 15:13, 11 February 2023 (UTC)
- Support CROIX (talk) 15:18, 11 February 2023 (UTC)