This is a page for requesting tasks to be done by bots per the bot policy. This is an appropriate place to put ideas for uncontroversial bot tasks, to get early feedback on ideas for bot tasks (controversial or not), and to seek bot operators for bot tasks. Consensus-building discussions requiring large community input (such as request for comments) should normally be held at WP:VPPROP or other relevant pages (such as a WikiProject's talk page).

You can check the "Commonly Requested Bots" box above to see if a suitable bot already exists for the task you have in mind. If you have a question about a particular bot, contact the bot operator directly via their talk page or the bot's talk page. If a bot is acting improperly, follow the guidance outlined in WP:BOTISSUE. For broader issues and general discussion about bots, see the bot noticeboard.

Before making a request, please see the list of frequently denied bots, either because they are too complicated to program, or do not have consensus from the Wikipedia community. If you are requesting that a template (such as a WikiProject banner) is added to all pages in a particular category, please be careful to check the category tree for any unwanted subcategories. It is best to give a complete list of categories that should be worked through individually, rather than one category to be analyzed recursively (see example difference).

Alternatives to bot requests

Note to bot operators: The {{BOTREQ}} template can be used to give common responses, and make it easier to keep track of the task's current status. If you complete a request, note that you did with {{BOTREQ|done}}, and archive the request after a few days (WP:1CA is useful here).


Please add your bot requests to the bottom of this page.
Make a new request
# Bot request Status 💬 👥 🙋 Last editor 🕒 (UTC) 🤖 Last botop editor 🕒 (UTC)
1 Date ranges for noticeboard archives 6 5 Wikiwerner 2024-02-24 12:50 Primefac 2023-11-12 08:10
2 Categorizing ACM Fellows by Year BRFA filed 3 2 Frostly 2024-02-04 03:45
3 Add articles under the the following categories and subcategories to Wikiproject 6 4 GoingBatty 2024-01-30 21:06 GoingBatty 2024-01-30 21:06
4 Backlog drive leaderboard updates Y Done 3 2 ARandomName123 2024-02-03 18:12
5 Bot request for Korean hangul text  Done 5 3 Primefac 2024-02-06 12:54 Primefac 2024-02-06 12:54
6 Bot to automatically revert date change vandalism 15 5 Geardona 2024-02-06 17:23 Primefac 2024-02-06 13:49
7 Google cache  Done 2 1 GreenC 2024-02-11 16:38
8 ID pages needing infoboxes 21 5 J04n 2024-02-24 18:33 GoingBatty 2024-02-06 18:37
9 Question or another bot request for Korean hangul text 13 8 172.56.232.234 2024-02-29 22:16 Primefac 2024-02-29 16:40
10 Copyvio bot 3 2 Novem Linguae 2024-02-07 01:41
11 Using coordinates on Wikidata BRFA filed 2 2 GoingBatty 2024-02-07 14:13 GoingBatty 2024-02-07 14:13
12 Protection padlock bot 5 3 Geardona 2024-02-07 15:13 Primefac 2024-02-07 14:20
13 Replacing invisible space characters in short description templates BRFA filed 6 3 GoingBatty 2024-03-01 21:14 GoingBatty 2024-03-01 21:14
14 Fixing broken links to talk page discussions 12 4 Kanashimi 2024-02-26 06:22 Usernamekiran 2024-02-18 21:54
15 Proxy Blocking Bot 3 3 Primefac 2024-02-19 18:49 Primefac 2024-02-19 18:49
16 Notifying AfC acceptors an article gets AfDed 3 3 Novem Linguae 2024-02-22 06:27
17 Discussion at Wikipedia talk:Teahouse § Bot inoperable 1 1 Rotideypoc41352 2024-02-23 02:11
18 Bot request Y Done 5 3 GoingBatty 2024-03-01 03:55 GoingBatty 2024-03-01 03:55
19 To add categories based on article's listing in a third page 8 3 Wikiwerner 2024-03-16 17:40 GoingBatty 2024-03-01 08:10
20 Toolforge tool/bot to send email notifications 1 1 Primefac 2024-03-04 12:12 Primefac 2024-03-04 12:12
21 Implementing the outcome of Wikipedia talk:Naming conventions (television)#Follow-up RfC on TV season article titles BRFA filed 16 7 Alex 21 2024-03-27 20:18 Primefac 2024-03-27 12:55
22 Bot to mass-undo edits & pagemoves 3 2 A smart kitten 2024-03-07 15:36
23 Auto-WP:NAVNOREDIRECT Declined Not a good task for a bot. 7 5 Certes 2024-03-16 20:53 Primefac 2024-03-13 18:37
24 Bot to add uncategorized tag to untagged uncategorized pages Y Done 3 3 GoingBatty 2024-03-23 03:43 GoingBatty 2024-03-23 03:43
25 Mass changes needed for retirement of Drug Information Portal 6 4 WhatamIdoing 2024-03-13 17:40
26 Remove NYTimes tracking parameters  Done 12 5 Primefac 2024-03-27 14:17 Primefac 2024-03-27 14:17
27 NFL Draft move downcasing cleanup BRFA filed 22 4 Bsoyka 2024-03-23 02:55 Primefac 2024-03-18 10:12
28 Bot to clean up wikiproject templates 8 2 Cocobb8 2024-03-24 15:05 GoingBatty 2024-03-23 19:12
29 Update WP: maintaince pages 1 1 OrdinaryGiraffe 2024-03-21 23:43
Legend
  • In the last hour
  • In the last day
  • In the last week
  • In the last month
  • More than one month
Manual settings
When exceptions occur,
please check the setting first.



Date ranges for noticeboard archives edit

This seems uncontroversial.

It would be pretty cool if some kind bot could go through the pre-current (should never change) archives of the boards listed in the dramaboard archivebox series, extract the earliest and latest timestamps, truncate them to dates, and use those dates to annotate the links somehow. Inactive archives at time of writing are:

User story: I was recently trying to find an archived conversation from a few months ago, and the best tools I had available were a scattershot "tap an archive number, wait for the entire page to load, check top and bottom timestamps" and "search archives for exact string matched date". Improved navigability gained from annotating the archive links with date ranges should save people time.

Implementation ideas: The quickest implementation would just be a plaintext date range edited onto the archive list pages linked above. A further step could be to add a |date-span= (or similar) to {{Administrators' noticeboard navbox all}} which, if present, would display the date range of comments posted at the top of the page itself, so the information is available both on the archive page and the index of archives. The most elegant, stupid, and expensive implementation would be to add {{shortdesc}} to all the archives, set the |1= to the date range, and convert the indices to use {{annotated link}}.

Anyway though: Anyway though the first step is getting the date ranges. Maybe this is already in a report somewhere? Folly Mox (talk) 18:30, 11 November 2023 (UTC)Reply

@Folly Mox, I suspect you'd need consensus to go through with this. Perhaps trying asking at those noticeboards first? — Qwerfjkltalk 19:06, 11 November 2023 (UTC)Reply
Oh right I tacked on all those expanded scope ideas in the process of making the edit. Folly Mox (talk) 20:22, 11 November 2023 (UTC)Reply
Just noting, an Index of some variety would probably be easier than going through the thousands of archives and amending them. Primefac (talk) 08:10, 12 November 2023 (UTC)Reply
Yep. A user script could be useful for displaying date ranges without the need for edits. — Frostly (talk) 10:04, 7 January 2024 (UTC)Reply
The lists mentioned are generated by Template:Archive list. Could we change it's module to show the date ranges? Wikiwerner (talk) 12:50, 24 February 2024 (UTC)Reply

Categorizing ACM Fellows by Year edit

Right now, there is a category "Category:Fellows of the Association for Computing Machinery" - which is added to all ACM Fellows. I created a bunch of categories "Category:202x Fellows of the Association for Computing Machinery" as subcategories of the main category to organize these by year. The recepients are already organised by year in this page.

  1. Go through each section of the page (which corresponds to a certain year).
  2. Foreach blue linked article in that section add the correct year-specific category "Category:202x Fellows of the Association for Computing Machinery" to the article.
  3. After all sections are done, remove the generic "Category:Fellows of the Association for Computing Machinery" from all the linked articles since they are now living under a subcategory.

KNivedat (talk) 18:37, 26 January 2024 (UTC)Reply

KNivedat,   Coding...— Frostly (talk) 18:37, 27 January 2024 (UTC)Reply
@KNivedat,   BRFA filed— Frostly (talk) 03:45, 4 February 2024 (UTC)Reply

Add articles under the the following categories and subcategories to Wikiproject edit

I want to add the articles under the following categories+subcategories to wikiproject: Indian caste system. Is this a good request for a bot?

Category:Dalit (42)
Category:Dalit literature (19)
Category:Dalit politics (61)
Category:Navayana Buddhists (3)
Category:Ambedkarite political parties (22)
Category:Satnami (5)
Category:Paraiyar leaders (3)
Category:Balmiki (4)
Category:Adivasi (39)
Category:Caste system in India (67)
Category:Anti-caste movements (43)
Category:Scheduled Tribes of India (179)

Miximon (talk) 19:48, 30 January 2024 (UTC)Reply

Probably not; humans will need to add the WikiProject templates based on context. I picked a couple of articles at random from the categories, and Giraudpuri and Guru Balakdas, in Category:Satnami, do not appear to have anything to do with that WikiProject. (edited to add: I believe that the OP is referring to {{WikiProject Indian caste system}} and the associated WikiProject.) – Jonesey95 (talk) 20:10, 30 January 2024 (UTC)Reply
I would also make the argument that other than the Scheduled Tribes cat, none of these are heavily populated - a quick AWB run would probably be both faster and more accurate (since there would be human oversight). Primefac (talk) 20:15, 30 January 2024 (UTC)Reply
Even the big category will need human oversight; I don't see a reference to caste in Tani people, which is in that scheduled tribes category. – Jonesey95 (talk) 20:21, 30 January 2024 (UTC)Reply
Just adding context to clarify - Scheduled castes and tribes are Govt of India's list of castes and tribes that are recognized for affirmative action because of historic discrimination - Caste system in India#Recognition Miximon (talk) 20:29, 30 January 2024 (UTC)Reply
@Miximon: If you want to post a list of pages (not categories) on the WikiProject's talk page, and there's consensus to tag each of them, I will be happy to have my bot tag them. GoingBatty (talk) 21:06, 30 January 2024 (UTC)Reply

Backlog drive leaderboard updates edit

Hi, is there a bot that can automatically update the leaderboard for the unreferenced articles backlog drive? Ideally, it would count the number of edit summaries made by each participant with "feb24" (not case-sensistive) to unique articles. Then, it would update the "Points from references" column in the leaderboard with that number. The rest of the leaderboard doesn't need to be updated by the bot, as the points from reviews is simpler to update, and the total points is automatically provided by a template. There's a bit of prior discussion at the talk page. Thanks! ARandomName123 (talk)Ping me! 23:14, 1 February 2024 (UTC)Reply

I created a simple scraper which I plan to use daily to update the leaderboard. I don't think it's a very good solution, so if bot experts want to help, it would still be greatly appreciated ;) Broc (talk) 21:32, 2 February 2024 (UTC)Reply
 Y Done. Bot created based on script above. See User:BaranBOT/FEB24DriveLeaderboard. ARandomName123 (talk)Ping me! 18:12, 3 February 2024 (UTC)Reply

Bot request for Korean hangul text edit

Per the discussion at Wikipedia talk:Manual of Style/Korea-related articles#About adding a link to each hangul syllable using Template:Linktext, I am submitting this bot request. Please perform the following.

  1. Check if Template:Linktext only contains [ ]?[0-9가-힣][ ]? in each parameter.
  2. If so, remove Template:Linktext and |, but retain the text entered as parameters (including space characters before and/or after [0-9가-힣]).
  3. If not (that is, if Template:Linktext contains (1) any character other than [0-9가-힣], or (2) two or more adjacent [0-9가-힣] in at least one parameter), leave it as-is.

The following examples would help you understand this request.

  • Cases that should be changed
    • {{linktext|국|립|중|앙|도|서|관}}국립중앙도서관 (currently found in National Library of Korea)
    • {{Linktext|수|도|권|제|1|순|환|고|속|도|로}}수도권제1순환고속도로 (currently found in Capital Region First Ring Expressway)
    • {{linktext|새|터|데|이| 나|이|트| 라|이|브| 코|리|아|}}새터데이 나이트 라이브 코리아 (space characters have to be retained; currently found in Saturday Night Live Korea)
    • {{linktext|구|름|은}} {{linktext|흘|러|가|도}}구름은 흘러가도 ((added this example just in case) a space character between two instances of Template:Linktext has to be retained; currently found in Even the Clouds Are Drifting)
  • Cases that should NOT be changed
    • {{linktext|中|文|維|基|百|科}} (contains any character other than [0-9가-힣]; currently found in Chinese Wikipedia)
    • {{linktext|새|마을|호}} (contains two or more adjacent [0-9가-힣] in at least one parameter; currently found in Saemaeul-ho)

172.56.232.167 (talk) 00:24, 2 February 2024 (UTC)Reply

The regex will need to be a bit more complex than what is described above, but this should be doable. Let me do some small-scale testing and get back to you. Primefac (talk) 12:30, 2 February 2024 (UTC)Reply
  BRFA filed. Primefac (talk) 21:34, 2 February 2024 (UTC)Reply
Thank you for running your bot. I greatly appreciate it.
But can you please also remove them in the Draft namespace? There are currently 86 pages containing them (see this). They can be moved to the main (article) namespace at any time. 172.56.232.239 (talk) 05:46, 5 February 2024 (UTC)Reply
Didn't think about draft space, seems reasonably uncontroversial
  Done. Primefac (talk) 12:54, 6 February 2024 (UTC)Reply

Bot to automatically revert date change vandalism edit

Hi, I want to create a bot that automatically reverts obvious date change vandalism. For example:

"James H. (born 26 December 2002)"
And then a vandal comes and changes it to:
"James H. (born 29 December 2002)"

And the goal of the bot is to revert these changes as accurately as possible. And here's how it's gonna work:

A bot sees that someone changed the birth date. The bot looks up the name of the person on wikidata. If the person appears on wikidata, The bot searches for his birth date on his wikidata page. And if the birth date written on wikidata is different than the date the vandal changed it to, the bot automatically revert these changes. I hope this bot can be coded for me. It seems like a great idea for a bot. 93.173.38.154 (talk) 11:28, 5 February 2024 (UTC) Very minor formatting changes made for readability. Primefac (talk) 12:58, 6 February 2024 (UTC)Reply

This might require a discussion to get consensus rather than being an automatic "do now". I would check that the Wikidata matches the old date, rather than just differing from the new one. Bear in mind that Wikidata also has vandalism and good-faith errors, so (with all due respect to the IP proposer) we might want the bot to revert non-autoconfirmed editors only. Certes (talk) 12:07, 5 February 2024 (UTC)Reply
This might be something that an edit filter could be able to accomplish, just disallowing changes like that. Geardona (talk to me?) 12:27, 5 February 2024 (UTC)Reply
  • Minor changes to numbers are depressingly common. I have been combating a mobile IP from Italy for over 6 months, who modifies incorrectly the heights of buildings, in 100s and 1000s of articles. Might be game or competition. I agree watching birth/death date changes is a good idea. I have some ideas how to do this, but it gets involved, it's not easy. -- GreenC 15:22, 5 February 2024 (UTC)Reply
  • Not sure if this is possible even remotely, but a bot to unaccept any change like these, pushing them onto pending changes, even if the page is not protected as such, just for new/unregistered users, might solve the immediate problem of false info presented to readers. Geardona (talk to me?) 15:26, 5 February 2024 (UTC)Reply
  • I like the gist of the proposal but not the substance. If we're going to revert number vandalism (and I would say everything from DOB to height/weight to number of albums sold, etc) it should just be done, without checking WD (which might be wrong or nonexistent anyway). If a number is being changed without a reference, it's likely to be vandalism. Basically ClueBot NG but specifically for numbers. It would need broader consensus to get implemented, though (regardless of how the bot is set up). Primefac (talk) 12:58, 6 February 2024 (UTC)Reply
    I would say that this seems more possible with a edit filter, so it should be proposed there (edit filter talk page). Then see what they think. Geardona (talk to me?) 13:11, 6 February 2024 (UTC)Reply
    That would certainly catch a lot of petty vandalism, such as changing the lead of 123 to begin "420 is..", but it might have many false positives. For example, good-faith editors regularly update sporting records for players and teams after each match, without waiting for some newspaper to mention that Smith has now played 42 matches rather than 41. Certes (talk) 13:34, 6 February 2024 (UTC)Reply
    Potentially limiting it to just dates in the past (1 year +) would alleviate false positives? Maybe also limiting it to large number changes, would stop good faith false positives. Geardona (talk to me?) 13:38, 6 February 2024 (UTC)Reply
    Oh, don't take my suggestion as what must be, just throwing out an idea that I feel is better than trusting WD. Whether edit filter or bot, I suspect that the reverts would be limited to IPs and non-AC users. Primefac (talk) 13:49, 6 February 2024 (UTC)Reply
    Potentially even having it set to revoke AC status would really solve the problem, AC is not that hard to get. Geardona (talk to me?) 13:53, 6 February 2024 (UTC)Reply
    That's an interesting idea but I don't think we have a precedent for a "Robocop" bot which removes permissions and it would need at least an RfC. Getting AC for the first time is easy, but we would need to think about how affected editors would recover AC - permission request? Certes (talk) 14:05, 6 February 2024 (UTC)Reply
    To my knowledge some of the high-power filters can revoke AC. Geardona (talk to me?) 14:07, 6 February 2024 (UTC)Reply
    From Wikipedia:EFBASICS "The strongest setting is disallow. In this case, the edit is rejected, and the user will see a customizable message. A link is provided for reporting false positives. It is also possible to have a user's autoconfirmed status revoked if a user trips the filter." Geardona (talk to me?) 17:23, 6 February 2024 (UTC)Reply

Google cache edit

Google cache is shutting down, it is making the news. We have 5,000 pages on Enwiki. It is at WP:URLREQ#Google_cache. Thanks. -- GreenC 15:26, 5 February 2024 (UTC)Reply

  Done -- GreenC 16:38, 11 February 2024 (UTC)Reply

ID pages needing infoboxes edit

Identify pages with Template:WikiProject Albums in their talk page but not Template:Infobox album on their main page and add |needs-infobox=yes to them. Please and thank you, J04n(talk page) 15:24, 6 February 2024 (UTC)Reply

Question, what about disambiguation or redirect pages, do they require the infobox? Would this be a 1 time run or a ongoing thing, if it is 1 time I could try to figure out some AWB or JWB regex to get this partly done. (given the pages a bot would be more efficient in my opinion)   Thanks Geardona (talk to me?) 15:37, 6 February 2024 (UTC)Reply
Thanks for the quick response,disambiguation or redirect pages don't need them, if they can be filtered out all the better. I suppose continuous is better, not sure of the logistics. J04n(talk page) 16:07, 6 February 2024 (UTC)Reply
I am not a bot programer myself, but it seems possible, (405683 pages) would need to be checked, and thats way too many for 1 or 2 people to check manually in any reasonable time (even with AWB). Geardona (talk to me?) 17:20, 6 February 2024 (UTC)Reply
Geardona, J04n, according to my PetScan query, 29,831 results. I could run my bot on these pages. — Qwerfjkltalk 17:59, 6 February 2024 (UTC)Reply
Looking at the results though, seems there are quite a few false positives. — Qwerfjkltalk 18:01, 6 February 2024 (UTC)Reply
Less amazing, how did it fail? Geardona (talk to me?) 18:02, 6 February 2024 (UTC)Reply
Geardona, because whilst they are in WikiProject Albums, quite a few of the articles likely don't need an infobox e.g. Grammy Award for Best Comedy Album. — Qwerfjkltalk 18:04, 6 February 2024 (UTC)Reply
Im not sure how to filter those out, Wikipedia:CONTEXTBOT is rearing its ugly head. Might need to be done manually, at least the list is a tiny bit shorter. Geardona (talk to me?) 18:06, 6 February 2024 (UTC)Reply
Most of those seem to be redirects. — Qwerfjkltalk 18:02, 6 February 2024 (UTC)Reply
I see a "redirects yes/no" setting, would that fix it or am I missing something? Geardona (talk to me?) 18:04, 6 February 2024 (UTC)Reply
Amazing, I thought that something like this would exist, maybe post a notice with the albums project talk page, wait a day or 2 and then start. (Not sure if a BRFA would be needed here?) Geardona (talk to me?) 18:01, 6 February 2024 (UTC)Reply
Yeah, the majority seem to be false positives. Can redirects be filtered out? J04n(talk page) 18:04, 6 February 2024 (UTC)Reply
J04n, I did so in my second query. Sorry if that was unclear. — Qwerfjkltalk 18:14, 6 February 2024 (UTC)Reply
Very cool, I don't mind filtering out other false positives by hand. Thank you so much! J04n(talk page) 18:18, 6 February 2024 (UTC)Reply
@J04n: Is there consensus that all articles should have an infobox? When creating the BRFA, it would be good to link to that consensus (whether it's a conversation or an albums style guide). Thanks! GoingBatty (talk) 18:37, 6 February 2024 (UTC)Reply
I'll start a conversation, thanks J04n(talk page) 18:49, 6 February 2024 (UTC)Reply
I reached out to the project, another thought I had was maybe have the bot look for any infobox template not just album. This would further reduce false positives. J04n(talk page) 19:09, 6 February 2024 (UTC)Reply
Rather than looking for the WikiProject template, you could work through yyyy albums, i.e. the subcategories of Albums by year. That might miss a few pages but should produce dramatically fewer false positives. Certes (talk) 22:21, 6 February 2024 (UTC)Reply
That's a great idea, appreciate folks putting thought into this. J04n(talk page) 00:39, 7 February 2024 (UTC)Reply

I started a discussion at Wikipedia talk:WikiProject Albums#Bot to help identify album pages missing infoboxes, which generated pretty much no interest one way or the other. I would like to go on with this as a one-time sweep of pages in the subcategories of Albums by year that do not have an infobox, if redirects could be filtered out it would be a big help. Can this be done? Thanks! J04n(talk page) 18:33, 24 February 2024 (UTC)Reply

Question or another bot request for Korean hangul text edit

This is also related to the #Bot request for Korean hangul text above.

Any instance of Template:Linktext in Korean personal names should also be removed.

Korean personal names are usually in the "one-syllable surname + two-syllable given name" format (e.g. 홍길동 – surname 홍, given name 길동), so some people added Linktext like this: {{linktext|홍|길동}}. There are currently 726 pages containing such instances of Linktext (see this), and these are mostly—but not always—personal names.

In this case, you should not look for any space characters and [0-9]. You only need to look for \{\{[Ll]inktext\|[가-힣]\|[가-힣][가-힣]\|?\}\} (that is {{[Ll]inktext|[가-힣]|[가-힣][가-힣]|?}} without the backslashes), and remove Template:Linktext and |, but retain the text entered as parameters (i.e. change {{linktext|홍|길동}} to 홍길동).

Here are my questions:

  1. Is it possible to remove such instances of Linktext just from personal names?
    1. If so, please perform the bot removal.
    2. If not, if I provide pages that should not be affected by the bot removal, would that work? For example, a case like {{linktext|집|으로}} (found in The Way Home (2002 film)) should not be affected.

172.56.232.179 (talk) 21:27, 6 February 2024 (UTC)Reply

Note that "no linktext in personal names (that is, do not add any kind of link to a personal name, including other forms of segmentations such as 가|나다)" was also part of the discussion. Look under "For personal names (including pseudonyms such as pen names, stage names, etc.), no links should be added." in Wikipedia talk:Manual of Style/Korea-related articles#About adding a link to each hangul syllable using Template:Linktext. 172.56.232.188 (talk) 04:13, 8 February 2024 (UTC)Reply
I am slightly concerned about the CONTEXTBOT issues presented. Primefac (talk) 12:43, 8 February 2024 (UTC)Reply
I manually checked the search results and prepared a list of pages (total 11) where \{\{[Ll]inktext\|[가-힣]\|[가-힣][가-힣]\|?\}\} is not a personal name. (As of 02:02, 23 February 2024 (UTC), this list still remains the same)
But you don't need to add these as exceptions when running your bot because these can be manually re-added/reverted after the bot runs.
Is the task doable now? If so, please perform the bot removal. 172.56.232.101 (talk) 20:24, 8 February 2024 (UTC)Reply
FYI you can just write {{tld|linktext|꽃|부리}} --> {{linktext|꽃|부리}} without all the nowikis. Or to link the template: {{linktext|꽃|부리}} -- GreenC 21:00, 8 February 2024 (UTC)Reply
If you are still concerned about the CONTEXTBOT issue, just don't worry about it. Since there is only a small number of exceptions, and since Linktext has never been a requirement (i.e. any instance of Linktext does not have to be there in the first place), you don't really need to worry about anything. Don't even add those cases as exceptions when running your bot either. 172.56.232.239 (talk) 03:14, 10 February 2024 (UTC)Reply
insource:/\{\{[Ll]inktext\|[가-힣]\|[가-힣]\|[가-힣]\|?\}\}/ also has two. Also, I'm curious if it's necessary to leave something like {{linktext|黄|喜|燦}} behind? Kanashimi (talk) 07:46, 15 February 2024 (UTC)Reply
Nothing was discussed about Chinese characters. 172.56.232.179 (talk) 21:48, 15 February 2024 (UTC)Reply

I don't want to urge anyone, but can anyone please take care of this? I also want to move on. 172.56.232.179 (talk) 21:51, 15 February 2024 (UTC)Reply

Can anyone please take care of this? 172.56.232.239 (talk) 02:02, 23 February 2024 (UTC)Reply

@Primefac Can you please also take care of this? Just don't worry about the CONTEXTBOT issue. It's not really worth worrying in this case. 172.56.232.239 (talk) 14:26, 29 February 2024 (UTC)Reply

Chill. Yes, but chill. Primefac (talk) 16:40, 29 February 2024 (UTC)Reply
Got it.
I didn't mean to urge you. I was just concerned whether this request was getting forgotten. 172.56.232.234 (talk) 22:16, 29 February 2024 (UTC)Reply

Copyvio bot edit

Hello,
I was looking around for something like this, and did not find it, could a bot run a page against earwigs copyvio detector automatically, and flag it for human review if its score is too high? (I am willing to attempt to code this if there is not a glaring issue with it)
  Thanks
Geardona (talk to me?) 22:28, 6 February 2024 (UTC)Reply

Nevermind, I see the village pump thread. Geardona (talk to me?) 00:09, 7 February 2024 (UTC)Reply
You may find User:Novem Linguae/Essays/Copyvio detectors to be a good read. –Novem Linguae (talk) 01:41, 7 February 2024 (UTC)Reply

Using coordinates on Wikidata edit

Category:Articles missing coordinates with coordinates on Wikidata contains 20,245 articles tagged with {{coord missing}}, but they all have coordinates available on Wikidata. Would it be possible for this template to be removed and replaced with {{Coord|display=title}} which will fetch the coordinates from Wikidata? I am not familiar with previous discussion on this, but I have also contacted The Anome for comments — Martin (MSGJ · talk) 09:32, 7 February 2024 (UTC)Reply

@MSGJ and The Anome:   BRFA filed. GoingBatty (talk) 14:13, 7 February 2024 (UTC)Reply

Protection padlock bot edit

Bot to look through the page on the list of protected pages, find ones missing the padlock and add it at the correct level, and to correct the padlock level if needed.   Thanks Geardona (talk to me?) 14:06, 7 February 2024 (UTC)Reply

  Already done by User:MusikBot II. Primefac (talk) 14:20, 7 February 2024 (UTC)Reply
Can we confirm is is still up? Geardona (talk to me?) 15:06, 7 February 2024 (UTC)Reply
It is. You can check its user contribution for the recent edits. – robertsky (talk) 15:11, 7 February 2024 (UTC)Reply
Good, thanks Geardona (talk to me?) 15:13, 7 February 2024 (UTC)Reply

Replacing invisible space characters in short description templates edit

This is a request to replace invisible space characters with regular space characters in {{short description}} templates within articles. As the MOS says, these characters are typically placed inadvertently via copying and pasting, and they can cause problems of various sorts. The task would be to replace invisible nbsp and thinsp characters found within short descriptions in the articles listed at Wikipedia:Database reports/Short descriptions containing invalid space characters.

I am pretty sure this would be a cosmetic task that would need explicit BRFA approval. Fixing the existing 3,000 or so instances of the problem will help us understand the root causes of the problem by identifying how new instances are occurring. I have some regexes that might help at User:Jonesey95/AutoEd/pages.js. – Jonesey95 (talk) 16:30, 8 February 2024 (UTC)Reply

If it's an issue and if there's consensus, I can probably run this. Of course, if these invisible formatting characters are in the "private use area" then AWB will be useless. Primefac (talk) 16:45, 8 February 2024 (UTC)Reply
Thanks, Primefac. This request follows from this discussion. My impression was that a long-standing MOS guideline was consensus enough to remove these characters. – Jonesey95 (talk) 20:39, 10 February 2024 (UTC)Reply
@Primefac: Did you want to submit a BRFA for this, or would you like me to do so? GoingBatty (talk) 04:44, 1 March 2024 (UTC)Reply
Totally forgot about this. Looks like I should be able to make AWB do what I want, so I can handle it. Thanks for the reminder. Primefac (talk) 13:22, 1 March 2024 (UTC)Reply
@Primefac - Thanks! Marking as   BRFA filed so the table at the top of the page is updated. GoingBatty (talk) 21:14, 1 March 2024 (UTC)Reply

Fixing broken links to talk page discussions edit

Links to talk page discussions often break when the discussions are archived by User:Lowercase sigmabot III. Could this bot be configured to replace the links (by linking to archived discussions) instead of breaking them? Jarble (talk) 18:58, 16 February 2024 (UTC)Reply

Jarble, this is not the right place. Ask on the bot operator's talk page. — Qwerfjkltalk 14:02, 17 February 2024 (UTC)Reply
@Jarble: clubot III does this by default. See User:ClueBot III#Keeping linked. —usernamekiran (talk) 21:19, 18 February 2024 (UTC)Reply
@Usernamekiran: Does ClueBot III repair links to discussions that were broken by other bots, including Lowercase sigmabot III? Jarble (talk) 21:40, 18 February 2024 (UTC)Reply
@Jarble: To keep it short, I don't think so. —usernamekiran (talk) 21:54, 18 February 2024 (UTC)Reply
cewbot regularly fixes these types of link errors. If there are any that are not fixed, please let me know and I'll see what's wrong. Kanashimi (talk) 05:37, 19 February 2024 (UTC)Reply
@Kanashimi: I frequently find broken links to sections of talk pages that were archived. Does Cewbot replace these broken links with links to archived talk page discussions? Jarble (talk) 21:48, 19 February 2024 (UTC)Reply
That's what a robot would do. If the robot misses something, you can give me an example and I'll see what's wrong. Kanashimi (talk) 22:41, 19 February 2024 (UTC)Reply
@Kanashimi: For example, I found several broken links to talk page sections on this page. Does this bot not repair broken links from archived discussions? Jarble (talk) 17:32, 25 February 2024 (UTC)Reply
@Jarble The bot works by checking all the links to a specific anchor. There are too many links on this page, can you point out the exact anchor? Thank you. Kanashimi (talk) 03:18, 26 February 2024 (UTC)Reply
@Kanashimi: One of the broken section anchors is at the beginning of this section, but there are probably several others. Jarble (talk) 03:39, 26 February 2024 (UTC)Reply
@Jarble This page will be processed by the bot when it processes all the pages linked to Talk:BTS (band). Kanashimi (talk) 06:22, 26 February 2024 (UTC)Reply

Proxy Blocking Bot edit

This bot is programmed to use a wide range of VPN services; using so, it detects the IP addresses, and then blocks them. This means that a lot of time could be saved. HedgehogLegend (talk) 18:48, 19 February 2024 (UTC)Reply

We already have a proxy blocking bot. * Pppery * it has begun... 18:49, 19 February 2024 (UTC)Reply
Specifically, User:ST47ProxyBot. Primefac (talk) 18:49, 19 February 2024 (UTC)Reply

Notifying AfC acceptors an article gets AfDed edit

Hello, I am wanting to propose the idea of creating a bot that notifies Articles for creation acceptors when an article they accept gets AfDed around 100 days within them accepting it via their talk page. GMH Melbourne (talk) 05:41, 22 February 2024 (UTC)Reply

There is a script called User:Novem Linguae/Scripts/WatchlistAFD.js that automatically adds the AfD pages of your AfC accepts and NPP curations to your watchlist for 6 months. It's really handy because then you can easily keep track of when things are AfD'd and adjust your reviewing accordingly. – DreamRimmer (talk) 06:18, 22 February 2024 (UTC)Reply
I think my user script is broken. I should probably fix it one of these days. –Novem Linguae (talk) 06:27, 22 February 2024 (UTC)Reply

Discussion at Wikipedia talk:Teahouse § Bot inoperable edit

  You are invited to join the discussion at Wikipedia talk:Teahouse § Bot inoperable. Rotideypoc41352 (talk · contribs) 02:11, 23 February 2024 (UTC)Reply

Bot request edit

Would it be possible to get a bot to expand the match report citations at 2023–24 UEFA Europa Conference League qualifying phase and play-off round (Main Path) to stop the article exceeding template size limits? I've tried sandboxing a couple of different ways to try and reduce the number of templates on the page and I think the best (and possibly easiest) way to do so would be to expand the Cite web templates but there are quite a few so it would take a while to do so manually. As an example, <ref>{{cite web |url=https://www.uefa.com/uefaeuropaconferenceleague/match/2038534/ |title=Sutjeska-Cosmos |website=UEFA.com |publisher=Union of European Football Associations |access-date=13 July 2023}}</ref> would become <ref>[https://www.uefa.com/uefaeuropaconferenceleague/match/2038534/ "Sutjeska-Cosmos"]. UEFA.com. Union of European Football Associations. Retrieved 13 July 2023.</ref>

Any help would be much appreciated. Stevie fae Scotland (talk) 12:08, 29 February 2024 (UTC)Reply

If it's just one page, a find/replace (either via AWB or just a text editor) is better than a bot. A bot won't really do anything different than a user. Primefac (talk) 12:30, 29 February 2024 (UTC)Reply
Okay, it should be   Fixed; I did a mass find/replace on the most re-used cite style and everything seems to be showing up now. Primefac (talk) 13:02, 29 February 2024 (UTC)Reply
Thanks Primefac, much appreciated. Stevie fae Scotland (talk) 13:51, 29 February 2024 (UTC)Reply
Marking as  Y Done to update the table at the top of this page. GoingBatty (talk) 03:55, 1 March 2024 (UTC)Reply

To add categories based on article's listing in a third page edit

I wish to add the Category:Banaras Hindu University alumni to all articles listed in List of Banaras Hindu University people. The bot should automatically update/add Category to any article added in the List. This List-Category linker can not only be used across WP:UNI but also other such relations where a list and category exist for same theme. Thank you, User4edits (talk) 04:36, 1 March 2024 (UTC)Reply

@User4edits: The first person in the article is "C. V. Raman, the Nobel Prize winner in Physics in 1930 and Bharat Ratna laureate..." The bot would have to check C. V. Raman and ignore the links to Nobel Prize and Bharat Ratna. Might be easier if all the lists in the article were in the same format (e.g. all tables or all with bullets). GoingBatty (talk) 04:43, 1 March 2024 (UTC)Reply
@GoingBatty would it not be possible to filter only biographical articles? Re-formatting would be tedious for such large article, and will not make the bot a universal use. Thanks, User4edits (talk) 04:59, 1 March 2024 (UTC)Reply
@User4edits: It might be possible, but more challenging when you look at List of Harvard University people#Royalty and nobility where you would also have to filter out the biographical articles from the "Notability" column. GoingBatty (talk) 05:26, 1 March 2024 (UTC)Reply
@GoingBatty That is an issue. However, we can counter this by providing users with two modes -- biographical filter, or columns (formatted lists as Harvard above). Thanks, User4edits (talk) 06:02, 1 March 2024 (UTC)Reply
@User4edits: Another issue that any potential bot owner (i.e. not me) will have to consider is that it won't be appropriate to add "Category:XXXX alumni" to an article if it already has a sub-category (e.g. Category:Harvard University people has 17 subcategories and numerous sub-subcategories). GoingBatty (talk) 08:10, 1 March 2024 (UTC)Reply
@GoingBatty Yes, it will have to skip if any sub category of the main category is already listed. Although in the example you gave, I see Category:Harvard University alumni a sub cat of people. Thanks, User4edits (talk) 04:25, 2 March 2024 (UTC)Reply
The category at the start of this topic has no subcategories, so that is not an issue. AWB's list comparer yields 196 pages that are linked on the list, but are not in the category (plus 146 pages in the category that are not in the list). Filtering out biographical articles can be done by checking whether a category "... births" exists, or by a human. Wikiwerner (talk) 17:40, 16 March 2024 (UTC)Reply

Toolforge tool/bot to send email notifications edit

I've started a tool request about the recent "bots don't trigger email watchlist notifications" change to the backend at VPT (since it's not a botreq) but thought folks here might want to know. Primefac (talk) 12:12, 4 March 2024 (UTC)Reply

Implementing the outcome of Wikipedia talk:Naming conventions (television)#Follow-up RfC on TV season article titles edit

This is a rather big and somewhat complex job. Per the RfC, we need to move all articles on individual TV seasons from, e.g., Loki (season 2) titles to "Loki season 2" titles (get rid of the parens and add a DISPLAYTITLE template to maintain the italicization scheme; and add "| italic_title=no" to the television infobox to avoid a conflict). BD2412 T 01:00, 6 March 2024 (UTC)Reply

@BD2412: thinking about this, but not actively working on it. Per the RfC, this is not a task for blanket removal of brackets as Hawaii Five-0 (2010 TV series, season 10) is supposed to become "Hawaii Five-0 (2010 TV series) season 10". Am I getting this correctly? —usernamekiran (talk) 04:05, 6 March 2024 (UTC)Reply
That is correct. My thinking is that we hold those off to the end. BD2412 T 04:12, 6 March 2024 (UTC)Reply
Apparently this will actually require retooling of the infobox first to avoid clashes, but once that is done, this can roll. BD2412 T 22:22, 7 March 2024 (UTC)Reply
add a DISPLAYTITLE template to maintain the italicization scheme; and add " I think all of this will eventually be handled on the infobox level, so we shouldn't need a multitude of DISPLAYTITLEs (and thus that parameter in the infobox). - Favre1fan93 (talk) 18:47, 9 March 2024 (UTC)Reply
Yes, the infobox sandbox version should be working with the new style. More testing by other editors is of course always appreciated. The display title and italic_title should not be needed to be edited by a bot. Other things mentioned in the follow-up still need bot work. Gonnym (talk) 13:17, 11 March 2024 (UTC)Reply
This is technically two different tasks (first, move, second, cleanup). I'm happy to help out with the second half. Primefac (talk) 13:28, 11 March 2024 (UTC)Reply
For the moves, the complete list of articles to be moved (original and new location) are listed at User:Alex 21/sandbox/NCTV. -- Alex_21 TALK 00:49, 16 March 2024 (UTC)Reply
Just bumping this, to see if any available editors with bots are willing to help out. Cheers.   -- Alex_21 TALK 09:17, 23 March 2024 (UTC)Reply
Alex 21, I can take care of this. (The first part, moving the pages.) — Qwerfjkltalk 15:45, 23 March 2024 (UTC)Reply
@Qwerfjkl Fantastic, thank you! The complete list of articles to be moved are at User:Alex 21/sandbox/NCTV; the former link is the current location, the latter link the location to move to (some of which are already redirects and will require overwriting). Let me know if you have any questions. -- Alex_21 TALK 11:00, 25 March 2024 (UTC)Reply
I suppose I should have mentioned   BRFA filed. — Qwerfjkltalk 16:57, 25 March 2024 (UTC)Reply
Just so as I can hopefully get to the "part two" as quickly as possible after "part one" is done (unless someone else feels like tackling it), my list of things to update after the pages moves are:
  • Add |italic_title=no to the infobox
  • Update talk page archiving to point to the correct location
I seem to be reading from the above that the DISPLAYTITLE issue is being fixed on the backend in the infobox itself, yes? Is there anything else that needs updating? Primefac (talk) 12:37, 26 March 2024 (UTC)Reply
First trial is complete, for the record; extra eyes are always appreciated. Primefac (talk) 12:55, 27 March 2024 (UTC)Reply
No to your first bullet. The infobox handles italics (or at least should if I didn't mess up the code). Once the moves are done Template:Infobox television season/sandbox and Module:Infobox television season name/sandbox2 should be moved to live. Gonnym (talk) 14:16, 27 March 2024 (UTC)Reply
The main update that will need to occur after the page moves will be updating usages of {{Episode list/sublist}} (e.g. from {{Episode list/sublist|American Idol (season 1)}} to {{Episode list/sublist|American Idol season 1}}. This could be done through a bot or AWB, either works; the latter would need a find-and-replace with (\{\{Episode list\/sublist\|).+ to $1{{subst:BASEPAGENAME}} (regex enabled). This was a test edit of exactly that. -- Alex_21 TALK 20:18, 27 March 2024 (UTC)Reply

Bot to mass-undo edits & pagemoves edit

There seems to be (at least a rough) consensus at WP:BOTN#Rollback Proposal to mass-undo at least a set of the edits and pagemoves that were proposed for reversal. I originally said that I would be happy to submit a BRFA to do this myself, but I am no longer personally able to take on this task.

Let me know if there are any queries. All the best, ‍—‍a smart kitten[meow] 18:44, 6 March 2024 (UTC)Reply

Looks like this user changed his name? Kanashimi (talk) 14:25, 7 March 2024 (UTC)Reply
@Kanashimi: Yes, this user is now Renamed user g5s6n3yi8z7g08cs. All the best, ‍—‍a smart kitten[meow] 15:36, 7 March 2024 (UTC)Reply

Auto-WP:NAVNOREDIRECT edit

Could we have a bot to automatically bypass redirects in navboxes? It would simplify part of the WP:POSTMOVE work that page movers have to perform. – Hilst [talk] 00:39, 10 March 2024 (UTC)Reply

Not all redirects in navboxes should be bypassed. WP:NAVNOREDIRECT recommends bypassing redirects which are synonymous with the target but not those which are subtopics or other related topics on which a separate article might be written. In some cases, bypassing everything might create a navbox for Garage Band where all the entries are of the form [[Garage Band|Mike Singer]], [[Garage Band|Obscure Single]], etc. Certes (talk) 11:19, 10 March 2024 (UTC)Reply
  Not a good task for a bot. As indicated above, there are context issues. Primefac (talk) 18:37, 13 March 2024 (UTC)Reply
Alright, thanks. – Hilst [talk] 20:18, 13 March 2024 (UTC)Reply
@Hilst: One could generate a report of existing redirects on navboxes, whether or not filtered by redirects containing {{R from move}}. Then the results can be processed manually. A nice one is Template:Districts of Cambodia: all districts have been renamed from "... District" to "... district". Wikiwerner (talk) 19:49, 16 March 2024 (UTC)Reply
Yes, R from moves should be safe. Districts of Cambodia is one template where a bot or other process to bypass redirects automatically would be helpful. There may be other categories/templates of redirect which can also be bypassed safely. Others such as R from misspelling look tempting but might be mislinks where a topic with no article has its title redirected to an unrelated topic with a similar spelling. Certes (talk) 20:53, 16 March 2024 (UTC)Reply
And those navboxes should go straight to WP:TFD for being pointless. Gonnym (talk) 19:17, 13 March 2024 (UTC)Reply

Bot to add uncategorized tag to untagged uncategorized pages edit

Could we have a bot to automatically add the Template:Uncategorized tag to untagged uncategorized pages? BlueberryIntoTheWild (talk) 06:29, 10 March 2024 (UTC)Reply

It's been discussed previously at Wikipedia talk:New pages patrol/Coordination#Reviewing backlog. – DreamRimmer (talk) 07:10, 10 March 2024 (UTC)Reply
@BlueberryIntoTheWild:  Y Done I already have BattyBot 55 to do this, and I last ran it on March 21. GoingBatty (talk) 03:43, 23 March 2024 (UTC)Reply

Mass changes needed for retirement of Drug Information Portal edit

(I am contacting WP:BOTREQ at the suggestion of Andy Mabbett)

The National Library of Medicine's Drug Information Portal has been retired, with all information moved to the Library's PubChem database. I think all the links to the Drug Information Portal should be updated to the corresponding article in PubChem. I suspect that someone can set up a bot to do this, but I don't know how. Perhaps someone can point me to instructions to do this or turn this over to someone who already knows how? — HowardBGolden (talk) 20:40, 12 March 2024 (UTC)Reply

For example: Here's an example of a change I made manually:

Synopsis:

"druginfo" -> "pubchem/ncbi"
"drugportal/name" -> "compound"
"Drug Information Portal" -> "PubChem"
"charcoal" -> "Activated%20Charcoal#section=Drug-and-Medication-Information"


BEFORE

* {{cite web |title=Activated charcoal |url=https://druginfo.nlm.nih.gov/drugportal/name/charcoal |work=Drug Information Portal |publisher=U.S. National Library of Medicine}}

AFTER

* {{cite web |title=Activated charcoal |url=https://pubchem.ncbi.nlm.nih.gov/compound/Activated%20Charcoal#section=Drug-and-Medication-Information |work=PubChem |publisher=U.S. National Library of Medicine}}

HowardBGolden (talk) 22:25, 12 March 2024 (UTC)Reply

@HowardBGolden: Could WP:URLREQ do this more efficiently than a new bot? Certes (talk) 23:06, 12 March 2024 (UTC)Reply
There is a |Pubchem= parameter for {{Infobox drug}}, and presumably many/most of the affected articles have that infobox, so I don't think it should also be listed in WP:EL. And it's maybe even already populated with the correct entry, so in many cases this item should simply be removed altogether. That would certainly limit the scope of the pages needing actual attention. And in many of those cases, it probably merits an infobox update (and then nuking the EL) rathe than changing the EL. DMacks (talk) 02:08, 13 March 2024 (UTC)Reply
I asked WPMED for advice on whether they see a need to special-case around WP:EL vs infobox link. DMacks (talk) 15:24, 13 March 2024 (UTC)Reply
Thank you so much for this, and to DMacks for dealing with it. WhatamIdoing (talk) 17:40, 13 March 2024 (UTC)Reply

Remove NYTimes tracking parameters edit

Hey all! I know there is previous consensus to remove tracking parameters from URLs in articles (ex: PrimeBOT 17 and its predecessor), and I've noticed a parameter that appears in many URLs from The New York Times (in almost 3,700 articles as of now). There's also this particular link from the Mona Lisa article that shows a few more tracking parameters used by NYT: https://thelede.blogs.nytimes.com/2008/01/15/mona-lisas-identity-solved-for-good/?searchResultPosition=2&mtrref=www.nytimes.com&gwh=9DE4B32CC79812F2537467E9D52707E9&gwt=pay&assetType=REGIWALL.

I'd like to create a bot task to remove these but wanted to start a conversation on-wiki first to ensure there's consensus. I believe I have some draft code started that would work well, matching all NYT subdomains and whatnot. (Using the following regex to find NYT links in source code and this library to edit them \b(?:https?://)?(?:[\w-]+\.)*nytimes\.com/[\w/.\-#?&=]*\btest it)

Overall thoughts from the community? Bsoyka (tcg) 03:14, 15 March 2024 (UTC)Reply

Please do not modify archive URLs eg. avoid "/https://" or "?url=https://" covers most cases. -- GreenC 03:56, 15 March 2024 (UTC)Reply
@GreenC: Ah, good point — thank you! I've updated the regex and I think this should work to avoid archive URLs. You can see it working here:
(?<!/)(?<!\?url=)https?://(?:[\w-]+\.)*nytimes\.com/[\w/.\-#?&=]* Bsoyka (tcg) 04:15, 15 March 2024 (UTC)Reply
  • As long as you can do it without making it harder to access the article, definitely, yes! --David Tornheim (talk) 05:49, 15 March 2024 (UTC)Reply
  • I can just append this to my existing task. Just to check, these are mtrref, gwt, and gwh, yes? Primefac (talk) 08:51, 15 March 2024 (UTC) Primefac (talk) 08:51, 15 March 2024 (UTC)Reply
    @Primefac: I'd originally thought about that, but these parameters seem specific to the NYT. Those three you mention seem like they'd probably be safer to remove globally, but the one I was originally focusing on, searchResultPosition, along with assetType, seem like they'd have potential uses on other sites that could break the linked page if they're not included in the URL. (A few potential examples) Bsoyka (tcg) 14:24, 15 March 2024 (UTC)Reply
    Okay, so it's more about removing a full string of parameters rather than a group of them. Primefac (talk) 09:09, 16 March 2024 (UTC)Reply
    Does Primefac's existing task have a facility to remove a tracking parameter only from certain domains? Certes (talk) 23:16, 15 March 2024 (UTC)Reply
    Yes (see its talk page), I just need to do a short run to show there aren't any issues. Primefac (talk) 09:08, 16 March 2024 (UTC)Reply
    Awesome, even better. I'll let you take it from here then! Bsoyka (tcg) 13:04, 16 March 2024 (UTC)Reply
      Done, for the bot (and the record); I've taken care of everything that was there currently, and I'll add it into my rota for the utm checks. Primefac (talk) 14:17, 27 March 2024 (UTC)Reply

NFL Draft move downcasing cleanup edit

The report Wikipedia:Database reports/Linked miscapitalizations shows something over 20,000 links to over-capitalized redirects after the NFL Draft downcasing moves, and there are of course lots of other over-capitalizations in the text other than links. User:Bagumba has fixed a few thousand over the last few days, but I think it might be better to take his JWB setup and make a bot run of it. Someone with more experience with such things could tune up his regular expressions to be more precise and effective, I expect. See our discussion at User talk:Bagumba#JWB followups. Dicklyon (talk) 05:05, 17 March 2024 (UTC)Reply

At a high-level, some of the changes are to:
  1. Replace links to all "XXXX NFL Draft" and "XXXX NFL/AFL Draft" redirects to the actual page title "XXXX NFL draft" or "XXXX NFL/AFL draft" (see Category:National_Football_League_draft)
  2. If any of those links are also piped, changed the displayed text from "Draft" (when present) to "draft"
  3. Change links to the redirects if referred by {{main}} or {{see also}}
The relevant discussion to lowercase to "NFL draft" was at Wikipedia:Requests for comment/Capitalization of NFL draft article titles.—Bagumba (talk) 05:29, 17 March 2024 (UTC)Reply
I think this would be a fun one to take on! I think it could be done really effectively by using mwparserfromhell to filter and edit wikilinks across these pages. If no one else wants to work on this and no existing bot task can handle it, count me in. Bsoyka (tcg) 13:40, 17 March 2024 (UTC)Reply
Also, should this task potentially be expanded to cover all the linked miscapitalizations at that database report? Bsoyka (tcg) 13:49, 17 March 2024 (UTC)Reply
Potentially, though I'd go slow on the general case, as some of those have their own complications that might not be obvious at first. I'm glad to hear you have a decent parser, as that's clearly what's needed for best results. I look forward to seeing how you take this on. We're willing to help. Dicklyon (talk) 09:23, 18 March 2024 (UTC)Reply
This will likely not get approval as a bot task; "fixing" redirects is very, very rarely supported on a mass scale. You should know this already, Dicklyon, given that your insistence on doing so was what got you banned from using AWB in the first place. Primefac (talk) 09:48, 18 March 2024 (UTC)Reply
That is totally not true! What got me banned was that I made a few mistakes while editing too fast; some false positives in contexts such as reference titles slipped by me. Nobody objected to what I was trying to do, as far as I recall, though some general discomfort with case fixes was likely an underlying motivation for them wanting to throttle me. Dicklyon (talk) 09:57, 18 March 2024 (UTC)Reply
@Primefac: This specific case has gone through an RFC, approving both the page titles and the general usage of the term "NFL draft" in text. Seems uncontroversial at this point for this case. —Bagumba (talk) 10:00, 18 March 2024 (UTC)Reply
I recognise that there was an RFC to change the article titles, but bots replacing redirects is usually seen to be a minor task that should be done in combination with other tasks, not done on its own (especially when considering piped links which would offer no visual change to the page). I can't deny a bot request that hasn't been filed, and you are welcome to do what you feel is necessary, I'm just telling you my initial opinion based on this request. Primefac (talk) 10:12, 18 March 2024 (UTC)Reply
Understood. FWIW, 95+% of the links are not piped, so it generally would be making a visual change and not just be cosmetic. —Bagumba (talk) 10:20, 18 March 2024 (UTC)Reply
Primefac, if you'll review the RFC, you'll see that it was not just to change article titles. As for replacing piped redirects, yes it's a minor task, but an important one in making the maintenance report useful. It's not just cosmetic, as it affects that report. Prohibiting such fixes would make that report useless. I've been doing such fixes manually for many months now, thousands of edits, and have had zero pushback about fixing piped links to miscapitalized redirects. Dicklyon (talk) 10:26, 18 March 2024 (UTC)Reply
For reference see a recent run on JWB. Mostly (if not all) unpiped links i.e. non-cosmetic.—Bagumba (talk) 10:35, 18 March 2024 (UTC)Reply
Right, most of these are not piped links. But we should also be fixing those that are, such 2000. Dicklyon (talk) 10:48, 18 March 2024 (UTC)Reply
Bagumba, did you use any patterns that would have replaced piped links? If there's any significant pushback such as Primefac suggests, we could just not do that at all. It would still be huge progess, avoiding fixing piping through miscapitalized redirects, and we could use non-bot methods to decide what else to do. Dicklyon (talk) 11:04, 18 March 2024 (UTC)Reply
In my experience, almost every (all?) page that was edited had at least one link that was not piped. Later links might pipe just the year only, when it was obvious that the context was to a particular draft. Otherwise, it'd be pipes like [[2023 NFL Draft|2023 Draft]] or [[2023 NFL Draft|the Draft]], where "Draft" was still in the displayed text. —Bagumba (talk) 11:26, 18 March 2024 (UTC)Reply

From my understanding of the RfC, I do agree that it says "draft" should be lowercase across NFL-related articles, not just in the titles but in the content as well. I believe that with my intended method of parsing the wikicode itself with mwparserfromhell rather than simple regexes, everything can be taken care of, including piped links. (i.e. [[2024 NFL Draft|2024 Draft]] -> [[2024 NFL draft|2024 draft]]) If this is decided to be a good bot task, I'd love to take it on, but if not, I respect the consensus of the community. Bsoyka (tcg) 15:11, 18 March 2024 (UTC)Reply

Probably it's best to avoid controversy by not doing edits where the only change is to piped links (e.g. [[2024 NFL Draft|2024]]); where other things are being fixed, these are worth fixing at the same time. I don't think this will leave many articles linking to the NFL Draft articles, as they pretty much all have the capitalized Draft in text, too, per Bagumba's experience. Dicklyon (talk) 07:03, 19 March 2024 (UTC)Reply
@Bsoyka: Are you an experienced bot operator, familiar with how to do the approval request and such? Can we get started on that? Dicklyon (talk) 07:08, 19 March 2024 (UTC)Reply
@Dicklyon: Somewhat, in that I've been through the process a couple of times and currently run a daily bot task (see User:BsoykaBot). I'll work on some code and get a BRFA going shortly. Bsoyka (tcg) 02:10, 20 March 2024 (UTC)Reply
Sounds good. Don't rely on the report at Wikipedia:Database reports/Linked miscapitalizations, since a user has untagged all the NFL Draft redirects as not "errors". See discussion at User talk:Hey man im josh#NFL Draft capitalization. @Hey man im josh:. Also, many were not yet tagged. Dicklyon (talk) 02:19, 21 March 2024 (UTC)Reply
I actually have a script working to generate a list of these "XXXX NFL Draft" redirects without that database report; in other words, my tentative bot code doesn't rely on the {{R from miscapitalization}} template, so no worries on my end. Bsoyka (tcg) 02:25, 21 March 2024 (UTC)Reply
My code appears to work, so...   BRFA filed! Bsoyka (tcg) 02:55, 23 March 2024 (UTC)Reply

Bot to clean up wikiproject templates edit

Some relevant tasks include:

  • Disabling the needs-infobox parameter if there is an infobox on the article
  • Disabling the needs-image parameter if there is an image on the article

Cocobb8 (💬 talk • ✏️ contribs) 15:14, 19 March 2024 (UTC)Reply

Disabling the needs-infobox parameter edit

@Cocobb8: I haven't run BattyBot 70 since October to work on removing |needs-infobox= where it's no longer needed, so I'll start that up now. GoingBatty (talk) 03:38, 23 March 2024 (UTC)Reply
@Cocobb8: BattyBot 70 is in the process of removing the |needs-infobox= parameter from about 830 pages. GoingBatty (talk) 19:12, 23 March 2024 (UTC)Reply
Awesome! Cocobb8 (💬 talk • ✏️ contribs) 15:05, 24 March 2024 (UTC)Reply

Disabling the needs-image parameter edit

@Cocobb8:Is there consensus somewhere to disable the |needs-image= parameter if there is an image on the article? I believe it's possible that an article needs another image or a better image even though it already has one. GoingBatty (talk) 03:38, 23 March 2024 (UTC)Reply
@GoingBatty: Quoting from the image requested template: It is a residual indicator, not a general-purpose "no image present" indicator (for that, use {{improve images}}) Cocobb8 (💬 talk • ✏️ contribs) 14:00, 23 March 2024 (UTC)Reply
@Cocobb8: Thank you for the link to the template {{Image requested}}. However, I don't see how that is related to the request to disable the |needs image= parameter (and presumably all its variations) from WikiProject templates. GoingBatty (talk) 19:08, 23 March 2024 (UTC)Reply
@GoingBatty Yes my bad, I got mixed up. No idea if there is consensus for it or not, but I would assume that it is only set as "yes" if there no images at all. Cocobb8 (💬 talk • ✏️ contribs) 14:58, 24 March 2024 (UTC)Reply

Update WP: maintaince pages edit

A bot to make edits like this one: https://en.wikipedia.org/w/index.php?title=Wikipedia%3ABacklog&diff=1214091029&oldid=1197405012. Also used at Wikipedia:Disambiguation pages with links#Current disambiguation collaborations. OrdinaryGiraffe (talk) 23:43, 21 March 2024 (UTC)Reply