User talk:Mike Peel/Archive 67

Wikidata weekly summary #486
Here's your quick overview of what has been happening around Wikidata over the last week. 


 * Events
 * Upcoming:
 * Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Bionomia and maintaining Wikidata synchrony with David Shorthouse (Agriculture and Agri-Food Canada)., Sep 21st.
 * Lightning Talk: Wikidata in your Civic Tech project | Summit 2021 - YouTube
 * Ongoing:
 * The Creative Commons Global Summit and Hack4OpenGLAM hackathon take place from September 20 until 24 (fully online). Several sessions and projects are related to Wikidata and/or Wikibase (see schedule search).
 * Past:
 * Data Quality Days:
 * Periodic editathons as a way to improve data quality on Wikidata: an experiment in Italy - YouTube
 * Bringing Czech authority files into 21st century: Integration with Wikidata - YouTube


 * Press, articles, blog posts, videos
 * Videos
 * Mapping the Scottish Reformation - using Wikidata, Wikipedia's sister project - YouTube
 * OpenSym 2021: WDProp: Web Application to Analyse Multilingual Aspects of Wikidata Properties - YouTube
 * Wikipedia Weekly Network - LIVE Wikidata editing #53 (user scripts and gadgets that can help you edit) - YouTube


 * Tool of the week
 * User:Inductiveload/scripts/ShowQsAndPs shows the Q and P IDs on Items.


 * Other Noteworthy Stuff
 * OpenRefine has started development of features for Structured Data on Wikimedia Commons. Sign up here if you want to receive occasional updates on a Wikimedia talk page of your choice.


 * Did you know?


 * Newest properties:
 * General datatypes: created for, Candomblé nation, NZTCS conservation status, Mexican video game rating category
 * External identifiers: INAPP author ID, TBDB ID, Enciclopedia dello Sport ID, INAPP work ID, Fondation du patrimoine ID, Endemia.nc animal taxon ID, Gry-Online game ID, Encyclopaedia of Islam (first edition) ID, Encyclopaedia of Islam (third edition) ID, Festivaletteratura person ID, Every Noise at Once ID, Spotify show episode ID, Online Begraafplaatsen cemetery ID, Bing entity ID, TermCymru ID, NZTCS ID, Online Begraafplaatsen person ID, UK Renewable Energy Planning Database ID, ICCD ID - Santuari Cristiani, Naver Post member ID, Swedish Food Agency food ID, Dictionary of Old Norse Prose ID


 * New property proposals to review:
 * General datatypes: relevant date for copyright, issuing agency, Hardy's Guide to Marine Gastropods ID, main subject for, type host taxon, has thematic relation, location of lexeme usage, ODOT county code, illustrative content
 * External identifiers: e-Maapõu locality ID, Grand dictionnaire terminologique ID, Google Fonts ID, Kallías, Owler company ID, Vietherb species ID, Vietherb metabolite ID, Allrugby, SLSP editions ID, Issuu ID, XXI Secolo ID, Journées européennes du patrimoine ID, Peoples.ru ID, musik-sammler.de artist ID, HJP ID, NVE reservoir ID, Biografija.ru ID, Madrean Discovery Expeditions Flora Database ID, Madrean Discovery Expeditions Fauna Database ID, IRIS Tuscany IDs, Joshua Project people group ID, Flipboard ID, Washington Rare Plant Field Guide (2021- Version) ID, Gente di Tuscia ID, Poetsgate poem ID, AdoroCinema person ID, Zenodo Communities ID, National Union Catalog ID


 * Query examples:
 * Biological taxa named after (metal (and other) music bands
 * Works by Dante Alighieri (1265 - September 13/14, 1321)
 * Cumulative page views for candidates in Czech parliamentary election 2021, split by party (Source)


 * Development
 * The new Streaming Updater for Wikidata Query Service will be in production 18 Oct 2021
 * Working on changing the way sitelinks to Wikimedia Commons are created from Item data; now using topic's main category (P910) and category related to list (P1754) before Commons category (P373) (T232927)
 * Continuing the work on the Mismatch Finder. This week we focused on the remaining groundwork for showing the first mismatches for review.
 * Continuing to work on improvements to the underlying system of how edits are propagated from Wikidata to the other Wikimedia projects.
 * Implemented two improvements for constraints: the “distinct values” constraint type now supports the “separator” parameter (T277855) and we no longer check qualifiers on some unusual™ properties (T235292)
 * Adding tags to some of the remaining UI edits that didn't get them yet for edits on Lexemes (T290950)
 * Making it possible to add tags to some remaining Lexeme API modules (T290951)
 * Fixed a bug in the Query Builder where it didn't show labels when opening an existing visual query from a shared link (T280684)
 * Made the Query Builder more visible in the Query Service UI (T280229)

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.


 * Monthly Tasks
 * Add labels, in your own language(s), for the new properties listed above.
 * Comment on property proposals: all open proposals
 * Contribute to a Showcase item.
 * 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!

Read the full report · Unsubscribe · Mohammed Sadat (WMDE) 15:14, 20 September 2021 (UTC)

The Signpost: 26 September 2021
 * Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 20:57, 26 September 2021 (UTC)

Wikidata weekly summary #487
Here's your quick overview of what has been happening around Wikidata over the last week. 


 * Discussions
 * Open request for adminship: BrokenSegue (RfP scheduled to end after 27 September 2021 14:36 UTC)


 * Events
 * Upcoming:
 * We’re celebrating the 9th birthday of Wikidata on October 29 during the WikidataCon 🎂 Did you know that you can participate in the celebration by preparing a birthday present or attending events? Here’s how you can get involved!
 * The next Wikibase live session is 16:00 GMT on Thursday 30th September 2021 (18:00 Berlin time). All are welcome!
 * LIVE Wikidata editing #55 (with OpenRefine) - YouTube, Facebook, October 2 at 18:00 UTC
 * Online Wikidata meetup in Swedish #81, October 3
 * COVIWD: COVID-19 Wikidata Dashboard, 30 Sep 2021, Time: 13.00-14.00 WIB (join details)
 * Past:
 * Data Quality Days: You can find slides, videos and notes for many of the sessions on the event page.
 * Wiki Movimento Brasil. The universe of libraries:
 * Wikidata and the multiplication of knowledge potencies (in Portuguese)
 * Wikidata and the multiplication of knowledge powers (in Portuguese)
 * LIVE Wikidata editing #54 - YouTube, Facebook


 * Press, articles, blog posts, videos
 * Blogs
 * Connecting Cell Ontology and Wikidata via Mix’n’match
 * Papers
 * WDProp: Web Application to Analyse Multilingual Aspects of Wikidata Properties, OpenSym 2021, 15-17 September 2021 (Slides, source code, Short Video)
 * Videos
 * How to work with Wikidata in the library (in Italian) - YouTube
 * Demo: create Wikidata lexemes from Goethe's "Der Versuch die Metamorphose der Pflanzen zu erklären" - YouTube
 * Demo of adding a string to Wikidata as a lexeme and linking it to the corresponding Wikidata item - YouTube
 * Wikidata Query Service assistance (in French) - YouTube
 * Experiences of Using WDumper to Create Topical Subsets from Wikidata - YouTube
 * Other
 * Chirpanalytica: "Give me your Twitter name and I'll tell you which party you choose". "What if you could automatically determine the political orientation of a person using just a Twitter account? This is exactly what I have been doing for the past two years".
 * That Wikidata Buzz - Siobhan Leachman talks about Wikidata in the The World According to Wikipedia podcast.
 * That Wikidata Buzz - Siobhan Leachman talks about Wikidata in the The World According to Wikipedia podcast.


 * Tool of the week
 * User-level gender statistics for Wikipedia an Observable notebook which computes the share of articles created on fr.wikipedia.org by gender using P21 property through Wikidata's API.


 * Other Noteworthy Stuff
 * You can nominate your favorite Wikidata projects (tools, community initiatives, WikiProjects...) until October 10th for the WikidataCon community awards.


 * Did you know?


 * Newest properties:
 * General datatypes: App Store age rating, music created for, issuing agent of work, FLOSS development policy URL, relevant date for copyright, inscription image, Hardy's Guide to Marine Gastropods URL
 * External identifiers: Australian Research Council Grant ID, Grand dictionnaire terminologique ID, Materials Project material ID, All.Rugby player ID, swisscovery edition ID, e-Maapõu locality ID, Online Begraafplaatsen memorial ID, PoetsGate poem ID, NVE reservoir ID, FLORE author ID, USiena air author ID, IRIS IMT author ID


 * New property proposals to review:
 * General datatypes: WikiProject importance scale rating, predicate for, eHive ID
 * External identifiers: Database of Czech amateur theater ID, National Gallery Prague work ID, George Eastman Museum artist ID, All.Rugby club ID, Sachsens-Schlösser-Kennung, Dizionario di Economia e Finanza ID, Densho Encyclopedia ID, AsianWiki ID, Channel One Russia show ID, DWDS lemma ID, WDG lemma ID, company code (RICS)


 * Query examples:
 * Given name "Filaret" ranked within similar names (source: talk page of item)
 * Start time of open access journals known to Wikidata (Source)
 * Mouths of rivers flowing into the Arctic (Source)
 * What chocolate mousse is called in different languages (Source)
 * Women in Wikidata whose husbands are economists with articles on the English Wikipedia, but they themselves lack articles (adapted from Source)
 * Same with husbands (adapted from Source)
 * People employed by the ZDF with an image on Commons and a link to the German language Wikipedia (Source)
 * Coordinates of the birth places of people named Antoine (Source)
 * Place of birth of people named Antoine, Tony, Antonio, etc
 * UK MPs who had the most identified descendants who were themselves MPs (Source)
 * Newest database reports: top missing properties by number of sitelinks/P26 (works again)


 * Development
 * Changed the formatting of low year numbers so that they now show as e.g. “5 CE” instead of “5” to reduce ambiugity in dates like “March 5 (CE)” (T104750)
 * Working on fixing an issue where two Properties could have the same label in a given language (T289473)
 * Working on preventing a few more cases where two Items could have the same sitelink (T291377)
 * Mismatch Finder: Continuing to work on showing mismatches on the results page so that they can be reviewed
 * Continuing to work on technical improvements to how changes on Wikidata are propagated to Wikipedia and the other Wikimedia projects

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.


 * Monthly Tasks
 * Add labels, in your own language(s), for the new properties listed above.
 * Comment on property proposals: all open proposals
 * Contribute to a Showcase item.
 * 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!

Read the full report · Unsubscribe · Mohammed Sadat (WMDE) 13:45, 27 September 2021 (UTC)

Administrators' newsletter – October 2021
News and updates for administrators from the past month (September 2021).

Administrator changes
 * Gnome-colors-list-add.svg Blablubbs
 * Gnome-colors-list-remove.svg Alvestrand • Black Falcon • Deathphoenix • Dppowell • Mark Arsten • JGHowes (deceased)



Oversighter changes
 * Gnome-colors-view-refresh.svg Callanecc
 * Gnome-colors-list-remove.svg Mkdw

Interface administrator changes
 * Gnome-colors-list-remove.svg Galobtter

Guideline and policy news
 * Following an RfC, extended confirmed protection may be used preemptively on certain high-risk templates.
 * Following a discussion at the Village Pump, there is consensus to treat discord logs the same as IRC logs. This means that discord logs will be oversighted if posted onwiki.

Technical news
 * DiscussionTools has superseded Enterprisey's reply-link script. Editors may switch using the "Discussion tools" checkbox under.

Arbitration
 * A motion has standardised the 500/30 (extended confirmed) restrictions placed by the Arbitration Committee. The standardised restriction is now listed in the Arbitration Committee's procedures.
 * Following the closure of the Iranian politics case, standard discretionary sanctions are authorized for all edits about, and all pages related to, post-1978 Iranian politics, broadly construed.
 * The Arbitration Committee encourages uninvolved administrators to use the discretionary sanctions procedure in topic areas where it is authorised to facilitate consensus in RfCs. This includes, but is not limited to, enforcing sectioned comments, word/diff limits and moratoriums on a particular topic from being brought in an RfC for up to a year.

Miscellaneous
 * Editors have approved expanding the trial of Growth Features from 2% of new accounts to 25%, and the share of newcomers getting mentorship from 2% to 5%. Experienced editors are invited to add themselves to the mentor list.
 * The community consultation phase of the 2021 CheckUser and Oversight appointments process is open for editors to provide comments and ask questions to candidates.

Discuss this newsletter

Subscribe

Archive Sent by MediaWiki message delivery (talk) 17:04, 1 October 2021 (UTC)

Wikidata weekly summary #488
Here's your quick overview of what has been happening around Wikidata over the last week. 
 * Discussions
 * Closed request for adminship: BrokenSegue. Welcome onboard \o/


 * Events
 * Upcoming
 * OSM TW x Wikidata Taiwan Taipei (Q1867) Meetup 2021-10-04, Mozilla Community Space Taipei (Q61752245)
 * Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Stephanie Sapienza and Emily Frazier on Unlocking the airwaves, a digital archive project that compiles early educational public radio content from the National Association of Educational Broadcasters (NAEB). Agenda with call link, October 5.
 * SPARQL queries live on Twitch in French, by Vigneron, October 5 at 18:00 CEST
 * Ongoing:
 * New Wikidata Lexemes Challenge! Help to improve lexicographical data on Wikidata. This week's theme: Seasons.
 * Past
 * Wikibase Live session logs (September 2021)
 * LD4 - video presentation start 05:00 Keepin 'N Sync... with wikidata ... and ORCID...and GBIF - slides by David Shorthouse
 * The Magnus list that was mentioned at 27:00 (please update list)
 * Ticket created related to problem mentioned with WD objects getting deleted - T291659
 * 2021-09-30, Talk "COVIWD: COVID-19 Wikidata Dashboard" at Seminar Pekanan IR-NLP &mdash; slides in English, video in Indonesian (source)


 * Press, articles, blog posts, videos
 * Blogs
 * What can querying Wikidata do for me?
 * https://diff.wikimedia.org/2021/10/01/synchronising-wikidata-and-wikipedia-an-outreachy-project/
 * Papers: Representing COVID-19 information in collaborative knowledge graphs: The case of Wikidata
 * Videos
 * Introduction to Wikidata for beginners Part. 1 (in Portuguese) - YouTube
 * How to work with Wikidata in the library (in Italian) - YouTube
 * How to work with Wikidata in the library (in Italian) - YouTube


 * Tool of the week
 * ItemSubjector is Python console tool that helps add main subject (P921) to groups of items in a semi-automatic way.


 * Other Noteworthy Stuff
 * You can nominate your favorite Wikidata projects (tools, community initiatives, WikiProjects...) until October 10th for the WikidataCon Community Awards
 * You can also sign up for a slot at the birthday presents lightning talks session at WikidataCon 2021 to present your gift for Wikidata birthday until October 16
 * Submissions for day 2 and 3 of WikidataCon are still open. You can submit sessions about a variety of topics until October 20


 * Did you know?


 * Newest properties:
 * General datatypes: App Store age rating, music created for, issuing agent of work, FLOSS development policy URL, relevant date for copyright, inscription image, Hardy's Guide to Marine Gastropods URL, number of evacuated, template populates category, number of tries marked, madhhab
 * External identifiers: Australian Research Council Grant ID, Grand dictionnaire terminologique ID, Materials Project material ID, All.Rugby player ID, swisscovery edition ID, e-Maapõu locality ID, Online Begraafplaatsen memorial ID, PoetsGate poem ID, NVE reservoir ID, FLORE author ID, USiena air author ID, IRIS IMT author ID, Journées européennes du patrimoine ID, Peoples.ru person ID, Kallías ID, Convict Records of Australia ID, Croatian Language Portal identifier, Issuu ID, Flipboard ID, Umění pro město ID, BBC Food ID, Baijiahao ID, Inventory of Heritage Artefacts institution ID, Inventory of Heritage Artefacts object ID, Vietherb species ID, Vietherb metabolite ID, Zenodo communities ID, XXI Secolo ID, Indonesian Museum National Registration System ID, Postimees topic ID


 * New property proposals to review:
 * General datatypes: WikiProject importance scale rating, predicate for, eHive ID, original description, Bowers acronym, mul label property, stylized name
 * External identifiers: Database of Czech amateur theater ID, National Gallery Prague work ID, George Eastman Museum artist ID, All.Rugby club ID, Sachsens-Schlösser-Kennung, Dizionario di Economia e Finanza ID, Densho Encyclopedia ID, AsianWiki ID, Channel One Russia show ID, DWDS lemma ID, WDG lemma ID, company code (RICS), IRIS Sapienza author ID, AFNIL publisher ID, Institut de recherche pour le développement (IRD) identifier, TMOK ID, Kastra ID, Indigenous Corporation Number, United Nations Treaty Collection object ID, Österreichischer Fußball-Bund ID, MYmovies-Personenkennung, IGI Global Dictionary ID, L'Unificazione ID, EMBO member ID


 * Query examples:
 * Women born in Nigeria with an article in Basque for Listeria (Source)
 * Still life paintings by women (Source)
 * Map of cemeteries in New Zealand (Source)
 * Right Livelihood Award laureates (Source)
 * Chelsea FC players, with English Wikipedia article, Commons image, etc (Source)
 * Newest database reports: Missing properties by number of sitelinks: P22 (father) (works again)


 * Development
 * Finished preventing a case where the same sitelink could be added to two different Items (T291377)
 * Continuing work on the Mismatch Finder. Currently focusing on showing the details of the mismatches to the person reviewing mismatches.
 * Continued work on not allowing two Properties to have the same label after undo/revert (T289473)
 * Continuing work on improving how changes on Wikidata are propagated to Wikipedia and the other other Wikimedia projects. The new system is being rolled out to all wikis now. It should not change anything for editors and just be a technical improvement in the backend.

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.

Read the full report &middot; Unsubscribe &middot; Lea Lacroix (WMDE) 16:36, 4 October 2021 (UTC)
 * Monthly Tasks
 * Add labels, in your own language(s), for the new properties listed above.
 * Comment on property proposals: all open proposals
 * Suggested and open tasks!
 * Contribute to a Showcase item.
 * 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!

DYK nomination of 2021 La Palma volcanic eruption
Hello! Your submission of 2021 La Palma volcanic eruption at the Did You Know nominations page has been reviewed, and some issues with it may need to be clarified. Please review the comment(s) at your nomination's entry and respond there as soon as possible. Thank you for contributing to Did You Know! Flibirigit (talk) 16:54, 5 October 2021 (UTC)

DYK for Fundadores de São Paulo
Hog Farm Talk 04:25, 6 October 2021 (UTC)

Wikidata weekly summary #489
Here's your quick overview of what has been happening around Wikidata over the last week. 


 * Events
 * Upcoming:
 * We’re celebrating the 9th birthday of Wikidata on October 29 during the WikidataCon 🎂 Did you know that you can participate in the celebration by preparing a birthday present or attending events? Here’s how you can get involved!
 * Wikidata/Wikibase office hour, 16:00 UTC on Wednesday 20th October 2021 (18:00 Berlin time), on the Wikidata Telegram channel.
 * Upcoming: WMF search platform team office hour, Wednesday, October 13th, 2021 at 15:00-16:00 GMT / 08:00-09:00 PDT / 11:00-12:00 EDT / 17:00-18:00 CEST. Etherpad, Google Meet. You can come and chat about the Wikidata & Commons Query Service.
 * LIVE Wikidata editing #57 - YouTube, Facebook, October 16 at 18:00 UTC
 * Online Wikidata meetup in Swedish #83, October 17
 * Ongoing:
 * Weekly Lexemes Challenge #11, Perception and Senses


 * Press, articles, blog posts, videos
 * Blogs
 * Wikidata in African Language Communities
 * Media art on Wikipedia wants to make collections and metadata more accessible (in Dutch)
 * Papers
 * Modeling and Documenting Queer Voices and Topics on Wikidata, Panel on Metadata and Gender Diversity, Amber Billey, Clair A Kronk, John Samuel, Rachel Ivy Clarke, Sayward Schoonmaker, DCMI Virtual 2021, October 8, 2021, Slides
 * Videos
 * Introduction to Wikidata for beginners. Part 2 (in Italian) - YouTube
 * Introduction to Wikidata (in Spanish) - YouTube
 * Scripts and gadgets in Wikidata (in French) - YouTube
 * Wikidata Workshop 2021 - Coupling Wikipedia Categories with Wikidata Statements for Better Semantics - YouTube


 * Tool of the week
 * Neguess is a Wikidata entity guessing game with negative clues. (demo video)


 * Other Noteworthy Stuff
 * You can nominate your favorite Wikidata projects (tools, community initiatives, WikiProjects...) until October 10th for the WikidataCon Community Awards
 * You can also sign up for a slot at the birthday presents lightning talks session at WikidataCon 2021 to present your gift for Wikidata birthday until October 16
 * Submissions for day 2 and 3 of WikidataCon are still open. You can submit sessions about a variety of topics until October 20
 * Wikimedia Foundation is hiring a Graph Consultant to help migrate the Wikidata Query Service (WDQS) from Blazegraph to a different RDF store. Apply here!
 * The WMF Search team will begin data transfer for the new Streaming Updater today (11 Oct 2021).


 * Did you know?


 * Newest properties:
 * General datatypes: dissertation program, date of probate
 * External identifiers: Densho Encyclopedia ID, Institut de recherche pour le développement (IRD) identifier, DWDS lemma ID, Dizionario di Economia e Finanza ID, National Gallery Prague work ID, Hill Museum & Manuscript Library ID, Database of Czech Amateur Theater person ID, WDG lemma ID, The World Factbook country ID, AFNIL publisher ID, RICS company code, Greek Castles ID, Gente di Tuscia ID, Lexicon of Medieval Nordic Law ID, Product and Service Code, SAM ID, IRIS Sapienza author ID, museum-digital place ID, Det Norske Akademis Ordbok ID, PDDikti ID, VI.BE platform ID, Owler company ID


 * New property proposals to review:
 * General datatypes: registration number, present in non-fictional work, NIK (Nomor Induk Kependudukan), reports to, excitation energy, merger, split-off, choreography for
 * External identifiers: AllSides ID, Apple maps id, Enciclopedia dei ragazzi ID, NLI archive ID, CANTIC ID, Bat Sheva Archive ID, Research Vocabularies Australia ID, Australian Reptile Online Database ID, Chi era Costui - Plaque ID, Research Data Australia ID, Australian Institute for Disaster Resilience Knowledge Hub resource ID, Parliament of Australia MP ID, Trove work ID, Geographical Names Board of NSW geoname ID, Arachne.org.au ID, Remontees-mecaniques.net ID, Apple Music track ID


 * Query examples:
 * Share of women for each Nobel prize (source)
 * Nobel Prize statistics on number of recipients for award wrt. gender (interactive plot) (source)
 * Share of women among Nobel prize winners by decade
 * Notable books on linked data, semantic technologies, and semantic knowledge graphs (source)
 * Benelux railway stations connected from Brussels-South railway station (Q800587) (source)
 * Date of opening and closing of railway stations in Denmark (Source)
 * Map or Talaiotic archeological culture sites located in the Menorca island in Spain (source)
 * Location of all the meteorological stations in Navarre (source)
 * Photos of participants in the Pandora Papers (source)
 * Diameter, size and mass of balls (source)
 * French departments with their shape
 * Longest rivers located in France and which did not gave their name to a department (source)
 * [https://query.wikidata.org/#SELECT%20DISTINCT%20%3Fitem%20%3FitemLabel%20%3Fheight%20%3FcountryLabel%20%3FsubjectLabel%20%3Fcoords%20%3Fimage%20WITH%20%7B%0A%20%20SELECT%20%3Fitem%20%3FheightStatement%20WHERE%20%7B%0A%20%20%20%20%3Fitem%20wdt%3AP31%20%3Ftype%20.%0A%20%20%20%20VALUES%20%3Ftype%20%7B%20wd%3AQ1779653%20wd%3AQ179700%20wd%3AQ1051606%20wd%3AQ29168169%20wd%3AQ3476533%20%7D%0A%20%20%20%20FILTER%20NOT%20EXISTS%20%7B%20%3Fitem%20wdt%3AP31%20wd%3AQ21745157%20%7D%0A%20%20%20%20FILTER%20NOT%20EXISTS%20%7B%20%3Fitem%20wdt%3AP5816%20wd%3AQ56556915%20%7D%0A%20%20%20%20%3Fitem%20p%3AP2048%20%3FheightStatement%20.%0A%20%20%20%20%7B%20%3FheightStatement%20pq%3AP518%20wd%3AQ179700%20%7D%20UNION%0A%20%20%20%20%7B%20FILTER%20NOT%20EXISTS%20%7B%20%3FheightStatement%20pq%3AP518%20%3Fx%20%7D%20%7D%20%20%20%20%0A%20%20%7D%0A%7D%20AS%20%25i%20WHERE%20%7B%0A%20%20INCLUDE%20%25i%20.%0A%20%20%3FheightStatement%20psv%3AP2048%20%5B%0A%20%20%20%20%20%20wikibase%3AquantityAmount%20%3FbaseHeight%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20wikibase%3AquantityUnit%20%5B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20p%3AP2370%2Fpsv%3AP2370%20%5B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20wikibase%3AquantityAmount%20%3FunitHeight%20%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20wikibase%3AquantityUnit%20wd%3AQ11573%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%5D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%5D%0A%20%20%20%20%5D.%0A%20%20BIND%20%28%20%3FbaseHeight%20%2a%20%3FunitHeight%20AS%20%3Fheight%20%29%0A%20%20FILTER%20%28%20%3Fheight%20%3E%3D%2030%20%29%0A%20%20OPTIONAL%20%7B%20%3Fitem%20wdt%3AP17%20%3Fcountry%20%7D%0A%20%20OPTIONAL%20%7B%20%3Fitem%20wdt%3AP625%20%3Fcoords%20%7D%0A%20%20OPTIONAL%20%7B%20%3Fitem%20wdt%3AP18%20%3Fimage%20%7D%0A%20%20OPTIONAL%20%7B%20%3Fitem%20wdt%3AP921%20%3Fsubject%20%7D%0A%20%20%23SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22%20%7D%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%22%20%7D%0A%7D%0AORDER%20BY%20DESC%28%3Fheight%29%20%3FcountryLabel%20%3FitemLabel%0A%20 Statues measuring more than 30 m in height (excluding the pedestal)] (Source)


 * Development
 * Mismatch Finder: We are continuing the work on the review part of the system. We are now working on letting reviewers indicate if the mismatch is on Wikidata, the other database, both or neither.
 * Fixed a bug where it was possible for two Properties to have the same label in a given language by undoing/reverting an edit (T289473)
 * Fixed a confusing error message that was being shown when trying to save geoshape / tabular data that doesn’t exist (T285758)
 * Removing some unnecessary entity link formatting in edit summaries and special pages to improve performance (T292203)
 * Fixing an issue with invalid dates that the API accepts but should not (T289417)
 * Migrated all Wikimedia wikis to use the new change dispatching system. This system is responsible for notifying the other wikis about edits made on Wikidata that affect their articles so the article is refreshed and edits are added to recent changes and watchlists.

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.


 * Monthly Tasks
 * Add labels, in your own language(s), for the new properties listed above.
 * Comment on property proposals: all open proposals
 * Contribute to a Showcase item.
 * 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!

Read the full report · Unsubscribe · Mohammed Sadat (WMDE) 15:36, 11 October 2021 (UTC)

This Month in GLAM: September 2021
About This Month in GLAM · Subscribe/Unsubscribe · Global message delivery · Romaine 22:33, 12 October 2021 (UTC)

Sockpuppet investigations/Llywelyn2000/Archive
Mike, the report had been disposed of and closed by. Once a report is closed, any clerk may archive it. The fact that you do not understand what happened does not entitle you to edit the archive and ask. As I said in my edit summary, if you want to get more info, talk to GeneralNotability or. I am going to revert you again. Please leave it alone.--Bbb23 (talk) 20:15, 8 October 2021 (UTC)
 * Where was the closing statement please? Mike Peel (talk) 20:17, 8 October 2021 (UTC)
 * Special:Diff/1048889956 GeneralNotability (talk) 20:20, 8 October 2021 (UTC)
 * Thanks. There's a mismatch between saying "Regrettably, I believe the best path forward is to block the editors" and them actually doing the block - and I completely missed the closure because of that. I'm upset by the conclusion, but as you say, it is separate from the archive editing. I won't repeat the edit. But I really hope that there will be an appeal here, and I'm also planning a general WTF post about this and other recent situations. Thanks. Mike Peel (talk) 20:25, 8 October 2021 (UTC)
 * Hi Mike, just commenting per the pings & was going to leave you a note here, but was tied up IRL for a bit (hence the editing drop off) and see a section was made. As Bbb23 says, I came along as the archiver after seeing 's close and that nothing seemed really amiss. I don't really have an opinion in this; in general, the closer is generally the best one to direct questions to that may arise. -- The SandDoctor Talk 20:40, 8 October 2021 (UTC)
 * This kind of archiving is really best done by bot, rather than a user, to avoid exactly this kind of issue. Nothing against you personally! Thanks. Mike Peel (talk) 20:43, 8 October 2021 (UTC)
 * Hi Mike. The process we use at SPI includes manual archiving as an essential part of our quality control.  As  said, the archiving clerk is looking to see that "nothing seemed really amiss".  That's mostly a check for mechanical things, like the text being formatted properly, tags applied if appropriate, the case is filed under the correct title, etc.  When I archive a case, I'll occasionally ask the closer a question or two, to verify that what was intended was indeed what was done.  That kind of review is beyond the ability of a bot.  That's the reason we don't want people editing the archives; once a case is archived, we know it has gone through this checking process.
 * That's not to say that users can't ask questions, or even voice objections. It's just that doing that in the archives is the wrong place.  Asking on the closer's talk page is certainly the right place to start.  I think you'll find that most SPI clerks (and certainly ) take WP:ADMINACCT seriously and are happy to answer reasonable questions on their talk page. -- RoySmith (talk) 21:12, 8 October 2021 (UTC)

−
 * I responded to the problem on the relevant talk page - but it was prematurely archived. Mike Peel (talk) 21:19, 8 October 2021 (UTC)
 * Where was it? I don't see it in the history of Wikipedia talk:Sockpuppet investigations/Llywelyn2000 or User talk:GeneralNotability. The only place a comment was left that I saw was on the archive, which isn't a talk page? I'm confused. -- The SandDoctor Talk 22:04, 8 October 2021 (UTC)
 * Sockpuppet investigations/Llywelyn2000/Archive. Mike Peel (talk) 09:11, 9 October 2021 (UTC)


 * I'm too close to this, so I deliberately took a few days away from this to come back to it when I was less frustrated about it. Coming back to it this eve, I want to raise three procedural issues that I have concerns with. I don't expect them to change anything in this case, I just want to share them with you in case they are helpful with improving the approach for future cases.
 * The closure should be clearly marked. We normally do this here by using an archive template and having the closing admin response at the top of the page. For a completely random example (1st of this month), see Articles_for_deletion/Log/2021_October_1 - you can clearly see that it's been archived, and see the conclusion. That was not the case here. I understand why the page isn't archived in place (for privacy reasons), but it should still be indicated as closed on the arxiv page.
 * GeneralNotability specifically mentions in his closing statement that "this is not a CU block". However, if you look at the block template posted at User talk:Llywelyn2000, there's no indication that this was the case - it was a block linked to a CU case. I haven't checked the other user accounts affected, but I assume that it's the same. This statement is buried at the bottom of the archived page, which is at least two clicks away from the user page. I'd strongly suggest making the conditions of the block clearer on the user page, or at least only one click removed.
 * There is no clear procedure for editors to comment on a recently closed CU case. This is what I tried to do, and I also saw a reverted comment at Wikipedia talk:Sockpuppet investigations/Llywelyn2000. The archiving felt very quick, and there was no clear alternative venue to post at. I don't know what the best solution is here.
 * I hope these thoughts are useful. Thanks. Mike Peel (talk) 18:06, 11 October 2021 (UTC)
 * , in order:
 * Why? Generally, the only people who care about archives (and which comment closed the case) are what I usually refer to as "SPI personnel" - clerks, CUs, and the occasional patrolling admin. It is not a discussion forum, nor a place where consensus is required. The purpose of the various steps in the process are to help the aforementioned SPI personnel track the progress of the case.
 * You have things backwards. Blocks are checkuser blocks if and only if they are marked with checkuserblock (or one of its variants). I think (though don't have data to confirm) that most blocks coming out of SPI are normal administrative blocks rather than checkuser blocks. Also, I'm not a checkuser, so I cannot apply checkuser blocks myself. The only reason I made that comment was because a checkuser marked the accounts in the case as confirmed, which usually does result in a checkuser block. Further, your next bullet refers to these as "CU cases" - these are sockpuppet investigation cases, which may or may not involve CU, and the block may or may not be a CU block even after CU is run. We did have Requests for checkuser once upon a time (I believe it and Suspected sock puppets were merged to form SPI), but SPI is not exclusively checkuser-based.
 * If you have concerns about the handling of a case, you should either discuss it with the admins/clerks who handled the case (me, though if you have concerns about the CU findings you should discuss them with since she performed the check) or raise your concern at the clerk noticeboard. The archive step just means that a clerk has made sure all of the paperwork is done, everyone who should be blocked is blocked, etc.
 * SPI has plenty of bureaucracy already. I don't see the value in adding a formal closing statement or whatever - it is not a venue where we're trying to find a consensus decision, and the "closure" is usually some variation on either "I agree these appear to be sockpuppets, blocked" or "I don't think these are the same person." I am certain I have closed cases with the statement "Yup. Blocked." If you object to my actions, you can follow your choice of dispute resolution - raise it with me (done here, I guess), take it to WP:AN, unblock if you feel sufficiently un-WP:INVOLVED, even go to ArbCom if you feel that is appropriate. But again: SPI is not a consensus venue, and to be blunt, I do not think there is anything you could have said that would have changed my actions in this case. GeneralNotability (talk) 18:30, 11 October 2021 (UTC)
 * Mike, SPI isn't AfD. The way GN closed this is completely standard SPI process.  The people who hang out at SPI do tend to use a lot of jargon and verbal shortcuts.  That's unfortunate, and could be improved, but it is what it is.
 * Regarding the "checkuser block" question, please see WP:CUBL. Seriously; please go read it and ask questions if anything is unclear.  In short, if the comment in the block log said  checkuserblock or checkuserblock-account, that triggers specific requirements, most notably that if another admin were to unblock the user without getting explicit permission from a CU, they would be subject to being desysopped.  I see you're an admin; you really should know that.  You really don't want this to happen to you, and "I didn't know what checkuserblock meant" is unlikely to be a useful argument.  What GN was saying was, "Even though a CU did a check, this block is explicitly not a checkuserblock and thus doesn't trigger the CUBL requirements."
 * I agree with you about your last point. People comment on the archives of closed SPIs on a regular basis.  I did so myself once a long time ago and got slapped for it.  That fact that it happens so frequently is a good indication that we need both more clarity about the rule (maybe an edit notice on archives?), and a more obvious venue for people to discuss archived cases.
 * I offer no opinion on the block itself. I just wanted to address the procedural issues you brought up. -- RoySmith (talk) 18:39, 11 October 2021 (UTC)
 * Mike, I think you might be confused on how checkuser blocks are marked. Here's an example of one I made not terribly long ago: User_talk:FutureWorldCup. The corresponding log entry looks like this: . We use variants of in the block log, and sometimes the user talk when we mark things as CU blocks. I don't see anywhere that GN alluded to it being one, and neither the userpage, nor the block log of the editor in question uses these templates, or similar verbiage.  SQL Query Me!  20:07, 11 October 2021 (UTC)

Thanks for the replies. With respect, I think you are both too close to the process to understand how others perceive it. Please take a step back and consider it from a more remote perspective. Consider that not everyone even knows what SPI or CU means in this context. Again, please remember that I'm not complaining about what happened - but I think the process can be improved.

With the specific points I raised:
 * 1) Remember that the archives will be read by the affected people - both the editor that is directly affected, their active on-wiki colleagues, and anyone that comes across their talk page in the future and wants to understand what happened. You can't just think about them from the perspective of your SPI personnel.
 * 2) How would anyone looking at the user page know that you didn't issue checkuser blocks? It's certainly not obvious when looking at the specific user page that is affected by the block - but you still linked to a checkuser page as the reason from the block. With WP:CUBL, that makes sense - providing you know the relevant templates. Otherwise, you're looking at a user page that says "for canvassing and/or meatpuppetry discussed at Wikipedia:Sockpuppet investigations/..." - so that's a CU block?
 * 3) The obvious place to comment on a case is the page about that case. In this case, that was the archived page - or at least, that's the first I saw of it when I saw the block. You shouldn't expect people to find user talk pages to comment on it (e.g., the only reason I started discussing it here was because I was asked to come back to this talk page).

