Overleg gebruiker:Mbch331

Welkom op mijn overlegpagina. Gelieve nieuwe vragen, zoals gebruikelijk hier op Wikipedia, onderaan de pagina onder een eigen kopje te plaatsen. Vragen hier gesteld zullen ook uitsluitend hier beantwoord worden. Gelieve uw boodschap op deze pagina ook te ondertekenen met vier tildes (~~~~) zodat ik weet wie hier heeft geschreven. In het geval het over een specifiek artikel gaat, gelieve een link naar dat artikel te verschaffen. Zie voor ouder overleg mijn Archief

Wikidata weekly summary #709

Here's your quick overview of what has been happening around Wikidata in the
week leading up to 2025-12-08. Missed the previous one? See issue #708.

Discussions

• New requests for permissions/Bot:
  • Well, Well, Bot! - Task/s: Database imports, maintenance.
  • RijksBot - Task/s: Adding Rijksmuseum IDs (P13234) to Wikidata items based on a CSV mapping of QIDs to Rijksmuseum URIs.
  • CostamiriBot - Task/s: Chess related tasks such as monthly updates to the elo rating of chess players.
• New draft: Wikidata:External identifiers/Obsolescence (opinions are welcome in its talk page)

Events

• Upcoming events:
  • How to view #25N with Wikidata? - a community hour with Wikimedia Chile, 21:00 UTC+1 (Time zone converter)
  • Fact-Checking with Wikidata Workshop - January 20, 2026, 16:30 ~ 18:00 UTC+1 (Time zone converter) - WMDE's Philippe Saadé will show hands-on methods using the Wikidata MCP to retrieve, filter and classify Wikidata statements with semantic search, reranker LLM and NLI models, registration required.
  • (Portuguese) Meeting Point Editatona II - Warm your hands modeling festival on Wikidata: December 10, 2025, 15:00 - 19:00 UTC+1, Porto, Portugal.
  • Next Linked Data for Libraries LD4 Wikidata Affinity Group session 9 December, 2025: We have our next LD4 Wikidata Affinity Group Session on Tuesday, 9 December, 2025 at 9am PT/ 12pm ET/ 17:00 UTC / 6pm CET (Time zone converter). WikiProject Personal Pronouns members will lead three implementation sessions to improve the data modeling and ethics of personal pronoun representation in Wikidata based on newly-established best practices and Wikidata policy by remediating legacy statements with participants. No previous Wikidata experience is needed to participate. Sessions will be held on October 14, November 25, and December 9, 2025 at our regular time of 9am PT/ 12pm ET/ 17:00 UTC / 6pm CET. Event page: https://www.wikidata.org/wiki/Wikidata:WikiProject_LD4_Wikidata_Affinity_Group/Project_Series/PersonalPronouns
• Past Events: Digital Humanities Hub: Documenting epigraphic data, Wikidata ontology practice - December 2 & 3, 2025, both 14:00 ~ 15:30 UTC.

Press, articles, blog posts, videos

• Blogs: Wikidata 13th Birthday Celebration in Lafia
• Papers:
  • Wikontic: Constructing Wikidata-Aligned, Ontology-Aware Knowledge Graphs with Large Language Models - Chepurova et al., (2025)
  • Victims of Posterity. Identifying Gaps on 19th-Century French Art History with Wikidata - first paper in the Wikidata Across the Humanities: Datasets, Methodologies, Reuse collection by the Journal of Open Humanities Data. Authored by Claire Dupin de Beyssat.
• Videos: GB Claude Code AI Agent: Fully Autonomous Wikidata Query & Visualization (Zero Human Intervention)
  • (Taiwanese Mandarin) Wikidata Taiwan translation project on "Creating Library Linked Data with Wikibase: Lessons Learned from Project Passage" (as published by the OCLC)

Tool of the week

• Wikiguessr Game Is a Wikidata game it guess the location from Image from anywhere around the world by User: Ranjithsiji

Other Noteworthy Stuff

• Remembering Amos Bairoch, co-contributor to Swiss Institute of Bioinformatics Semantic Web of data and consulted often for TiagoLubiana's CellosaurusBot.

Newest properties and property proposals to review

• Newest General datatypes:
  • ‎GBFS feed URL (URL of a GBFS feed for the bicycle-sharing system)
  • code of conduct URL (URL of a resource that contains the Code of Conduct of a project or organization)
