Here's your quick overview of what has been happening around Wikidata over the last week.
Welcome to 2023’s Final Weekly Summary!
A big thank you to everyone who contributed to the newsletter this year!👏🙏 As we step into 2024, we'd love to hear what changes you would like to see in the newsletter. Share your wishlist here: What changes would you like to see in the newsletter in 2024?"
Discussions
Open request for adminship: EPIC (RfP scheduled to end after 26 December 2023 20:34 UTC)
New requests for permissions/Bot: Balyozbot. Tasks:
Import sitelinks, labels, descriptions from ku wikipedia pages which use the template w:ku:Template:Înterwîkî etîket û danasîn. (There are over 1800 articles that use this template waiting to be connected to Wikidata at the moment.)
Add sitelinks to kuwiktionary / kuwikipedia categories / create an item for the category if necessary. I have been doing this manually for quite some time using Quickstatements but since I need to get permission for the first task, I will be handling them using a bot as well.
Upcoming: Introducing WMF Wishathon for Wikimedia’s Community Wishlist! "focused on bringing together people who already contribute to technical aspects of the Wikimedia projects, who know how to find their way on the technical ecosystem, and who are able to work or collaborate on projects rather autonomously." March 15th to 17th, 2024.
African Librarians empowered to share knowledge and enhance information visibility through AfLIA Wikidata Online Course --> The "Promoting Open Knowledge Practices in African Libraries through Wikidata" project, executed by AfLIA with support from the Wikimedia Foundation, trained African librarians on using Wikidata to enhance the visibility of library collections and close the knowledge and gender gap on Africa. The course was facilitated by experienced African Wikimedian editors and included diverse strategies for learner engagement and support.
Papers: Increasing Coverage and Precision of Textual Information in Multilingual Knowledge Graphs by (Conia et al, 2023) --> This paper introduces a novel task of automatic Knowledge Graph Enhancement (KGE) to bridge the gap in the quantity and quality of textual information between English and non-English languages in Wikidata. It presents M-NTA, an unsupervised approach that combines Machine Translation, Web Search, and Large Language Models to generate high-quality textual information, and studies its impact on Entity Linking, Knowledge Graph Completion, and Question Answering tasks.
Videos
Wikidata, Wikisource and Wiktionary: Wikisource for DH (WiSe 2023) --> The lecture "Fundamentals and application-oriented methods of the Digital Humanities" by Kay-Michael Würzner is designed as a series of lectures in which teachers in the "Digital Humanities" course present their fields of work and key topics and present them for discussion.
Empowering Open-Source Generative AI by Integrating the Wikidata knowledge graph --> Generative AI has changed the information ecosystem, and open-source knowledge graphs like Wikidata can become invaluable assets, propelling a myriad of applications forward. Jonathan Fraine & Lydia Pintscher present the practical integration of Wikidata's open-source, open-access knowledge graph to empower Generative AI applications. Harnessing the real-time updated, structured data encapsulated within Wikidata, they explore automated content creation, data augmentation, and semantic analysis, underpinning the generative paradigms. Through a blend of theoretical insights and real-world applications, they elucidate how to leverage Wikidata to elevate generative AI applications, breaking down existing data silos, and fostering a collaborative ecosystem within our global community of developers and contributors.
Wiki Indaba 2023 - African content on Wikidata --> Discussion with Alice Kibombo, Georges Fodouop and Jesse Asiedu-Akrofi, about Wikidata for African Librarians during the Wiki Indaba conference, that took place between 3-5 November 2023 in Agadir, Morocco.
No Time to Wait - S07E10 - ACMI // Wikidata - Paul Duchesne + Simon Loffler --> Report on recent residency program to extensively link together collection data from ACMI with Wikidata. This work has allowed the organisation to import vast quantities of data and media to enrich their own internet collection experience, as well enable writing information back to source and federating with other linked institutions.
Map of K-Pop Idols --> An interactive map where each red dot represents a K-pop Idol (a singer or musician in South Korean Pop music) you are able to click on.
Disney as the Mega Corporation it is Today --> Disney has greatly evolved from the simple animation company that first debuted in 1923 with its signature Steamboat Willie animation. This analysis details some of the major acquisitions Disney has chosen to help expand its reach as a media and entertainment company.
State of statues in the US --> Map of how many statues there are, who is depicted in the statues, their genders, and where the statues are concentrated.
An Analysis on Nepo Babies: Net Worths and Fame --> This work uses Wikidata to analyze the influence and success of children of famous actors (nepo babies) in the entertainment industry, and compares the careers and net worth of these children with their parents to understand the impact of nepotism on their success.
Tool of the week
Cersei - is a tool designed for importing or scraping data from various third-party sources, using source-specific Python code. It can use a "headless browser" to scrape complicated websites that rely on eg JavaScript to navigate. It can therefore access data sources that can not be accessed via eg Mix'n'match. The data from sources can be updated regularly, either for everything, or just changed entries (if the source has a "recent changes" equivalent).
Wikidata:Zotero/Cita - is a Wikidata addon for Zotero that adds citations (i.e., what other items an item cites) metadata support to this open source reference management software, using cites work (P2860) information available from Wikidata, and enabling users to easily contribute missing data.
production manager (manager that is responsible for the administration of a feature film or television production; oversees production plans, controls resources, initiates production, ensures ongoing operations, monitors schedules and expenditures, and creates a detailed production schedule and budget)
Newest WikiProjects: WikiProject Städel Museum Wikidata Clean-Up - This WikiProject from the Städel Museum aims to actively participate in the Wikimedia community by maintaining and updating the quality of its data. This includes their collection of public domain art, which has been digitized and made freely available for public use. The project focuses on ensuring that the most current and high-quality data, including high-resolution images and improved metadata, are available on platforms like Wikimedia Commons and Wikidata.
Upcoming: The next Wikidata+Wikibase office hours will take place on Wednesday, 17:00 UTC, 17th January 2023 (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
Papers: Improving maintenance of community-based knowledge graphs. This paper by Nicolas Ferranti addresses the critical issue of data quality in open knowledge graphs, with a specific focus on Wikidata. It aims to formalize Wikidata's unique approaches to assess and resolve data inconsistencies, proposing a semi-automatic refinement pipeline to empower the Wikidata user community in maintaining and enhancing the reliability of this extensive collaborative knowledge graph.
Videos: WikidataCon 2023 Day 1.5 - The past and future of Wikidata. In this video Lydia Pintscher takes a moment to review the major events of Wikidata over the past few years. Then turns to look forward and predict what Wikidata's prospects will be over the next year.
Tool of the week
WICA: Wikidata's insights for created articles is an updated version of an old tool. It now includes many new features to analyse your list of created articles using Wikidata properties.
Nonprofit Status (Indicating the legal and tax status of a non-profit organization (specific to served legal areas, aka. Countries). Addition to ((P|1454)). ((P|1628)) to [https://schema.org/nonprofitStatus nonprofitStatus] from schema.org. Organizations can have multiple Nonprofit Status from different countries.)
creative director (person who makes high-level creative decisions, oversees the creation of creative assets such as adverts, products, events or logos and guides and directs the creative people who create the end result)
The next Wikidata+Wikibase office hours will take place on Wednesday, 16:00 UTC on Wednesday, 17th January 2024 (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
Blogs: PubChem on Wikidata – What is the state of coverage? by Tiago Lubiana. In summary, Wikidata has good coverage of the structured chemical data in PubChem, though there are improvement points. PubChem displays, and will always display, textual information and vendor-specific data that do not fit Wikidata, but they are complementary tools in the ecosystem of open chemical data.
LIS Journals’ Lack of Participation in Wikidata Item Creation by Eric Willey & Susan Radovsky, discusses the gap of Wikidata items being created for scholarly articles by the scholar's themselves and if this can lead to inconsistent or inaccurate data model.
Quantifying Americanization: Coverage of American Topics in Different Wikipedias: this paper asks whether there is an americanisation bias in the content created by the communities. By Piotr Konieczny & Włodzimierz Lewoniewski.
Videos
Map Kerala Initiative is an opendata portal geospatial map powered by Wikidata and OpenStreetMap, introduced by Manoj Karingamadathil.
Notebooks: Wikipedia article as a timeline - This tool transforms a Wikipedia article in a timeline by parsing all internal links in a Wikipedia article and retrieving the date corresponding to each internal link using the point in time (P585) property in Wikidata.
Tool of the week Map your list of created articles - a notebook display of geolocated articles on a map created by a user per chosen project and batch (featured/good article).
Other Noteworthy Stuff
Wikimedia Indonesia and Wikimedia Deutschland ended their partnership within the project Software Collaboration for Wikidata prematurely. Read their joint statement here.
IP masking/temporary accounts: We are adjusting Wikibase to be prepared for the upcoming changes to no longer expose IP addresses for non-logged-in users (phab:T351968)
Dumps/lex. data: We’re adjusting how empty lists of Forms and Senses are represented in JSON dumps (phab:T305660)
Wikibase REST API:
We finished the work on making it possible to get all sitelinks of an Item (phab:T344041)
We are working on getting a sitelink for a given wiki (phab:T344039)
PARAKANYAA, yes, I know. I was trying to catch more WikiProjects that I missed, but there seems to be a bug in the code (it takes over an hour to run the code that fetches all the wikiprojects, so I left it to run). — Qwerfjkltalk18:21, 14 January 2024 (UTC)[reply]
Hi. The CfD slipped out of my watchlist so I just saw that Marcocapelle already did the purging per the closure. You noted yesterday that it'd been listed for bot renaming, but I'm not seeing it. Perhaps the edit failed? --Paul_012 (talk) 11:22, 14 January 2024 (UTC)[reply]
Here's your quick overview of what has been happening around Wikidata over the last week.
Discussions
New request for comments: Community request for the development team to access inverse properties on client wikis. (Summary: We currently cannot access inverse property values on Wikipedia. This can be a data management issue on Wikipedia as we must always ask ourself if we must introduce an inverse property for cases where we need them. So I think it’s useful to gather the usecases community would want and draft a request for an API to the devteam to do that.)
Upcoming: The next Wikidata+Wikibase office hours will take place on Wednesday, 16:00 UTC on Wednesday, 17th January 2024 (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
Past
Provenance Loves Wiki (PLW24), Jan 12th - 14th, research and data on the origin of artworks and cultural heritage and how Wikibase and Wikidata can support this.
WikiLovesWomen #SheSaid campaign wrapped up the 2023 campaign by visiting Kinshasha and Kisangani, where local Wikimedians improved quotes from women on FR Wikipedia and Wikidata.
QLever: a new way to query OpenStreetMap --> Discussion of the new opportunities offered by QLever to query OpenStreetMap and to run federated queries with Wikidata
Wikidata for authority control: 3 years of work --> The three-year Wikidata for authority control project, a collaboration between Wikimedia Sverige and Swedish museums, concluded in December 2023. It equipped museum staff with tools and skills to integrate their authority databases with Wikidata, resulting in added identifiers, SPARQL query proficiency, and enhanced knowledge sharing within the GLAM sector.
Go-ahead for Wikidata Project of GLAM institutions from Baden-Württemberg --> The GLAM-BW project, under "GLAM goes OpenData," connects major collections in Baden-Württemberg, focusing on the württembergische Kunstkammer. With over 3,000 objects, the project integrates information on collectors, histories, and objects into a knowledge graph for semantic searches, contributing to the broader realm of linked open data, akin to Wikidata.
Swiss GLAM Programme --> Wikimedia CH imported the Museum of Natural History of Neuchâtel's urchin fossil casts to Wikimedia Commons, connecting structured data on Wikidata. The project involved data cleaning, adding missing elements, and file imports via OpenRefine, highlighting seamless integration between Wikidata and Commons.
Papers
Reflections on the PCC Wikidata Pilot at UCLA Library: --> Undertaking the PCC Learning Objectives. Discusses the 14-month Pilot programme for cooperative cataloguing of UCLA Library and Museum Collections. By E. Zhang, P. Biswas & I. Dagher.
SMWCon 2023: Semantics, Wikis, and AI --> Day 1, Keynote by Prof. Markus Krötzsch who explores origins and principles of semantic wikis and key challenges that lie ahead in managing knowledge.
Brian M Sperlongano released US boundary QA checker, a quality assurance tool for finding issues with boundary data in the United States by using Wikidata, OpenStreetMap, and US Census Bureau data.
The Surrounding Ocean (available at vrandezo.github.io/TheSurroundingOcean) - is a tool that allows you to browse lexicographical data. You can use the tool to explore words and their meanings, translations, and synonyms. The tool is currently under development, and the developer, Danny, would appreciate feedback to fix any issues with the tool. More info: Wikidata:The Surrounding Ocean.
WikiProject Highlights: Ontology Cleaning Task Force: A group of people have started a task force to discuss problems with the Wikidata ontology and how to clean them up. Anyone interested in participating is welcome. The task force maintains Wikidata:WikiProject Ontology/Cleaning Task Force as a record of its activities. You can add yourself to the participants list there and find out how to join group meetings or otherwise participate in the group. (Got something noteworthy happening in your WikiProject? Share it in the upcoming issue!)
IP masking: We are working on adjusting Wikibase to handle the upcoming introduction of IP masking, which will give editors who are not logged in a temporary account name instead of using their IP to attribute edits to (phab:T351968)
Lexicographical data: We are changing how empty Senses and Forms are represented in the dumps (phab:T305660)
mul language code: We are doing user testing for the current implementation to see if it is understandable for people.
Mismatch Finder: We are continuing the work on migrating it to the Codex design system.
REST API:
We improved the handling of lower-case statement IDs (phab:T354262)
We are working on getting a sitelink for a given wiki (phab:T344039)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
Pages that use the JSON contentmodel will now use tabs instead of spaces for auto-indentation. This will significantly reduce the page size. [1]
Gadgets and personal user scripts may now use JavaScript syntax introduced in ES6 (also known as "ES2015") and ES7 ("ES2016"). MediaWiki validates the source code to protect other site functionality from syntax errors, and to ensure scripts are valid in all supported browsers. Previously, Gadgets could use the requiresES6 option. This option is no longer needed and will be removed in the future. [2]
An update on the status of the Community Wishlist Survey for 2024 has been published. Please read and give your feedback.
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 16 January. It will be on non-Wikipedia wikis and some Wikipedias from 17 January. It will be on all wikis from 18 January (calendar). [5][6]
Starting on January 17, it will not be possible to login to Wikimedia wikis from some specific old versions of the Chrome browser (versions 51–66, released between 2016 and 2018). Additionally, users of iOS 12, or Safari on Mac OS 10.14, may need to login to each wiki separately. [7]
The jquery.cookie module was deprecated and replaced with the mediawiki.cookie module last year. A script has now been run to replace any remaining uses, and this week the temporary alias will be removed. [8]
I used Rater to make a few wikiproject assessments and your bot came by to make edits like this one: [9]. Is it supposed to be doing this? This does not appear to change the behaviour or appearance of the banners. -- asilvering (talk) 03:43, 16 January 2024 (UTC)[reply]
Ah, I missed the earlier question similar to mine above. Is this something that can be avoided by changes to Rater? I don't really want to have a bot following up on every single edit I make with this tool if I can avoid it. -- asilvering (talk) 03:47, 16 January 2024 (UTC)[reply]
I'm wondering why the bot is removing "|1=" from ((WikiProject banner shell)) when the template documentation still shows to use this. When doing talk page tidying for WikiProjects, AWB keeps wanting to restore it after it's been removed. Has the documentation for the template simply not caught up? Or is the bot malfunctioning by chance? Stefen Towers among the rest!Gab • Gruntwerk07:24, 16 January 2024 (UTC)[reply]
But the bot edit above was doing a cosmetic edit just the same, and against the shell's documentation. Further, tidying of something like that using AWB usually goes along with other banner tidying. At any rate, cosmetic, tidying edits on talk pages are taken differently than on subject pages. Stefen Towers among the rest!Gab • Gruntwerk17:54, 16 January 2024 (UTC)[reply]
Marvel De brave, Welcome! Creating a new article from scratch is extremely challenging, and new editors are strongly recommended to spend a few months learning how Wikipedia works, by making improvements to some of our existing six million articles before trying it. When you do decide to have a go at a new article, you are highly encouraged to read WP:Your first article. If you haven't already also check out WP:TUTORIAL; it's a lot of fun! Happy editing! — Qwerfjkltalk07:40, 17 January 2024 (UTC)[reply]
We already have user:Cewbot doing this substantially pointless and distracting busywork and cluttering up everyone's watchlists. Is it really necessary to have several bots involved, each with their own complaints, discussions, bug reports/fixes, etc.? –jacobolus(t)04:22, 17 January 2024 (UTC)[reply]
Jacobolus, if I thought it was pointless I wouldn't be doing it. But that aside, the reason we have two bots is simply because things worked out that way (I filed my BRFA and then the one for Cewbot came later and with a slightly different scope). I do of course keep track of Kanashimi's talk page. — Qwerfjkltalk07:44, 17 January 2024 (UTC)[reply]
It's not completely pointless, but it is fairly disruptive by creating a massive amount of watchlist noise for a largely trivial benefit. It is going to end up touching essentially every (talk) page on the site, including those which ordinarily get ~1 edit every 6 months, where literally nobody cares they have a Wikiproject X banner by itself or wrapped in an extra frame. Editors watching substantial numbers of pages are going to have their watchlists completely flooded, with along the lines of tens to hundreds of times the ordinary volume of changes, potentially lasting for an extended period of time.
From what I can tell no particular effort has been made to figure out how to minimize this disruption. My recommendation would be to try to piggyback these trivial edits on top of other more substantive edits. That is, wait until some page on the list gets edited by anyone, and then make the banner twiddling changes immediately afterward. This would almost entirely eliminate the disruption, while not materially affecting the banner shell project. –jacobolus(t)08:28, 17 January 2024 (UTC)[reply]
Jacobolus, whilst yes, it would be technically feasible to piggyback other edits, it would be practically infeasible. I would have to write the code for that, which wouldn't be trivial, and then I would have to somehow keep track of everypage my bot has edited to avoid re-editing pages, and I would also have to actively update the code to avoid any bugs that crop up. The watchlist problem is only something you experience if you monitor bot edits, so here's my alternative: You are worried (understandably) about the bot making errors it its edits. What you could do is hide the bot's edits from your watchlist, and then do a spot check of the bot's edits, as many as you like. Would this be acceptable? — Qwerfjkltalk08:34, 17 January 2024 (UTC)[reply]
How do I exclude just one bot or one bot purpose from the watchlist? Is there a particular "tag" related to this banner shell conversion project? –jacobolus(t)08:40, 17 January 2024 (UTC)[reply]
Why is it hard to make a new tag? Since this is going to touch nearly every page on the site, wouldn't this be the exact type of situation where jumping through a few extra hoops to help minimize the disruption would be most worthwhile? –jacobolus(t)08:58, 17 January 2024 (UTC)[reply]
Arunima Sudha, Welcome! Creating a new article from scratch is extremely challenging, and new editors are strongly recommended to spend a few months learning how Wikipedia works, by making improvements to some of our existing six million articles before trying it. When you do decide to have a go at a new article, you are highly encouraged to read WP:Your first article. If you haven't already also check out WP:TUTORIAL; it's a lot of fun! Happy editing! — Qwerfjkltalk07:40, 17 January 2024 (UTC)[reply]
Bot run and missing header discussions
Hey Qwerfjkl, I was wondering how much more difficult would it be to add to the talk page bot run a fix to discussions with a missing header (this is a genfix in AWB; full list here). So a page like Talk:168th New York State Legislature which your bot edited would also do the edit I did after. Gonnym (talk) 13:10, 17 January 2024 (UTC)[reply]
Gonnym, how would I detect if there was a discussion with a missing header? I'm also not sure it would be a good idea to add to the bot's functionality at this point. — Qwerfjkltalk14:37, 17 January 2024 (UTC)[reply]
Schierbecker, thank you for bringing my attention to this. I've fixed it now. There was a flaw in my logic for detecting opted-out wikiprojects. I will revert and rerun the bot on the milhist pages with issues. — Qwerfjkltalk19:36, 17 January 2024 (UTC)[reply]
Hawkeye7, while this is another flaw, it's covered by the same fix, because my bot won't modify the classes on opted-out wikiprojects, regardless of what value class= (unless, I think, it's blank and the page is a talk page of a redirect/dab, in which case it will remove class=). — Qwerfjkltalk19:57, 17 January 2024 (UTC)[reply]
Hi, it's me again. This doesn't change the output and would be regarded as a cosmetic edit. I don't know if the bot is still performing this task (I have been away for a few days), but please avoid these edits in the future. Thanks. InfiniteNexus (talk) 07:58, 18 January 2024 (UTC)[reply]
Thank you for all the good work this bot is doing. All the cosmetic edits I've spotted consist of removing an unnecessary but harmless "1=" from a parameter. Would it be worth wrapping the save code in an if block for this specific case? Certes (talk) 20:14, 20 January 2024 (UTC)[reply]
Certes, it's not quite as simple as that. I'm using the python library mwparserfromhell to parse the pages, and it strips the 1= by default if it's unnecessary. I'll have to look in to how to disable that. — Qwerfjkltalk22:14, 20 January 2024 (UTC)[reply]
Is there a reason for that? I noticed that Cewbot was doing the same thing as well. Virtually all disambiguation talk pages do not wrap ((WikiProject Disambiguation)) in ((WikiProject banner shell)) (that's around 319,444 pages); are all of those pages going to be adjusted? Same thing for redirect, file, and category talk pages. If there is no meaningful reason for this change, I think that would just create more disruption on users' watchlists. InfiniteNexus (talk) 19:04, 21 January 2024 (UTC)[reply]
InfiniteNexus, that's the whole point of PIQA - that WPBS is added to all pages. I'm only running the bot on talk pages (i.e. namespace 1), so file and category talk pages will be unaffected, — Qwerfjkltalk20:33, 21 January 2024 (UTC)[reply]
Technically you are correct and I do see your point. If you think this aspect needs further discussion we can pause the processing on the single-banner pages. My view is that the logical conclusion of PIQA is that all ratings will eventually be in the banner shell and none in the separate banners. At this point, any rating placed in a banner will be redundant (if it is the same as the shell rating) or conflicting (if it is different). Neither of these are ideal, so I envisage that the class parameter will be deactivated completely from individual banner templates and the only way to assess quality will be via the banner shell. That is certainly the direction we are moving, but happy to discuss further.
With all the work done to the shell, I see it as a net positive. And I'm one of those that has a lot of redirect pages on my watchlist and I'm fine with the "spam". Gonnym (talk) 17:22, 22 January 2024 (UTC)[reply]
What is the net positive? Does it affect categories or anything like that? If not, and the only change is the appearance of the banner, then that would be the definition of a cosmetic edit. I envisage that the class parameter will be deactivated completely from individual banner templates and the only way to assess quality will be via the banner shell Redirects and DAB pages are automatically detected as redirects or DAB pages. Oftentimes, there is no |class=redirect or |class=NA tag attached to the WikiProject banner(s). InfiniteNexus (talk) 05:22, 23 January 2024 (UTC)[reply]
Well, that's the technical, wikilawyerable definition of "cosmetic edit", but as WP:COSMETIC notes, the term cosmetic edit is often used to encompass all edits of such little value that the community deems them to not be worth making in bulk, even though those edits might change the output HTML or readable text in subtle ways. If there's no benefit to changing these other than aesthetic purposes, then the bot is operating without consensus because this is not what the community !voted to do (it was to unify project-dependent quality assessments and redesign the banner shell template, nothing more). InfiniteNexus (talk) 07:10, 23 January 2024 (UTC)[reply]
That is a rather confusing sentence on the page, because the definition of a cosmetic edit is one which changes the wikicode but does not change the output. I agree that the truly cosmetic edits should be avoided by the bot if at all possible. To address the substance of your complaint, is it only the single-banner non-mainspace edits that you have a problem with? If so, I suggest leaving those pages for now and we can perhaps discuss it later (at a more suitable venue). I agree they are not urgent and do not address the core purpose of PIQA. If you are agreeable to this approach, I will ask the other bot operator to follow suit — Martin (MSGJ · talk) 08:47, 23 January 2024 (UTC)[reply]
I did not research how that sentence got into that dictionary page, but it was an invalid interpretation of WP:COSMETICBOT, which is policy. I have copy-edited that whole section to match the policy, which has been hashed out in great detail over the years and which has been pretty stable for a while, IIRC. If proposed bot edits have such little value that the community deems them to not be worth making in bulk, then the relevant BRFA will, or should, not be approved. That's part of what BRFA is for. – Jonesey95 (talk) 16:15, 23 January 2024 (UTC)[reply]
Is it only the single-banner non-mainspace edits that you have a problem with? Redirects and disambiguation pages are technically in the mainspace. But yes, if there is only one banner, and there is no |class= (because it is automatically detected), then it is unnecessary to add a banner shell. InfiniteNexus (talk) 17:53, 23 January 2024 (UTC)[reply]
Thank you. The next step, if you and/or the other bot operators believe it is beneficial to use WPBS on single banners on non-article talk pages, would be to gain consensus at a centralized location (probably not here). InfiniteNexus (talk) 18:26, 23 January 2024 (UTC)[reply]
What exactly is the issue here? An explicit |1= does nothing on WPBS. It can be removed by bot, but only as part of a larger substantive edit. Headbomb {t · c · p · b}20:43, 23 January 2024 (UTC)[reply]
WP:COSMETIC originally stated: The term cosmetic edit is often used to encompass all edits of such little value that the community deems them to not be worth making in bulk, even though those edits might change the output HTML or readable text in subtle ways. This was contested by two editors (MSGJ and Jonesey95), and the challenged wording has been removed. That text was authored by you back in 2017, which is why I pinged you for comment. InfiniteNexus (talk) 01:58, 24 January 2024 (UTC)[reply]
Really not sure how that's contentious. It's documenting how the term is used, because it is often used that way, even if this it not the way BOTPOL defines it. Headbomb {t · c · p · b}04:49, 24 January 2024 (UTC)[reply]
Hi. Where did the discussion determining the need for a merge of those WikiProject talk page templates take place? I would like to propose a moratorium there if appropriate so no other proposal flooding watchlists is approved for a while after this one ends. Regards, Super Dromaeosaurus (talk) 17:53, 18 January 2024 (UTC)[reply]
So... all of this is for the merge to be actually only partial? Alright.
This morning I saw this other edit [11]. Frankly it's starting to get annoying. It is clear this is because the two WikiProject templates had different class ratings. But this happened because MilHistBot changed the rating from stub to start [12]. Why don't you WikiProject talk page template people make sure to synchronise things to avoid situations like these to happen before putting forward such a massive thing? Super Dromaeosaurus (talk) 10:21, 19 January 2024 (UTC)[reply]
Super Dromaeosaurus, WPMILHIST is one WikiProject. I ha e no say over how they decide to rate their articles. All I can see is that there was a conflicting class and so my bot decided not to choose either rating. — Qwerfjkltalk15:01, 19 January 2024 (UTC)[reply]
I see an inline citation within a website that links to the wrong page of the website. When I try to change just that one citation, it replaces every citation coming from that website with the new one. How do I limit the change to just a single reference? --EO1912 (talk) 13:18, 21 January 2024 (UTC)[reply]
Ah, I think this referred to the url in the DBI template, which was based on incorrect template documentation. It (the article) was corrected in a subsequent edit. Andy02124 (talk) 16:55, 21 January 2024 (UTC)[reply]
Question from Herekeeprook (08:23, 22 January 2024)
Here's your quick overview of what has been happening around Wikidata over the last week. Translations are available.
Discussions
New request for comments: Domain name as data (Summary: How should Wikidata store the domain name associated with an item? There are many properties for URLs, but a domain name is a different value.)
PLW 2024: Provenance loves Wiki - Fri. 12th - Sun. 14th January. If you missed the event, catch up by reading the slides, Notes and watching the recordings on the Project page
Next: Linked Open Data in Heritage Workshop > Jan. 23rd, 13:00 - 15:00 CET. If you are in the Maastricht University Faculty and want to know enhance heritage research, improve data management, connectivity and visualisation, register for the Workshop.
AskWikidata: Natural language queries to Wikidata, a naive prototype created by Senior Software Engineer for Wikidata, Robert Timm. Want to try? (Google Colab)
IP Masking: We are continuing to adapt Wikibase to the upcoming IP Masking feature. We worked on hiding warnings about IP addresses being saved when they don’t apply (phab:T353807, phab:T352006) and creating temporary accounts when editing (phab:T354730)
Wikibase REST API:
We continued working on the ability to get a sitelink for a given site (phab:T344039)
We started working on the ability to remove a sitelink for a given wiki (phab:T344685)
We worked on fixing a bug where the REST API PUT request does not handle statement on Items with lowercase statement IDs (phab:T352644)
mul language code: We did user testing to find any remaining issue before release
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Problems
A bug in UploadWizard prevented linking to the userpage of the uploader when uploading. It has now been fixed. [13]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 23 January. It will be on non-Wikipedia wikis and some Wikipedias from 24 January. It will be on all wikis from 25 January (calendar). [14][15]
Question from Prathm.Shinde09 (04:29, 25 January 2024)
Hi, How do i add a description to Vinayak Pai.jpg image? Vinayak Pai is currently the Managing director and CEO of Tata Projects Limited, a leading sustainable technology-led engineering, procurement, construction (EPC) company in India. --Prathm.Shinde09 (talk) 04:29, 25 January 2024 (UTC)[reply]
Please Re-list CFD section that was closed with no real discussion
Hi Qwerfjkl. I just discovered that Category:Native American people from the San Francisco Bay Area, which I created a while back, had been listed for merging at CFD. For some reason the alert banner for my talk page did not show up on pages I was editing until a few hours ago, so I only learned of the CFD shortly after you had closed it - after just 7 days, and with only ONE editor commenting at all (a pro forma "Merge per nom" in support of merging). It was readily apparent that neither editor has any actual familiarity with the subject area - so I would dearly like to have the opportunity to make the case for keeping the category.
Anomalous+0, please give a valid rationale for why it should be kept. There is no rush; the category can always be restored. I am happy to reopen the discussion if you give a reason why it should be kept. — Qwerfjkltalk16:00, 25 January 2024 (UTC)[reply]
Hi again, Qwerfjkl. I just discovered to my dismay that the Category in question was deleted a few hours ago. I unfortunately construed your reply to mean that you were gonna hold off putting it into the queue for merging long enough for me to put together a halfway decent explanation/rationale for keeping it. (Which took me longer than expected due to some urgent family issues I needed to attend to.) I've asked the deleting admin to reverse the deletion if possible, so I can avoid having to go thru the whole bothersome process of Deletion Review.
In any event, I guess I may as well go ahead and share what I put together for you:
I thought the easist way to approach this would be simply to share a somewhat random assortment of links for online articles, etc. that discuss one or another aspect of the San Francisco Bay Area's Native American community. Most of these invoke the "SF Bay Area" right in the headline. (FYI: Simply put, the SF Bay Area encompasses all the counties in the North Bay, the South Bay, and the East Bay, as they are known.)
I thought I'd start with something from right here on Wikipedia:
Ohlone#Indian_People_Organizing_for_Change Indian People Organizing for Change (IPOC) is a community-based organization in the San Francisco Bay Area. Its members, including Ohlone tribal members and conservation activists, work together in order to accomplish social and environmental justice within the Bay Area American Indian community.
Muwekma Ohlone Tribe
http://www.muwekma.org/ The present-day Muwekma Ohlone Tribe is comprised of surviving American Indian lineages aboriginal to the San Francisco Bay region who trace their ancestry through the Missions Dolores, Santa Clara, and San Jose.
American Indian Cultural District of San Francisco - Facebook
https://www.facebook.com/AmericanIndianCulturalDistrict American Indian Cultural District of San Francisco, California
The purpose of the American Indian Cultural District is to honor and celebrate the San Francisco Bay Area Native American Community's culture, history, and contributions.
Bay Area American Indian Two-Spirits (BAAITS) exists to restore and recover the role of Two-Spirit people within the American Indian/First Nations community...
https://www.baaits.org
I should also mention that I listen regularly to a weekly radio program from a station in Berkeley called "Bay Native Circle", which is produced by and for Native Americans in the SF Bay Area.
Lastly, I've just discovered that we also have a Category:Native Americans in the San Francisco Bay Area, which further validates the existence of Category:Native American people from the San Francisco Bay Area and should be added as a parent cat.
Honestly, I think what I've presented here should be sufficient for you to change your close on this to "Full KEEP". At the very least, it's quite certainly a "No concensus KEEP".
Although everyone is welcome to contribute to Wikipedia, the introduction of inappropriate pages, such as Draft:Aruba Sucks, is considered vandalism and is prohibited. If you would like to experiment, please use the sandbox. Repeated vandalism may result in the loss of editing privileges. Under section G3 of the criteria for speedy deletion, the page has been nominated for deletion.
If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. Joyous!Noise!14:24, 25 January 2024 (UTC)[reply]
Hello! After a short break I'm back on Wikipedia. (Suffered some days from the flu.) Just wanted to let you know that I'm still working on localizing strings for your bot in my community (have around 20 left) and I will report back when I'm finished. Hope you have a good time! :) - Klein Muçi (talk) 13:56, 26 January 2024 (UTC)[reply]
Qwerfjkl, I am tracking the many bot updates you are doing, using this particular campaign: Implementing WP:PIQA (Task 26).
While the addition of the banner shell is helpful, I see that you have been deleting the param "listas" without replacement. That parameter helps ensure that researchers can find the valuable associated pages whose names do not start with the name of the fraternity. For example, the List of Sigma Alpha Epsilon chapters has a listas param of "listas=Sigma Alpha Epsilon chapters". We've not entered a campaign to rename all of these, (lists of chapters, lists of notable members, and a few others) and perhaps that is warranted. But for now, the listas param is essential to allow these pages to pop up as visible options when someone searches for that fraternity name. Would you adjust this?
You've also delete the param "class=list" from our specific Project listing (Fraternities and Sororities). In one case I noted it was bumped elsewhere within the shell, which is fine, but would you confirm that that second line has been added, and not lost? I only recently noticed the addition as a second line within the shell, and thought it may be missing from other locations. Jax MN (talk) 21:12, 26 January 2024 (UTC)[reply]
[16] The bot acted correctly on that page. The listas is only required once, and so the bot is moving it to the banner shell and out of the separate banners. It is also correct to move |class=list as that was moved into the banner shell, which is the whole benefit of PIQA — Martin (MSGJ · talk) 22:35, 26 January 2024 (UTC)[reply]
I will continue to review these pages for any syntax problems. I scanned several dozen, after reading your request here, and only found a few instances where our original code had neglected to add a LISTAS param, but where it would have been useful. I've subsequently added it. I will respond further if I find any errors. Thanks for engaging on this item. Jax MN (talk) 23:31, 26 January 2024 (UTC)[reply]
Don't hesitate to ask if you have any concerns. But everything looks good from my point of view at the moment — Martin (MSGJ · talk) 17:09, 27 January 2024 (UTC)[reply]
In this edit the Qwerfjkl bot has apparently duplicated a corrupt WikiProject Crime and Criminal Biography banner on Talk:Long Arm of the Law (film), when it should have merged the two version of WikiProject Crime [and Criminal Biography] banners or simply not done anything with the second corrupt and invalid banner syntax. Looks like it tried to do too many things and became confused. This should have been flagged as a corrupt banner shell. - Cameron Dewe (talk) 11:13, 29 January 2024 (UTC)[reply]