I understand that in most cases you don't expect a consensus decision, and for good reason - normally you're processing private information and making a decision based on that, which only people that can see that private information can comment on. The exception to that rule really should be where people think that there is a false positive, and you should expect extra scrutiny when that happens.

And thanks Roy for noting that comments on the archives happen regularly - that's a clear indication that something needs to be improved with the processs. Thanks. Mike Peel (talk) 19:07, 11 October 2021 (UTC)


 * For 2: if it were a checkuser block, it would be marked as such. It was not marked as such. It is not a checkuser block. Also, the blocks and block notices were customized in this case - there is a standard SPI block template and there is a specific talk page template for CU blocks (starts with something like "Wikipedia's technical logs indicate..."). I chose to make a customized block notice instead. Do I also need to indicate that this wasn't a username block, a harassment block, an oversight block, or a vandalism block?
 * For 3: You keep insisting on commenting on the case, but: why do you need to comment on the case at all? What is it going to change? If you object to the blocks, raise it with the blocking admin (as you've done), but the SPI archives aren't the place for you to record your disagreement. I've seen the comment you wanted to make, and it was just "I don't see the closing statement" - we've been over that already, there isn't a closing statement, but the correct approach would have been to ask a clerk for help. This has been answered.
 * And for your final comment: no, Roy and I (and our fellow SPI clerks) are almost never acting on private information (and when we are, it's usually someone emailing us to say "hey, I found someone tweeting 'go vote on this deletion discussion' but it would be OUTING to link their twitter here" or "both of these users' names match employees at XYZCorp"). Neither Roy nor I are checkusers, we are normal administrators who happen to be SPI clerks. We don't see the technical data. We aren't charged with receiving private information. Aside from a short conversation on IRC with Amanda about the details of her findings (which still did not involve private evidence, and consisted of me asking a couple clarifying questions about the patterns she saw so that I could get a better handle on sockpuppetry vs meatpuppetry), everything I used to make my decision was present on that SPI. Of course people push back when they disagree with the findings, and of course there will be more scrutiny on high-profile cases. But this isn't a "false positive," as you say: I believe the technical data is accurate, and the users in question confirmed as much, but my decision to block was based on both the technical data and the behavioral evidence that I summarized in my comments. If you have further concerns about my use of the admin tools, ArbCom is that way GeneralNotability (talk) 19:52, 11 October 2021 (UTC)

(This is a partial reply) Thanks for the replies. With respect, I think you are both too close to the process to understand how others perceive it. Please take a step back and consider it from a more remote perspective. Consider that not everyone even knows what SPI or CU means in this context. Again, please remember that I'm not complaining about what happened - but I think the process can be improved.

With the specific points I raised:
 * 1) Remember that the archives will be read by the affected people - both the editor that is directly affected, their active on-wiki colleagues, and anyone that comes across their talk page in the future and wants to understand what happened. You can't just think about them from the perspective of your SPI personnel.
 * 2) How would anyone looking at the user page know that you didn't issue checkuser blocks? It's certainly not obvious when looking at the specific user page that is affected by the block - but you still linked to a checkuser page as the reason from the block. With WP:CUBL, that makes sense - providing you know the relevant templates. Otherwise, you're looking at a user page that says "for canvassing and/or meatpuppetry discussed at Wikipedia:Sockpuppet investigations/..." - so that's a CU block?
 * 3) The obvious place to comment on a case is the page about that case. In this case, that was the archived page - or at least, that's the first I saw of it when I saw the block. You shouldn't expect people to find user talk pages to comment on it (e.g., the only reason I started discussing it here was because I was asked to come back to this talk page).