• Newest External identifiers: BFXC authority ID, Out tag ID, GayCities ID, Fight.ru fighters ID, Personality Database group ID, ‎Codes for the administrative divisions of the People's Republic of China, Macanese company ID, ‎MovieID film ID, Teen Vogue tag ID, ‎CRT Database model ID, PriceRunner product ID, BWB number, Brandenburg School ID
• New General datatypes property proposals to review:
  • fragrance gender (category for which a fragrance is marketed)
  • perfumer (person who created a perfume)
  • Discharge regime (The '''[[:en:Discharge regime|discharge regime]]''' can be Glacial, Nival or Pluvial. It can be a combination of 2 : Nivo-pluvial, Pluvio-nival, Nivo-glacial, etc. Be specific (e.g. pluvial tropical, meridional, etc.). Or be complex)
  • minimal pair of (lexeme that differ from this one in only one phonological element)
• New External identifier property proposals to review: Cookpad Recipe ID, Sector.sk game ID, Card Player ID, Fragrantica perfume ID, Fragrantica perfume brand ID, My Abandonware theme ID, Identificador Banrep Cultural, izoh.uz word ID, VGChartz game ID, Metacritic video game genre ID, Place Names and Places of Nova Scotia ID, Taking Stock ID, Game Font Library ID, Fragrantica perfume notes ID, EAGER game ID

You can comment on all open property proposals!

Did you know?

• Query examples:
  • Birthplace of French Heads of State
  • Films starring Cary Grant, directed by Howard Hughes, available on YouTube
• WikiProject Highlights: WikiProject Turkmenistan
• Showcase Items: Goosebumps - 2015 film directed by Rob Letterman
• Showcase Lexemes: course (L3958) - English noun (kɔːrs) meaning "direction of movement", "program of study", or "part of a meal"

Development

• Mobile statement editing:
  • It's now possible to edit existing references (phab:T405236)
  • We fixed a number of issues such as a problem when adding the first statements to an item (phab:T409069)
  • We started work on showing constraint violation indicators (phab:T400676)
  • We're working on showing errors in the edit form (phab:T408928)
  • We're improving the edit summaries (phab:T411247)
• Wikidata integration in the Wikimedia projects: We continued working on improvements to the Databox Lua module and template
• GraphQL: We continued working on the first version of GraphQL support

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Weekly Tasks

• Add labels, in your own language(s), for the new properties listed above.
• Contribute to the showcase Item and Lexeme above.
• Govdirectory weekly focus country: Togo
• Summarize your WikiProject's ongoing activities in one or two sentences.
• Help translate or proofread the interface and documentation pages, in your own language!
• Help merge identical items across Wikimedia projects.
• Help write the next summary!

· Previous issue · Full report · Unsubscribe . JosefAnthony talk ·MediaWiki message delivery (overleg) 8 dec 2025 16:41 (CET)

Tech News: 2025-50

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Anybody who wishes to secure their user account can now use two-factor authentication (2FA). This is available to all registered users of all Wikimedia projects. This is part of the Account Security initiative. Later, 2FA will be required for all users who can take security- or privacy-sensitive actions.

Updates for editors

• Following last week's deployments, the Add a link feature, which allows editors to add suggested links during editing, will be available to an additional 33 Wikipedias starting on 9 December. This expansion is possible thanks to the new prediction model that now supports all languages, including those that were previously not covered. While the feature has been available on most Wikipedias for some time, this rollout brings us closer to using the improved model everywhere. If you have any questions or would like more details please contact Trizek (WMF).
• Last week, the Search Platform team added transliterated as-you-type search suggestions to Georgian wikis. If there are only a few regular search suggestions, then queries in Latin or Cyrillic script are now rewritten into Georgian script to look for more matches. For example, searching for either bedniereba or бедниереба will now suggest the existing article about ბედნიერება ("happiness"). You can recommend other languages where transliterated suggestions would be useful on Phabricator for future development.
• Later this week, a controlled experiment will begin for editors on the 100 largest Wikipedias who are editing a section in the mobile web visual editor. 50% of these editors will notice a new "Edit full page" button that will enable them to expand their editing session to the whole page. This feature is intended to make it easier for people on mobile web to edit any article section, regardless of which section-edit icon they tapped to begin. The experiment will last ~4 weeks. You can find more details about the project.
• Later this week, the Reader Growth team will launch a mobile web experiment to expand all article sections by default (currently they are collapsed by default) and pin the section header the user is currently reading to the top of the page. The experiment will affect 10% of users on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias. [1]
• The Wikipedia Year in Review 2025, a feature in the Wikipedia mobile apps (iOS and Android) that provides users with a personalised summary of their engagement with Wikipedia over the year, is now available on the iOS and Android apps. This edition includes expanded personalised insights, improved reading highlights, new donor messaging, and updated designs. Open the app to view your Year in Review and explore your reading journey from 2025.
• A recent software bug caused edits made with VisualEditor to make unintended changes to wikitext, including removing whitespace and replacing spaces with underscores in wikilinks inside citations. This was partially fixed last week, and further fixes are in progress. Editors who used VisualEditor between November 28 and December 2 should review their edits for unexpected modifications. [2]
• View all 23 community-submitted tasks that were resolved last week. For example, the incorrect handling of URLs copied from the address bar of Microsoft Edge users, has been resolved. [3]