I understand that in most cases you don't expect a consensus decision, and for good reason - normally you're processing private information and making a decision based on that, which only people that can see that private information can comment on. The exception to that rule really should be where people think that there is a false positive, and you should expect extra scrutiny when that happens.

And thanks Roy for noting that comments on the archives happen regularly - that's a clear indication that something needs to be improved with the process. Thanks. Mike Peel (talk) 20:17, 11 October 2021 (UTC)

It's that iron law again. Andrew🐉(talk) 08:43, 13 October 2021 (UTC)

Pi Bot & CC-By-SA
Hey Mike, I'm not sure the best place to have the discussion - can you explicate what Pi Bot copies from Wikipedia into WikiData and how you're ensuring it's not violating copyright? Thanks, The Cunctator (talk) 15:52, 6 October 2021 (UTC)
 * You can find all the info about Pi bot on its user page, User:Pi bot. It doesn't copy anything long enough to violate copyright. Thanks. Mike Peel (talk) 15:55, 6 October 2021 (UTC)
 * Cumulatively, it copies entire books' worth of content. Furthermore, there's no set legal definition of a short enough passage to avoid violating copyright. At least under U.S. law. Fair use is an affirmative defense, for which the *defendant has the burden of proof*. --The Cunctator (talk) 01:15, 13 October 2021 (UTC)
 * The cumulative amount doesn't matter. If people are writing whole passages as short descriptions, that's a different problem here (and pi bot avoids that by checking the length of the descriptions before copying them). There's actually a tracking category for that at Category:Articles with long short description. Fair use is different: this is simply uncopyrightable material. And this was a lot clearer when we were just using the short descriptions directly from Wikidata. Thanks. Mike Peel (talk) 06:58, 13 October 2021 (UTC)
 * What's the basis for you saying that this is uncopyrightable material? I honestly don't understand that. --The Cunctator (talk) 14:08, 13 October 2021 (UTC)
 * For example, see or . Thanks. Mike Peel (talk) 14:27, 13 October 2021 (UTC)