Updates for technical contributors

• Starting this week, users of the "Verbeterde syntaxiskleuring" beta feature will have CodeMirror as the editor for Lua, JavaScript, CSS, JSON and Vue content models, instead of CodeEditor. With this, the linters will be upgraded. This is part of a larger effort to eventually replace CodeEditor and provide a consistent code editing experience. [4]
• Developers are encouraged to take the 2025 Developer Satisfaction Survey, which remains open until 5 January 2026. If you build software for the Wikimedia ecosystem and would like to share your experiences or feedback, your participation is greatly appreciated. [5]
• There is no new MediaWiki version this week.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 8 dec 2025 18:44 (CET)

Taalcodering bronnen

Hoi Mbch331, ik zie je wel vaker correcties uitvoeren in de taalcodering van bronnen, zoals hier. Ik gebruik de visuele editor voor het toevoegen van bronnen en die doet iets met de taalcodes, kennelijk. Is het niet beter om die VE aan te pakken dan al die handmatige correcties uit te voeren? Groet, Elly _{Sta jij al hier? (Overleg)} 9 dec 2025 20:57 (CET)

VE neemt de taalcodes over die de websites zelf ingesteld hebben. Voor codes als nl-NL (of en-US / en-GB) heb ik al heel lang geleden een oplossing bedacht in de code van de sjablonen. Die geven geen problemen, maar is meer bijvangst. Het grote probleem is de taal=nederlands. Wil je die ook kunnen gaan ondervangen, dan lukt dat niet meer met gewone sjablooncode. Ik weet dat ze op enwiki wel een oplossing hebben, maar dat is met een module voor de citeer sjablonen. Dat hier implementeren betekend alle citeer sjablonen herschrijven. En daar ga ik niet aan beginnen. Mbch331 (overleg) 9 dec 2025 21:06 (CET)

Trouwens ik vind het niet erg die zaken te fixen. De een is beter in schrijven en de ander beter in onderhoud. Mbch331 (overleg) 9 dec 2025 21:07 (CET)

Als jij het niet erg vindt, is er geen probleem. Jammer dat er in html geen standaardisatie is.... of dat men zich er weinig van aantrekt. Keep up the good work then! Groet, Elly _{Sta jij al hier? (Overleg)} 9 dec 2025 22:03 (CET)

Ja, altijd grappig om in de visuele editor te zien staan "De tweeletterige ISO 639-1-code van de taal waarin de webpagina is geschreven", terwijl er dan automatisch "nl-NL" is geplaatst. Dan haal ik "-NL" dus weg... Best veel werk, fijn dat jij dat doet, Mbch331, en ook bedankt dat je vaak de 'duplicates' bij mijn bewerkingen eruit haalt, bijvoorbeeld als er na mijn bewerking twee keer 'taal' in het referentiesjabloon staat...! Laurier (xij/die) (overleg) 10 dec 2025 09:58 (CET)

De opmerking staat er voor mensen die het sjabloon met de hand invullen. Wij hebben geen invloed op de cite tool die VE gebruikt. En een algemene tool passen ze niet aan, aan de wensen van 1 community. Mbch331 (overleg) 10 dec 2025 10:11 (CET)

Ja, snap ik, maar toch ziet het er grappig uit. Laurier (xij/die) (overleg) 10 dec 2025 12:35 (CET)

Waarom moet het per se een tweeletterige code zijn, of drieletterig zoals nds? Ikzelf vind het wel handig om te weten als een bron in het Amerikaans Engels (en-US) is geschreven, dan zoek ik in een lange pdf niet naar harbour maar naar harbor en dan weet ik welke sport er bedoeld wordt met football en of iemand op een college een universitaire studie volgt of juist niet; hier meer voorbeelden. Daarom laat ik zulke toevoegingen staan en voeg ik ze soms zelfs handmatig toe. Moet ik daarmee stoppen?  →bertux 10 dec 2025 16:05 (CET)

De parameter taal is bedoeld om de taalsjablonen vooraan de referentie weer te geven. Er wordt niet vooraan en-US getoond, alleen (en) . De -US wordt eraf gestript in de sjablonen, zodat het juiste taalsjabloon wordt getoond. In het verre verleden werd -US er niet afgestript en kreeg je in die gevallen ook geen (en) te zien. We hebben nog nooit gewerkt met taalvarianten in de citeer sjablonen. Mbch331 (overleg) 10 dec 2025 16:13 (CET)