Nomination for deletion of Template:AutoMapZoom
Template:AutoMapZoom has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. WikiCleanerMan (talk) 21:37, 16 October 2021 (UTC)

Wikidata weekly summary #490
Here's your quick overview of what has been happening around Wikidata over the last week. <div style="-moz-column-count:2; -webkit-column-count:2; column-count:2; -webkit-column-width: 400px; -moz-column-width: 400px; column-width: 400px;">


 * Discussions
 * New request for comments
 * Frequency of YouTube follower count data
 * Should previously linked Wikipedia articles be separated?


 * Events
 * Upcoming:
 * We’re celebrating the 9th birthday of Wikidata on October 29 during the WikidataCon 🎂 Did you know that you can participate in the celebration by preparing a birthday present or attending events? Here’s how you can get involved!
 * Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Scottish Accused Witches Project with Ewan McAndrew and Emma Carroll (University of Edinburgh)., Oct 19th.
 * WikiProject Govdirectory Collab Hour, October 22
 * LIVE Wikidata editing #58 - YouTube, Facebook, October 23 at 18:00 UTC
 * Online Wikidata meetup in Swedish #84, October 24
 * IT Festival Without Borders from 21 to 23 October 2021 in Rovereto - There will be a Wikidata for SPARQL queries workshop for high school and university students.
 * Ongoing:
 * Weekly Lexemes Challenge #12, Health professions
 * #12MonthsofOSM, mapping historical features


 * Press, articles, blog posts, videos
 * Blogs
 * Introduction to Observablehq.com for Wikidata users in French (Introduction à Observable pour les utilisateurs de Wikidata)
 * Learning to edit Wikidata is challenging; we aim to make it easier with this interactive course
 * Manuscripts on Wikidata: the state of the art? by Martin Poulter
 * Digital scholarship in archives: A data case study
 * Papers
 * Accepted papers for the Wikidata Workshop at ISWC have been published: https://wikidataworkshop.github.io/2021/
 * Detecting Cross-Language Plagiarism using Open Knowledge Graphs
 * Videos
 * Wikidata Scripts and gadgets (in French) - YouTube
 * Import RDF data from Wikidata (part 11) - YouTube
 * New introductory working hour on Wikidata (in Italian) - YouTube
 * Building Wikidata - Queries with Wikidata Query Service (in Spanish) - YouTube
 * Building Wikidata - Databases and Open Refine (in Spanish) - YouTube
 * How to retrieve the list of works by Canadian authors available on Wikisource? (in French) - YouTube
 * Other:
 * Research project: How can museums improve the usability of collection APIs?


 * Tool of the week
 * Snowman is a static site generator for SPARQL backend (source)


 * Other Noteworthy Stuff
 * Submissions for day 2 and 3 of WikidataCon are still open. You can submit sessions about a variety of topics until October 20
 * Sina Ahmadi has released a SPARQL query generator for lexicographical data
 * Wikidata reached the 10000th numbered property, with the creation of P10000 Research Vocabularies Australia. (There are currently 9285 pages in the Property namespace.)
 * Wikidata now has over 600,000 Lexemes!
 * Learn Wikidata is an online interactive course created by the Vanderbilt University thanks to a WikiCite grant and available in English, Spanish and Chinese. More information here.
 * The 3rd edition of the Coolest Tool Award is looking for nominations (see announcement on wikimedia-l). Please submit your favorite tools by October 27th. The awarded projects will be announced and showcased in a virtual ceremony in December.


 * Did you know?


 * Newest properties:
 * General datatypes: catalogue raisonné, predicate for, has thematic relation, illustrative content, ITU radio emission designation, isotopically modified form of, stylized name, record number, excitation energy
 * External identifiers: WDG lemma ID, The World Factbook country ID, AFNIL publisher ID, RICS company code, Greek Castles ID, Gente di Tuscia ID, Lexicon of Medieval Nordic Law ID, Product and Service Code, SAM ID, IRIS Sapienza author ID, museum-digital place ID, Det Norske Akademis Ordbok ID, PDDikti ID, VI.BE platform ID, Owler company ID, Ordbog over det danske sprog ID, Svenska Akademins Ordbok-section ID, Kalliope-Verbund ID, musik-sammler.de artist ID, United Nations Treaty Collection object ID, Washington Rare Plant Field Guide ID (Web version), RAWG game ID, TMOK ID, Vokrug sveta article, copyright registration, Eneström Number, NRK TV ID, NLI Archive (bibliographic) ID, L'Unificazione ID, IGI Global Dictionary ID, Enciclopedia dei ragazzi ID, CANTIC ID, EMBO member ID, NDL earlier law ID, AbandonSocios ID, Bat Sheva Archive ID, Literature.com book ID, Literature.com ebook ID, CantoDict word ID, CantoDict character ID, MYmovies person ID, Chi era Costui plaque ID, Bowers acronym, Turkish Cinema Archive Database person ID, Research Vocabularies Australia ID, Austrian Football Association player ID, Dewan Negara ID, Arachne.org.au ID, Dewan Rakyat ID, Remontees-mecaniques.net ID


 * New property proposals to review:
 * General datatypes: merger, split-off, choreography for, classification, compartmentalisation, or information category for this document, Hotel rating, NatureScot Sitelink ID, pole positions, podium finishes, StopGame ID, fastest laps, Amends, heading, Conway polyhedron notation
 * External identifiers: Australian Reptile Online Database ID, Research Data Australia ID, Australian Institute for Disaster Resilience Knowledge Hub resource ID, Parliament of Australia MP ID, Trove work ID, Geographical Names Board of NSW geoname ID, Apple Music track ID, Bokmålsordboka-ID, Nynorskordboka-ID, Birdata ID, IRIS Superior Graduate Schools IDs, Australian Trade Mark Number, Australian Prints + Printmaking artist ID, Australian Prints + Printmaking work ID, FFCAM ID, TVSA ID, Academy of Russian Television person ID, NSW Parliament Member ID, Australian Statistical Geography 2021 ID, KPU Calon 2019, Monaco Nature Encyclopedia ID, Refuges.info ID, Smotrim.ru film ID, Norgeshistorie ID, AHPRA registration number, PubCRIS product number, Toolhub ID, Spotify user ID, Dizionario di Medicina ID, Dizionario delle Scienze Fisiche ID, ORIAS number, SNSF person ID


 * Query examples:
 * List of written works authored by recent Nobel laureate Joshua Angrist (via d:Template:Item documentation on d:Talk:Q921499)
 * Books by Canadian authors with a Wikisource page (Source)
 * Repetitive taxon names (Source)
 * Count of sitelinks of museums/tourist attractions in the US (Source)
 * Map of French communes that are >30 characters long (Source)
 * Lexemes in Swedish that are missing in Svenska Akademiens Ordbok (Q1935308) (Source)
 * Attendance at the Bargoin, Roger-Quilliot and Henri-Lecoq museums per year (Source)
 * Present and past members of Czech Chamber of Deputies who are relatives (Source)


 * Development
 * Mismatch Finder: We are continuing the work on the review part of the system. We are working on letting reviewers submit their decision if the mismatch is on Wikidata, the other database, both or neither.
 * In the previous week we migrated all Wikimedia wikis to use the new change dispatching system. This system is responsible for notifying the other wikis about edits made on Wikidata that affect their articles so the article is refreshed and edits are added to recent changes and watchlists. This week we monitored the new system and investigated and fixed a few issues that came up.

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.


 * Monthly Tasks
 * Add labels, in your own language(s), for the new properties listed above.
 * Comment on property proposals: all open proposals
 * Contribute to a Showcase item.
 * 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!

<div style="margin-top:10px; font-size:90%; padding-left:5px; font-family:Georgia, Palatino, Palatino Linotype, Times, Times New Roman, serif;">Read the full report · Unsubscribe · Mohammed Sadat (WMDE) 13:50, 18 October 2021 (UTC)