Wikipedia:Bot requests

  (Redirected from Wikipedia:BOTREQ)
Jump to navigation Jump to search

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

Category sorting for Thai names[edit]

Hi. I'm looking to revive a request previously made in 2018, which was discussed (to a considerable extent) here and here. Back then, TheSandDoctor originally offered to help, but due to other circumstances was unable to devote time to the task, and suggested that I ask here again. I've left it for quite some time, but better late than never I guess.

Briefly, names should be sorted by given name (i.e. as they appear) in Thailand-related categories. A Thai biography footer should as such contain the following:

{{DEFAULTSORT:Surname, Forename}}
[[Category:International people]]
[[Category:Thai people|Forename Surname]]

Currently, compliance is all over the place, with the Thai order being placed in the DEFAULTSORT value in some articles, and the Thai sort keys missing in others. A bot is needed to: (1) perform a one-time task of checking DEFAULTSORT values in Thailand-related biographies (a list with correct values to be manually supplied), and replacing the values if incorrect, and (2) do periodical maintenance by going through a specified list of categories (probably via a tracking template placed on category pages) and adding the Thai name order as sort keys to those categories' calls in each member article that is a biography. In most cases, the Thai name order would be the page title, but there are several exceptions, which I will later elaborate upon. This had been advertised and some details of the task ironed out back then, but since it's been three years there may be need to reaffirm consensus. I would like to see first, though, whether any bot operators are interested in such a project. --Paul_012 (talk) 00:13, 26 February 2021 (UTC)

@Paul 012:Well, I think I will do this:
  1. For pages in Category:Thai people, all sub-pages of categories transcluding {{Thai people category}}:
  2. Add / modify DEFAULTSORT as {{DEFAULTSORT:Surname, Given name}}
  3. + Category:International people
  4. Modify sort key of Category:Thai people and categories transcluding {{Thai people category}}, as [[Category:Category name|Given name Surname]]
Do I miss anything? --Kanashimi (talk) 08:36, 11 March 2021 (UTC)
Kanashimi, the "Category:Thai people" and "Category:International people" in the example were meant as placeholders for all categories in and outside the pre-defined set, not literal categories with those names (so skip No. 3); sorry if this wasn't clear. The set of categories could be tracked by {{Thai people category}} (the template will need to be added), though this isn't set in stone. There are also names which are not in the Given-name Surname format; a list of these will probably need to be compiled by hand, so that's also something to consider. --Paul_012 (talk) 20:43, 11 March 2021 (UTC)
I misunderstood the discuss. Is this right?
  1. For categories transcluding {{Thai people category}} and their subcategories, call it Thai_CATEGORY_LIST. For articles in all Thai_CATEGORY_LIST, call it Thai_ARTICLE_LIST. And we will do this for all Thai_ARTICLE_LIST:
  2. If the article is in Template:Thai people category/doc#Sort keys of biographical articles added to categories with this template:
    1. Modify sort key of categories in Thai_CATEGORY_LIST, as [[Category:Category name|Category Sort key specified]]
  3. Else:
    1. Add / modify DEFAULTSORT as {{DEFAULTSORT:Surname, Given name}}
    2. Modify sort key of categories in Thai_CATEGORY_LIST, as [[Category:Category name|Given name Surname]]
And I have a question: Are the surnames of Thai peoples in English always just one-word so I can split the given name and surname via article title easily; it is always in a pattern of "given given given ... surname"? --Kanashimi (talk) 22:26, 11 March 2021 (UTC)

Maybe I should provide a bit more background first. The short answer your last question would be, "No." To get the long answer, I went through the about 4,000 Thai people articles to identify the following patterns:

lengthy name examples
  • The majority (about 3,300) are regular two-part given-name/surname names like Abhai Chandavimol (defaultsort Chandavimol, Abhai). These include a few dozen pseudonyms or stage names that are generally treated as if they were normal names, e.g. Amnaat Luukjan (Luukjan, Amnaat).
  • There are a few dozen multi-word names which are composed of either multiple-word given names (or middle names), and/or multiple-word surnames. Examples include:
  • Some names which appear to have two words are actually a single name, and must be sorted as they appear in all categories (both non-Thai and Thai). Examples include:
    • Lor Tok is a single word written in English with a space. Sort as Lor tok.
    • Sunthorn Phu is two words, but never separated. Sort as Sunthorn Phu.
    • Headache Stencil - a pseudonym with two words, also shouldn't be separated (Headache Stencil)
    • The Toys - a pseudonym with the article the. Sorted as Toys, The
    • Pang brothers - some are phrases that don't need a defaultsort
  • A couple hundred royal names. Some of them are multi-word names, but all are sorted as they appear (these may need checking as they may be confused with surnames). Examples:
  • A couple dozen articles use noble titles. These come in three parts: a prefix rank; the main title; and sometimes the person's personal name in parentheses. They should be sorted by the main title in all categories. Examples:
  • Some Buddhist monk names include honorifics. The given name and/or monastic name, or ecclesiastical title may be used. Sorting should omit the honorific in all categories.
  • Actors and singers often use a stage name based on their nickname. Often, this is combined with their given name to form a two-word name which sometimes is treated as if it were a regular name. Others are suffixed by the name of their band or label, which should probably not be treated as such.
    • Phum Viphurit - Phum is his nickname and Viphurit his given name, but English-language sources tend to treat them as given name and surname, so maybe sort in non-Thai categories as Viphurit, Phum?
    • Aed Carabao - Carabao is the name of his band, and no one would refer to him as such; should be sorted as Aed Carabao in all categories
  • Most boxers' ring names are two- or multi-word names. I don't quite know how they're used in English. Are they treated as regular names? If so, Muangthai P.K. Saenchaimuaythaigym wouuld take the defaultsort P.K. Saenchaimuaythaigym, Muangthai.
  • Some names are Chinese names and should be sorted in the Chinese order in all categories. E.g. Khaw Soo Cheang (Khaw, Soo Cheang)
  • There are also some other non-Thai names that show up in the list; their defualtsort values should be left alone.

I guess all this is to say it's probably far too complicated for the defaultsort value to be automatically processed; reading off a manually compiled list would be more practical. I'm still tweaking the list but see for example an earlier (outdated) version at Special:Permalink/829756891.

I think the process should be something more like:

  1. For categories transcluding {{Thai people category}}, call it Thai_CATEGORY_LIST. For articles in all Thai_CATEGORY_LIST, call it Thai_ARTICLE_LIST. And we will do this for all Thai_ARTICLE_LIST:
  2. If the article is a personal biography, proceed with the following:
    1. If the article is in DEFAULTSORT_UPDATE_LIST:
      1. Add / modify DEFAULTSORT according to the value in DEFAULTSORT_UPDATE_LIST
      2. If so instructed by DEFAULTSORT_UPDATE_LIST:
        1. Add {{Thai sort same as defaultsort}} to the article
      3. Else:
        1. Modify sort key of categories in Thai_CATEGORY_LIST, as [[Category:Category name|PAGENAME]] (though format the page name to exclude parenthetical disambiguators)

The above applies to the bot's initial run. There should also be periodical update runs, where 2.1 would be:

    1. If DEFAULTSORT exists and is different from article title (excluding commas and parenthetical disambiguators), and {{Thai sort same as defaultsort}} is not found in the article:
      1. Modify sort key of categories in Thai_CATEGORY_LIST, as [[Category:Category name|PAGENAME]] (though format the page name to exclude parenthetical disambiguators)

Category recursion is tricky and can lead to unexpected problems, so {{Thai people category}} should probably be placed directly on all applicable category pages. (That may also be a bot task.) I'm working off this preliminary list: Special:Permalink/1011801926, but some further tweaks my still be needed.

Since the Thai sort key will be the same as either the article title (for regular names) or the DEFAULTSORT value (for royalty, etc.), the DEFAULTSORT_UPDATE_LIST can note which case applies to each article, and this can be tracked in the article source. I think this would be preferable in the long run, as a central list will be hard to keep updated while a tracking template can be added to new articles as they are created. {{Thai sort same as defaultsort}} wouldn't need to generate any visible output (except maybe a tracking category if useful).

Does this more or less make sense? --Paul_012 (talk) 23:15, 12 March 2021 (UTC)

In the process above, we will ignore all articles that is not in DEFAULTSORT_UPDATE_LIST, even if the article is in Thai_ARTICLE_LIST. I think we may detect given name and surname automatically (for example, list up common surnames), only list up special cases in another list. This will greatly reduce the workload for human and bot both. And, is {{Thai sort same as defaultsort}} should appears in this way: {{Thai sort same as defaultsort}}{{DEFAULTSORT:Surname, Given name}} (nothing between the template and DEFAULTSORT)? --Kanashimi (talk) 01:26, 13 March 2021 (UTC)
Oops, should have been more like this:
  1. If the article is a personal biography, proceed with the following:
    1. If the article is in DEFAULTSORT_UPDATE_LIST:
      1. Add / modify DEFAULTSORT according to the value in DEFAULTSORT_UPDATE_LIST
      2. If so instructed by DEFAULTSORT_UPDATE_LIST:
        1. Add {{Thai sort same as defaultsort}} to the article
        2. Skip to next article
    2. Modify sort key of categories in Thai_CATEGORY_LIST, as [[Category:Category name|PAGENAME]] (though format the page name to exclude parenthetical disambiguators)
I don't quite see a practical set of instructions that would allow automatic name identification, given the intricacies involved. The human workload isn't a problem, as I'm mostly done with the names already (just needs a second check). I imagine the placement of the Thai sort same as defaultsort template the way you described. It's a preliminary suggestion though; if we agree to proceed with the method I'll post at the MOS talk page for community approval. --Paul_012 (talk) 07:18, 13 March 2021 (UTC)
Ok. I get a rough idea of what you mean. I think DEFAULTSORT_UPDATE_LIST should include PAGENAME, surnames, and given names; at least three columns. By the way, how do we maintain new Thai people articles? They will not in DEFAULTSORT_UPDATE_LIST. --Kanashimi (talk) 07:51, 13 March 2021 (UTC)
I expect DEFAULTSORT_UPDATE_LIST to be referred to only once, to check currently existing articles. The practice of specifying Given-name Surname as the DEFAULTSORT (which the bot will need to correct) is quite old (mostly found in articles from over a decade ago I think). New articles today will likely have DEFAULTSORT values in the Surname, Given-name format, so will only need PAGENAME sort keys added. The minority of articles which require specific formatting and tagging can be handled by patrollers following WikiProject Thailand's potential new articles feed as they are created. --Paul_012 (talk) 09:13, 13 March 2021 (UTC)
Ok. It seems possible for bot to do this. --Kanashimi (talk) 10:58, 13 March 2021 (UTC)
Thanks for the responses, Kanashimi. Do you plan to take on the task? If so, I'll notify the relevant projects and discussion pages. --Paul_012 (talk) 14:05, 14 March 2021 (UTC)
Yes, but I still need your help. I don't speak Thai. 😓 And please split the name to surname, and given name. I think this will be useful. --Kanashimi (talk) 21:54, 14 March 2021 (UTC)

I've opened a discussion requesting community input at Wikipedia talk:Categorization of people#Bot for Thai name category sorting. I've now also listed the categories and articles at Wikipedia:WikiProject Thailand/Thai name categories and Wikipedia:WikiProject Thailand/Thai name sort keys. --Paul_012 (talk) 18:54, 16 March 2021 (UTC)

Kanashimi, there hasn't been further comment, but given the lack of opposition, I think it should be safe to go ahead based on the previous consensus, when you have time. (I might not be very active for some time, so please leave me a talk page message if I don't respond to pings.) --Paul_012 (talk) 09:25, 14 April 2021 (UTC)
@Paul 012: BRFA filed --Kanashimi (talk) 10:07, 14 April 2021 (UTC)

@Paul 012: Sorry, it seems there are some pages modified during the interval we waiting for the task approved. Can you check and update Wikipedia:WikiProject Thailand/Thai name sort keys again? Thank you. For example,

And how do we deal with the pages moved in the future? When the pages moved, the sort key will not follow the changing. --Kanashimi (talk) 00:36, 31 May 2021 (UTC)

Kanashimi, list updated. I think future page moves can be adequately dealt with manually—editors moving pages are already expected to take care of updating the category sort keys, as the general rule. --Paul_012 (talk) 15:32, 31 May 2021 (UTC)
@Paul 012 Please check Wikipedia:WikiProject Thailand/Nonbiographical pages transcluding Thai name categories Kanashimi (talk) 23:56, 1 June 2021 (UTC)
@Kanashimi: Done. There were a few false positives, most of which were due to the article lacking birth/death year categories, which I've rectified. The list does seem to include quite a few articles that shouldn't have been picked up, though. For example, Made in Thailand doesn't transclude any Thai-people categories, though it is in Category:Carabao (band) albums, which is under Category:Carabao (band); it seems there's some unintended category recursion taking place. --Paul_012 (talk) 15:15, 2 June 2021 (UTC)
@Paul 012 OK, I fix this. May I mark the phase 1 is done? Kanashimi (talk) 21:09, 2 June 2021 (UTC)
The last round of edits still had problems where the DEFAULTSORT wasn't added to articles which didn't already have one (e.g. Special:Diff/1026370887). Could you check this? --Paul_012 (talk) 05:29, 3 June 2021 (UTC)
@Paul 012 Fixed Please check the new round. Wikipedia:WikiProject Thailand/Nonbiographical pages transcluding Thai name categories should properly now. Sheikh Ahmad (nobleman of Siam) seems strange... Kanashimi (talk) 07:34, 3 June 2021 (UTC)
Kanashimi, all seems sorted out, from what I've checked. The Sheikh Ahmad article was recently created, so it wasn't added to the list, but it's now manually tagged so shouldn't be a problem going forward.

I know I'm late to the party but would it make any sense to sort the Thai names as [[Category:Thai foos|{{PAGENAME}}]] (literally the word PAGENAME in braces) so they will update automatically if the page name changes? That would include parenthetical qualifiers, but consistently sorting Foo bar (footballer born 1900) before Foo bar (footballer born 2000) might not be a bad thing. Non-Thai names in Thai categories could either follow suit to sort consistently (often by given name) or simply omit the sort code to sort by DEFAULTSORT (normally surname). Certes (talk) 09:45, 2 June 2021 (UTC)

@Certes: Hmm. I never considered that. Not sure how acceptable it would be in the community's view, given that using the magic word directly in articles doesn't seem to be usual practice, but it should indeed produce no difference in output in articles with the regular name structure, and I can't think of specific examples where this would be detrimental. The change will probably need to be proposed at WP:NAMESORT first, though. --Paul_012 (talk) 15:15, 2 June 2021 (UTC)
My suggestion wouldn't handle Sheikh Ahmad (nobleman of Siam), but then nor would the current method or any other proposal I've seen. A few pages will always need manual attention. Certes (talk) 08:47, 3 June 2021 (UTC)
Certes, the initial bot run is now complete, but if the PAGENAME option is agreed upon it could be later implemented via the planned weekly update runs. I think the bot can stick to the original method for now; maybe other considerations will arise as time goes by that will also be worth re-evaluating. --Paul_012 (talk) 13:45, 3 June 2021 (UTC)

Paul_012 I start running the routine version, it modifying 2 pages. Please check this round. --Kanashimi (talk) 23:31, 3 June 2021 (UTC)

Hmm. Fahlan Sakkreerin Jr. demonstrates a minor issue where the sorting rules (not to include "Jr.") are a bit more complex than copying the article title, but since it doesn't produce any difference in output, I think we can live with that. The weekly runs should be good to continue. On what days do you plan to run the task (so I can remember to check)? --Paul_012 (talk) 07:12, 4 June 2021 (UTC)
@Paul 012 When are you free? Kanashimi (talk) 07:39, 4 June 2021 (UTC)
@Kanashimi: Right now, whenever is fine. --Paul_012 (talk) 14:24, 4 June 2021 (UTC)
I set the task running on Saturday, so you may check it weekend. It seems we may close this request then? Kanashimi (talk) 20:36, 4 June 2021 (UTC)
Okay, marking as  Done. --Paul_012 (talk) 16:17, 5 June 2021 (UTC)

Remove dead links from book and journal citation templates with identifiers[edit]

The March 2021 cleanup backlog for the Medicine WikiProject is currently dead links on articles that start with the letter A. About a quarter/third or so of the list was dead links in "cite journal" and "cite book" templates (Template:Cite journal and Template:Cite book) that contain identifiers such as ISBN, DOI, or PMID. A URL is not necessary in these references because identifiers are used. Using the March backlog as a sample and considering the size of the dead link category for the Medicine WikiProject as a whole (currently around two thousand), there are potentially thousands of dead links site-wide that fall into this type of dead link. Removing a single one of these dead links is simple but finding all of them and making a large number of tedious edits is very time-consuming, so this seems like a task a bot could do. Note that |access-date and other URL-related parameters would also be removed. An example of what the bot edits would look like. Velayinosu (talk) 04:09, 25 March 2021 (UTC)

Just to add another voice to this and try to gin up some interest here, the task would be to go through each page in Category:All articles with dead external links (251,000 pages have 1+ dead EL!). If the dead link is a URL within {{Cite journal}} or {{Cite book}}, and that template already includes a stable identifier (I think any of the ~26 parameters in Template:Cite_journal#Identifiers will do?), then we don't actually need to fix the dead URL since a stable identifier is pointing to the correct location. So the dead URL and the maintenance tag can be safely removed. This will help us prioritize our time to address dead links that require human intervention. Also the brave bot-operator to take this task up will probably be responsible for the largest drop in articles-with-dead-links of all time. Certainly worth bragging rights at Wikipedia talk:Backlog. Happy to address questions or concerns. Ajpolino (talk) 07:57, 31 March 2021 (UTC)
@Velayinosu and Ajpolino: I will accept this if still useful, initially just for the Medicine WikiProject. William Avery (talk) 21:01, 12 May 2021 (UTC)
@William Avery: that would be great! Still useful. Petscan shows 2113 articles currently tagged for WikiProject Medicine and in Category:All articles with dead external links. I think a conservative version of this bot would remove the tag only if the reference is in the cite book/cite journal templates, and the provided identifier links to the full text (i.e. |doi=, |jstor=, |pmc=, or |pmid=). If you have questions/concernes, let me know. Thanks! Ajpolino (talk) 15:12, 14 May 2021 (UTC)
Ajpolino and William Avery: Couple thoughts: URLs typically appear in |url= but there are many other places in a template a URL might be located. See the CS1|2 Lua Configuration source and search on "url". Since it has a {{dead link}} it unlikely to have a |archive-url= + |archive-date= + |url-status= .. but I have seen it, the possibility exists, they should be removed as well. Let's see.. it could end up removing a dead URL that can be saved via Wayback and this Wayback contains the full PDF, while the DOI link doesn't contain the full PDF. One way to tell is if the template has a |doi-access=free which flags the full PDF is freely available at the identifier-produced URL. Pinging Nemo who is more knowledgeable.. @Nemo bis:. -- GreenC 16:53, 14 May 2021 (UTC)
Yes, good point. Perhaps a better starting list is articles that InternetArchiveBot has already attempted and failed to find a Wayback link for, i.e. Category:Articles with permanently dead external links. That list is about 190,000 total articles; 1,541 tagged for WP Medicine. Ajpolino (talk) 17:06, 14 May 2021 (UTC)
I intend to take a look at this task in the coming week. It sounds like removing permanently dead links where there is {para|doi-access|free}} will be the least controversial step. Any advice on whether further discussion or notice is required at other venues before filing a BRFA will be gratefully received. William Avery (talk) 08:28, 16 May 2021 (UTC)
Doing... Working on scanning for suitable cases at the moment. At this stage the bot will create lists such as User:William_Avery_Bot/testsample. William Avery (talk) 20:05, 19 May 2021 (UTC)
Great! My impression is that |doi-access= is used relatively rarely (unless a bot has been adding it?), but I aagree it's the most straightforward task. So let's see how wide a net that is, and if we then want to test a broader set of restrictions we can do so. Thanks again William Avery! Ajpolino (talk) 20:32, 20 May 2021 (UTC)
@GreenC: Am I right in thinking that I should be ignoring deadlinks with an associated {{cbignore}}, such as this? Any deadness there seems to have been transient, BTW. William Avery (talk) 16:02, 23 May 2021 (UTC)
Oxforjournals is a known difficult case and probably should not used as an example, in this example the dead link should be removed. Generally though, cbignore is just a flag to tell IABot not to process the citation because it was already done by WaybackMedic and this helps prevent bot wars when there is disagreement. -- GreenC 22:08, 23 May 2021 (UTC)
Still doing... - Today's discovery is that when the url parameter is removed, any access-date parameter must be removed too, otherwise a template error is produced. William Avery (talk) 21:50, 28 May 2021 (UTC)
@Ajpolino: BRFA filed - strictly free access only for now. William Avery (talk) 08:41, 2 June 2021 (UTC)

Bot to repair broken peer review links[edit]

Summary of problem
Summary of bot request
  • There is now a way to provide the artice title of the page when it was reviewed (e.g. Special:Diff/986964116)
  • I would like help with a bot to go through the 700 or so reviews with broken links to provide this information and fix the link
  • User:AWMBot by BJackJS was created for this (Wikipedia:Bots/Requests for approval/AWMBot ) but unfortunately the editor is on a long wikibreak and this occurred during the bot approval process. There is one remaining problem that stopped the bot from being approved, which is that for some reason the link is duplicated when the bot runs through some articles. (see also Special:Diff/986964116)
  • I am hopeful finishing this request may be as simple as picking up User:AWMBot's code and making some small fixes.

Hopefully once a bot has gone through those articles, there may only be a few additional cases that I can manually fix. Unfortunately 700 is too much for me to do manually :(. Thanks I hope! --Tom (LT) (talk) 09:45, 2 April 2021 (UTC)

Update: bot request has been refiled at Wikipedia:Bots/Requests for approval/AWMBot 2. Tom (LT) (talk) 05:00, 11 May 2021 (UTC)

Bot for Top 25 report[edit]

Could a bot be created to add/update {{Top 25 report}} to the talk pages of pages featured in the Top 25 reports, it would be useful if the bot could also do the annual top 50 report and if the bot could go through the old top 25 reports as a few are missig thier talk page banners. Thanks,
SSSB (talk) 09:20, 18 April 2021 (UTC)

It seems a long term task. --Kanashimi (talk) 04:46, 19 April 2021 (UTC)
We'd need to do one iteration over all the reports (to make sure they all have the template), but after that it need only run once a week on the most recent report (i.e. 25 edits per week).
SSSB (talk) 09:23, 19 April 2021 (UTC)
Maybe we can also place it inside {{Article history}}? --Kanashimi (talk) 01:04, 20 April 2021 (UTC)
That's something you should bring up at Wikipedia:Templates for discussion
SSSB (talk) 08:19, 20 April 2021 (UTC)
Sorry, I just give some suggestions. Kanashimi (talk) 09:07, 20 April 2021 (UTC)

Creating a list of userpages that have been edited by the editor once[edit]

I am requesting for a bot to go through userpages so that a list is created of pages where its users have made edits only to their pages.

The intent is to tag these user pages as {{Db-notwebhost}}.Catchpoke (talk) 00:46, 22 April 2021 (UTC)

That would also potentially tag drafts which are not eligable for speedy deletion under that criteria.
SSSB (talk) 07:13, 22 April 2021 (UTC)
So then we use the bot to create a list rather than to tag pages. Editors can assess eligibility of individual pages for {{Db-u5}}.Catchpoke (talk) 16:53, 22 April 2021 (UTC)
Does Special:NewPagesFeed not already serve this purpose? Tol | Talk | Contribs 20:22, 23 April 2021 (UTC)
no it doesnt seem to. there are many userpages which are no longer new and are older than 6 months which are eligible for deletion per the draft policy.Catchpoke (talk) 20:28, 23 April 2021 (UTC)
I think this request might be better initially filed at WP:SQLREQ. I put a query into Quarry that might roughly list a minuscule sample of the pages you are interested in:
This script will catch pages like User:Hoad, User:Martin_spen, User:SnoFyre, User:Eoinlane/LittletonConservationTrust. Whether they are worth tagging or deleting is a separate question, that would need to be resolved before anybody wrote a bot to do it. William Avery (talk) 16:39, 12 May 2021 (UTC)
wow what an amazing tool. it looks like toggling the limit might be filter the pages.Catchpoke (talk) 23:05, 12 May 2021 (UTC)
Hhmm: I just noticed User:Mikedill has made more than 1 edit. If it were necessary, how would the query be modified so that it only lists users who made one edit?-- Catchpoke (talk) 04:15, 16 June 2021 (UTC)

Replace Template:Tbullet with Template: Demo inline[edit]

{{demo inline}} is similar to {{tbullet}}, but the former supports an infinite amount of named and unnamed parameters. {{tbullet}} is more widely used, but can only support 6 unnamed parameters. I suggest replacing this:


with this:

* {{demo inline|<nowiki>{{t|1|2|3|4|5|6}}</nowiki>}} JsfasdF252 (talk) 22:27, 24 April 2021 (UTC)

You may be looking for Wikipedia:Templates for discussion. – Jonesey95 (talk) 22:46, 24 April 2021 (UTC)
Perhaps the author would like some bot assistance with mass-replacing the template with a bot? Not sure if that's the intention or if it's appropriate (didn't look into this thoroughly) EpicPupper (talk) 23:21, 24 May 2021 (UTC)
Unless there is a consensus to do so, then it will not be done. As Jonesey says above, if the template really should be replaced then TFD is the way to do it. Primefac (talk) 12:21, 25 May 2021 (UTC)

Featured topic bot[edit]

Hi all, the WP:Featured and good topic candidates promotion/demotion/addition process is extremely tedious to do by hand, and having a bot help out (akin to the FAC and FLC bot) would do wonders. Unfortunately, this would have to be a rather intricate bot—see User:Aza24/FTC/Promote Instructions for an idea of the promotion process—so I don't know if many would be willing to take it up. But regardless, such a bot is long over due, and its absence has resulted in myself, Sturmvogel 66 and GamerPro64 occasionally delaying the promotion process, simply because of the discouraging and time consuming manual input needed. I can certainly provide further information on the processes were someone to be interested. Aza24 (talk) 01:14, 4 May 2021 (UTC)

Doing... Aza24, hello friend. I started on this one tonight. You're right, this is quite complicated. Hopefully I am disciplined enough to complete this one. Feel free to ping me every once in awhile to keep me on task! I may ask you some questions once I get a little farther along. Code so far: task2-promote-topics.phpNovem Linguae (talk) 11:10, 18 May 2021 (UTC)
Is there a way to determine whether an article is a featured topic nominee vs a good topic nominee, purely from its nomination page? Example: Wikipedia:Featured and good topic candidates/Fabula Nova Crystallis Final Fantasy/archive1Novem Linguae (talk) 12:36, 18 May 2021 (UTC)
A topic has to be at least 50% to be considered Featured. I guess that would be hard to figure out for a bot, right? GamerPro64 02:08, 19 May 2021 (UTC)
Many thanks for taking this up Novem! Yeah, Gamer's comment is the only way to tell—though we could probably add a parameter to the template if that won't work? Aza24 (talk) 05:26, 19 May 2021 (UTC)
Aza24, GamerPro64. Thanks for explaining how that works. I'll make a note. Work is slow but progressing. Link to GitHub.Novem Linguae (talk) 13:29, 25 May 2021 (UTC)

Bot for Challenges projects[edit]

I would like to request that a bot starts putting a project-box on all articles that appear in the Wikipedia:The 2500 Challenge (Nordic). Plenty of other projects has this kind of box at the articles talk pages like at Talk:Gunnar Seijbold. The project is growing bigger. BabbaQ (talk) 11:59, 5 May 2021 (UTC)

I see now that the bot have stopped working for the Wikipedia:WikiProject Europe/The 10,000 Challenge as well. I know that the bots HasteurBot and AnomieBOT did the work for a while. --BabbaQ (talk) 12:00, 5 May 2021 (UTC)
Is there a template in the Category:Wikipedia article challenge templates? By the way, are there any bots continue the work of Wikipedia:Bots/Requests for approval/HasteurBot 15? --Kanashimi (talk) 07:09, 7 May 2021 (UTC)
Yes it is the template:WPEUR10k that has been used for the Europe project. And I also request that a similar box is made for the Nordic challenge. As far as I can see no bot has taken over Hasteurbots work. No new articles added receives the box at it’s talk pages.--BabbaQ (talk) 21:38, 8 May 2021 (UTC)
Since there are many challenge templates, should we integrate them together, like {{WikiProject banner shell}}, {{Article history}}, {{Multiple issues}} or {{Redirect category shell}}? Kanashimi (talk) 21:45, 8 May 2021 (UTC)
Great idea. If something can be done, that would be appreciated. And then having a bot placing the templates at the respective project articles talk pages.BabbaQ (talk) 23:28, 8 May 2021 (UTC)
BRFA filed Please give some ideas there and tell me the template name if it is created. --Kanashimi (talk) 23:49, 8 May 2021 (UTC)
Just as a note, the other templates in Category:Wikipedia article challenge templates have been nominated to be merged into their related WikiProject banners. It might be better to hold off creating the banner template until the discussion has ended. Primefac (talk) 13:01, 10 May 2021 (UTC)

Replace User:PumpkinSky's signatures[edit]

I am looking for anyone to take a task of replacing signatures of PumpkinSky (talk · contribs). Their old signature had <font>...</font> tags which are creating obsolete html tag Lint errors in all pages that have their signature. Regex search shows that the signature is currently in 1,081 pages across namespaces. To remove the errors, the font tags need to be replaced with span tags.

[[User:PumpkinSky|<font color="darkorange">Pumpkin</font><font color="darkblue">Sky</font>]] [[User talk:PumpkinSky|<font color="darkorange">talk</font>]] need to be replaced with [[User:PumpkinSky|<span style="color: darkorange;">Pumpkin</span><span style="color: darkblue;">Sky</span>]] [[User talk:PumpkinSky|<span style="color: darkorange;">talk</span>]]

ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 16:47, 11 May 2021 (UTC)

If we're going to have a bot do this, we should probably think a little bigger and compile a list of regexes, like these:
Extended content
  str = str.replace(/<font colou*r *= *["']* *([#a-z\d ]+)["']* *>([a-z\d_— \'&;:!°\.#ταλκ\(\)\-\?\.,\!ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\@\!\?\&⊕⊗会話投稿記録日本穣投稿րևանցիԵ]+)<\/font>/gi, '<span style="color:$1;">$2<\/span>');
  str = str.replace(/<font style="colou*r:["']* *([#a-z\d ]+)["']* *>([a-z\d_— \'&;:!°\.#ταλκ\(\)\-\?\.,\!ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\@\!\?\&⊕⊗会話投稿記録日本穣投稿]+)<\/font>/gi, '<span style="color:$1;">$2<\/span>');
  str = str.replace(/<font colou*r *= *["']* *([#a-z\d ]+)["']* size="*([\dpxem\. ]+)"* *>([a-z\d_— \'&;:!°\.#ταλκ\(\)\-\?\.,\!ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\@\!\?\&⊕⊗会話投稿記録日本穣投稿]+)<\/font>/gi, '<span style="color:$1; size:$2;">$3<\/span>');
  str = str.replace(/<font face *= *"* *([a-z ]+)"* *>([a-z\d_— \'&;:!°\.#ταλκ\(\)\-\?\.,\!ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\@\!\?\&⊕⊗会話投稿記録日本穣投稿]+)<\/font>/gi, '<span style="font-family:\'$1\';">$2<\/span>');
  str = str.replace(/<font colou*r *= *["']* *([#a-z\d ]+)["']* face= *"* *([a-z ]+)"* *>([a-z\d_— \'&;:!°\.#ταλκ\(\)\-\?\.,\!ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\@\!\?\&⊕⊗会話投稿記録日本穣投稿]+)<\/font>/gi, '<span style="color:$1; font-family:\'$2\';">$3<\/span>');
  str = str.replace(/<font face= *"* *([a-z ]+)"* colou*r *= *["']* *([#a-z\d ]+)["']* *>([a-z\d_— \'&;:!°\.#ταλκ\(\)\-\?\.,\!ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\@\!\?\&⊕⊗会話投稿記録日本穣投稿]+)<\/font>/gi, '<span style="font-family:\'$1\'; color:$2;">$3<\/span>');
  str = str.replace(/<font style *= *"color:([#a-z\d ]+);" *>([a-z\d_— \'&;:!°\.#ταλκ\(\)\-\?\.,\!ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\@\!\?\&⊕⊗会話投稿記録日本穣投稿]+)<\/font>/gi, '<span style="color:$1;">$2<\/span>');
  str = str.replace(/<font style *= *"([:#a-z\d ;\.\-]+)" *>([a-z\d_— \'’&;:!°\.#ταλκ\(\)\-\?\.,\!ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\@\!\?\&⊕⊗会話投稿記録日本穣投稿]+)<\/font>/gi, '<span style="$1">$2<\/span>');

  str = str.replace(/(\[\[User:[a-z\d_— \'&;:!°\.#ταλκ\(\)\-\?\.,\!ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\!\?\&⊕⊗会話投稿記録日本穣投稿]+\|)<font colou*r *= *["']* *([#a-z\d ]+)["']*>([a-z\d_— \'&;:!°\.#\(\)\-\?ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\!\?\&⊕⊗会話投稿記録]+)<\/font> *(\]\])/gi, '$1<span style="color:$2;">$3<\/span>$4');
  str = str.replace(/(\[\[User[ _]talk:[a-z\d_— \'&;:!°\.#ταλκ\(\)\-\?\.,\!ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\!\?\&⊕⊗会話投稿記録日本穣投稿]+\|)<font colou*r *= *["']* *([#a-z\d ]+)["']*>([a-z\d_— \'&;:!°\.#ταλκ\(\)\-\?ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\!\?⊕⊗会話投稿記録]+)<\/font> *(\]\])/gi, '$1<span style="color:$2;">$3<\/span>$4');
  str = str.replace(/(\[\[Special:Contributions\/[a-z\d_— \'&;:!°\.#ταλκ\(\)\-\?\.,\!ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\!\?\&⊕⊗会話投稿記録日本穣投稿]+\|)<font colou*r *= *["']* *([#a-z\d ]+)["']*>([a-z\d_— \'&;:!°\.#ταλκ\(\)\-\?\.,\!ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\!\?\&⊕⊗会話投稿記録日本穣投稿]+)<\/font> *(\]\])/gi, '$1<span style="color:$2;">$3<\/span>$4');
There are more at User:Jonesey95/AutoEd/doi.js. Someone more skilled at regex construction could no doubt make something more comprehensive. – Jonesey95 (talk) 20:05, 11 May 2021 (UTC)
I will be happy if font tags are replaced more broadly. Some more signature regex can be found in User:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ/common.js. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 02:43, 12 May 2021 (UTC)
Pinging @Ahecht: who had done similar bot jobs in past. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 02:47, 12 May 2021 (UTC)
I really only ran ahechtbot for signatures whose formatting was bleeding out onto other text on the page. While I did replace font tags while I was fixing other issues, doing it just to replace the font tags doesn't really seem worth the effort of going through another BRFA, doing trial runs, etc., especially when it makes no difference to readers. Obsolete HTML Tags are listed as "Low priority" errors, which makes it hard to label them as "egregiously invalid HTML" per WP:COSMETICBOT. --Ahecht (TALK
) 17:29, 12 May 2021 (UTC)
I had the same doubt about font tags and asked at WP:VPT. There seems to be general sentiment that Linter errors regardless of priority can be replaced by bots. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 18:11, 12 May 2021 (UTC)
BRFA filed. Using AWB for now, with the original regex search listed above in the original post. EpicPupper (talk, contribs) 17:59, 2 June 2021 (UTC)

Broken section links[edit]

I really thought we had a bot or several working on this, and it seems it was brought up as recently as last year, but I just had to make yet another manual fix, so... We really need a bot that reliably fixes section links when section names are changed. Preferably one that stays online for more than a few weeks before it stops working.[understatement] {{u|Sdkb}}talk 06:58, 21 May 2021 (UTC)

Yes Dexbot stopping on this task was recorded at Wikipedia:Bot activity monitor/Report ("0 actions in last 1 week, expected at least 1. Last seen 5 May 2021"). @Ladsgroup would you like automated notifications when the bot stops again? If so, add |notify=Ladsgroup to the bot's config line on Wikipedia:Bot activity monitor/Configurations. – SD0001 (talk) 07:06, 21 May 2021 (UTC)
@SD0001The bot has a monthly cron so it's natural it did in early May and as you can see in this link at did fix hundreds just in early May. @Sdkb The bot I wrote can fix up to a certain portion of broken section links but the rest are too complicated for a bot to tackle and needs manual attention. I've already started doing some basic NLP work in the code to detect the new section and more than that would cause a lot of errors. Ladsgroupoverleg 07:12, 21 May 2021 (UTC)
Thanks both for the info. Would making the edit period more frequent perhaps help the bot catch some of these instances before the changes become too much to handle automatically? For some high-traffic redirects, a broken anchor for a month could affect a sizable number of readers. {{u|Sdkb}}talk 07:30, 21 May 2021 (UTC)
Just a note. user:cewbot fix broken anchors for the articles recently edited. I may do a global scan, although it certainly take a long time... Kanashimi (talk) 23:13, 21 May 2021 (UTC)
By the way, I think a notetag like w:ja:ノート:2009年の日本 is beneficial for fixing broken anchors. How about doing this in enwiki? Kanashimi (talk) 23:52, 21 May 2021 (UTC)
@Kanashimi You mean that when a redirect is broken and the bot is unable to fix it, the redirect be templated to summon a human to fix it? That sounds like a good idea. – SD0001 (talk) 11:47, 22 May 2021 (UTC)
Yes, this is just what I mean. Moreover, when the bot finds the link being fixed, it will remove the notice automatically, like this. Kanashimi (talk) 12:11, 22 May 2021 (UTC)

Replace external links to Wikimedia commons with interwiki link[edit]

Following up from this discussion about converting links to Wikimedia commons from http → http, it was decided a better option is to convert "external" links (i.e only those enclosed in [...]) to interwiki links since it provides better protection against WP:LINKROT. For example [ Wikimedia commons][[:commons:File:Example.jpg|Wikimedia commons]]

There are currently about 4,100 main space pages that use http or http external link to commons. Most of them can be replaced with interwiki link. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 17:58, 28 May 2021 (UTC)

Just to double check, shouldn't that be [[:commons:File:Example.jpg|Wikimedia commons]]? Primefac (talk) 20:04, 28 May 2021 (UTC)
Yes, corrected. Thanks. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 02:11, 29 May 2021 (UTC)
If someone else gets to it first, that's fine, but I can probably swing this. Primefac (talk) 10:43, 29 May 2021 (UTC)
BRFA filed, withdrawn due to it not being a suitable task for a bot. Primefac (talk) 00:23, 30 May 2021 (UTC)
Oh. I thought it would pass easily and did not expect this. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 03:26, 30 May 2021 (UTC)
Neither did I, but apparently the dozen pages I checked were not indicative of the entire set. Too much in the way of CONTEXT issues. Primefac (talk) 10:48, 30 May 2021 (UTC)

Reverse DNS lookup bot[edit]

There's current a boatload of raw IPv4/IPv6 address used in URLs, instead of something legit useful to readers. Is there a way to parse/update a link like


by bot? Or something similar/close to this? I fully expect most such links to not be recoverable, but there could be a few that are. Headbomb {t · c · p · b} 23:01, 28 May 2021 (UTC)

I am not sure this could be done in any automated fashion by a bot given reverse DNS lookups are often unreliable and inaccurate. IPs change ownership, or host multiple domains, or have a hostname that would not be the correct target anyway. To pick a silly example, just resolved to for me, and while seems to work and could theoretically end up in an article somehow, that IP's reverse DNS is which is clearly not what we want. Certainly tools could be used to build lists of possible replacements that could be manually reviewed, and a bot could perhaps operate on that, or we could use an existing method like WP:URLREQ. — The Earwig (talk) 00:18, 29 May 2021 (UTC)
Yes, might be better as some kind of tool... perhaps with a bot to compile/build basic suggestions and have humans review things, possibly assisted by a script. Headbomb {t · c · p · b} 02:47, 29 May 2021 (UTC)

Merging GA template into article history[edit]

There are 210 talk pages that transclude both {{GA}} and {{article history}}. A bot could integrate the GA template data into the latter, to reduce template clutter. – SD0001 (talk) 18:15, 1 June 2021 (UTC)

For 210 edits, that might be easier for an AWB user to perform. Primefac (talk) 18:16, 1 June 2021 (UTC)

Please replace 265–420 with 266–420 in the following articles[edit]


Thank you! --ExperiencedArticleFixer (talk) 16:41, 3 June 2021 (UTC)

Is this a typo or a link change? Primefac (talk) 16:45, 3 June 2021 (UTC)
It’s a common historical mistake in dating that has been corrected in all main articles dealing with that dynasty, but remains uncorrected in hundreds or thousands of articles. --ExperiencedArticleFixer (talk) 16:49, 3 June 2021 (UTC)
Fair enough, though it's only 1211 pages. Primefac (talk) 16:54, 3 June 2021 (UTC)
Thank you! --ExperiencedArticleFixer (talk) 16:55, 3 June 2021 (UTC)
An editor making these changes may want to verify the dates. There is a bit of discussion here. There may be more. – Jonesey95 (talk) 17:15, 3 June 2021 (UTC)
Given the initial post was 2017 and the move in 2019, I'm thinking that there has been sufficient eyes to ensure accuracy.
I guess what I mean is, what sort of verification are you referring to? Primefac (talk) 17:17, 3 June 2021 (UTC)
BRFA filed, convo continues there. Primefac (talk) 17:25, 3 June 2021 (UTC)
I know that you know what you're doing, but when I implement a request like this, I just like to do a quick check to ensure that it won't have to be undone. You know, trust, but verify. – Jonesey95 (talk) 17:42, 3 June 2021 (UTC)
That's a fair point, and I've been a little quick to judge those who question me lately... might be time for a deep breath. Primefac (talk) 17:46, 3 June 2021 (UTC)

New pictures in a Commons category[edit]

I'm a marine biologist specialized in Echinodermata. I would like to be informed of any new picture of these animals so I can review the identification and, when useful, add them to the relevant Wikipedia articles. But as there are over 7000 species of the, of course I can't check all the categories every day. I used to benefit from Ogrebot's newsfeed for a long and useful time but it is no longer working. Do you guys know any other way I could get such uploading newsfeed ? Thanks and best regards, FredD (talk) 14:23, 8 June 2021 (UTC)

@FredD: What is your preferred way to be notified? Talk page message? User subpage that you have watchlisted? Ping on a user subpage? Notification? EpicPupper (he/him | talk, FAQ, contribs) 21:41, 9 June 2021 (UTC)
Hi. A user subpage would be good : here is how it worked with Ogrebot, it was doing well. Cheers, FredD (talk) 06:10, 10 June 2021 (UTC)
Hi, any news, EpicPupper ? Thx, FredD (talk) 19:53, 14 June 2021 (UTC)
@FredD: Still in the concept stage, but I'll try to hammer out something later this week. BTW, please ping me when replying, or else I might not be able to see the message :) 🐶EpicPupper (he/him | talk, FAQ, contribs) 20:10, 14 June 2021 (UTC)

mass linking and reffering[edit]

bot for linking stuff in wikipedia

FizzoXD (talk) 03:31, 9 June 2021 (UTC)

@FizzoXD: There isn't enough information in this request for anyone to be able to design a bot from it. "Linking stuff" could mean any number of things, and nearly all linking decisions are going to be context-dependent, which makes them bad tasks for a bot. If you do have some specific type of linking that can be performed universally, please expand on your request. Vahurzpu (talk) 05:00, 9 June 2021 (UTC)

By linking things i mean like linking to other wikipedia articles. Like if there is a word link "internet meme" the bot would like it to the page by editing it. FizzoXD (talk) 05:31, 9 June 2021 (UTC)

As indicated above, not only is this a WP:CONTEXTBOT issue, it's a WP:CONTEXT issue as well; we don't link every use of a term on every page that uses it. Primefac (talk) 11:47, 9 June 2021 (UTC)

Using tagbot to mark orphaned page[edit]

Some of the newly created pages are orphaned pages, but they have not been marked with orphaned templates, is tagbot that can do this?--q28 (talk) 08:44, 9 June 2021 (UTC)

@Q28:  Question: Is there already a bot that does this? This is definitely a task that can be done, but I want to make sure that it's not duplicated by another bot. 🐶 EpicPupper (he/him | talk, FAQ, contribs) 21:49, 14 June 2021 (UTC)

Cleanup of chronological data in NFL Draft tables[edit]

There are 298 list articles in Category:Lists of National Football League draftees by college football team. Of these, approximately 121 articles contain a table of records which are not in correct chronological order (they contain newer "2021" rows on top of older "19XX" rows).

Currently, all 121 articles in need of one-time cleanup contain sections with {{Chronological|sect=yes|date=June 2021}}. So that is potentially a hook to key off of.

There are two cases where automated cleanup should update the table to cause render in chronological order (oldest YYYY rows first, newest YYYY rows last, AND preserve the existing top-bottom sequence of rows within a given year's draft by Round/Pick/Overall ).

  1. List of Central Arkansas Bears in the NFL Draft#Selections - where there are no rowspans in the YYYY column. (Every year row has exactly 1 player selected)
  2. List of Central Michigan Chippewas in the NFL Draft#Selections - where there are some years with 2 or more players selected and the existing top-bottom sequence must be preserved. Ex, within the 2 "2019" rows, the "2 7 39 Sean Murphy-Bunting Tampa Bay Buccaneers DB" row must remain above the "6 22 195 Xavier Crawford Houston Texans DB" row. Same callout for 2010, 2007, 2005, etc.

Note, there might be a few per-article variations which do not use a section name of #Selections

Here are the other cases to consider, where no bot modification is desired:

  1. List of Ohio State Buckeyes in the NFL draft is a formatting outlier and no change is desired.
  2. List of Florida State Seminoles in the NFL Draft is a formatting outlier with multiple tables, but can be manually fixed (not in scope to this request).
  3. List of Penn State Nittany Lions in the NFL draft#Players is correctly sequenced, but without rowspans for players in the same YYYY Draft (there are no YYYY rowspans)
  4. List of Austin Peay Governors in the NFL Draft#Selections is in the correct chronological order AND without YYYY rowspans
  5. List of Amherst Mammoths in the NFL Draft#Selections is in the correct chronological order AND with YYYY rowspans

If this can be automated, I am happy to manually inspect all 298 articles and fix/revert any missed edge cases to stable where necessary. Updating these manually would be very slow and prone to error. The scope is unlikely to ever be done, even with WP:NFL project participation. So any automation would be an enormous time-saver and win. Cheers, UW Dawgs (talk) 23:41, 9 June 2021 (UTC)

Accepted @UW Dawgs: Could you please do a couple of things for me?
  • Drop a line onto WT:CFB to give chance for any other input, such as get confirmation that this is the desired direction of sorting, before a BRFA is filed.
  • Check that the sorted versions of the two tables you highlighted as examples appear correctly on User:William_Avery/Test_tablesort
Thanks, William Avery (talk) 14:01, 10 June 2021 (UTC)
Feedback from WP:CFB and WP:NFL projects
BRFA filed - It will be best to continue this discussion there.

WP:OVERCITE warning for draft articles submitted[edit]

As an AfC reviewer I come across many draft articles with a disproportional ratio of references to the prose text. A healthy number of such draft articles are on subjects that ultimately turn out to be notable, i.e. authored by newcomer editors with good intentions who are simply oblivious of WP:OVERCITE.

By developing and launching a bot that would show a warning notice for editors trying to submit a draft article triggering WP:OVERCITE filters, we would:

  1. Raise the awareness of newcomer good faith editors on citation rules and give them an opportunity to resolve the shortcomings in their draft;
  2. Contribute to a speedier resolution of the 4500+ AfC backlog by decreasing the number of reference-bloated drafts;
  3. Decrease the number of naive bad-faith editors bombarding drafts with references in hope that it will create an illusion of superficial appearance of notability.

Suggested filters that would trigger this notice could vary and be based on a community consensus. Examples of filters:

  1. There are two or more sentences or words with over 3 or more references;
  2. Disproportional ratio of references per X number of words in the article.

Example text for the notice: "It seems like your draft is using too many references. Please keep in mind that draft articles are not accepted based on the number of references provided. To the contrary, citation overuse can delay review or even be a reason for a decline. Please see WP:OVERCITE and consider editing your draft accordingly." nearlyevil665 06:24, 12 June 2021 (UTC)

I am noting here that WP:OVERCITE is an essay that contains the advice or opinions of one or more Wikipedia contributors. This page is not an encyclopedia article, nor is it one of Wikipedia's policies or guidelines, as it has not been thoroughly vetted by the community. Some essays represent widespread norms; others only represent minority viewpoints.
  • Since this is an essay & neither a policy or guideline, I question the need to enforce it.
  • It is unclear from the proposal whether this would apply only to drafts that have been submitted for approval. A plethora of citations might well be appropriate for a draft still in development.
  • I know that I always strive for a minimum of ten citations for biographical notability. I would hate to see a draft get warned for having too many citations in draft form then get nominated for deletion as an article when it has too few. It seems to me that the proposed bot should only apply when there is a minimum number of citations.
Peaceray (talk) 06:36, 12 June 2021 (UTC)
Hi, thanks for the input. I understand that WP:OVERCITE is technically an essay and your other reservations about BLPs. Let's go through them one by one:
  1. I agree this shouldn't be a nuisance for editors who have good intentions and are providing a proper set of references, especially for BLPs. This could be avoided through the following:
    1. Registered accounts could turn off this notification in their preferences;
    2. The filter would be triggered for blatant citation overkill, such as having over 5 references per a single word or sentence. Very rarely could a BLP with only two sentences possibly justify 10 in-line references between them;
  2. The proposal would apply only when editors try to submit the draft for review. A notification would come up (much like the blacklisted source warning) which the editor could override by simply hitting publish again.
  3. For your point about WP:OVERCITE being an essay, was an oversight on my part. I'm not well-versed enough around Wikipedia to say if that essay cannot be linked as recommended reading for newcomer editors.
nearlyevil665 06:58, 12 June 2021 (UTC)
I feel pretty strongly about having a minimum of 10 in-line references before the bot starts flagging them as WP:OVERCITE, even if they only two sentences. Let me give a scenario or two.
  1. A woman who has no Wikipedia article wins a Nobel Prize in physics.[1] Or a previously unknown colonel in a small African country's army, again with no Wikipedia article, becomes head of a government through a coup d'etat.
  2. A non-autoconfirmed editor immediately creates a stub in the draft namespace with ten in-line references from contemporary news sources. This editor submits it for promotions, then gets the WP:OVERCITE message, so the editor removes some of the references.
  3. An autoconfirmed editor, perhaps even the creating editor who now may have enough edits to be autoconfirmed, moves the draft into the article space so that Wikipedia
  4. A deletionist tags it with a {{Db-person}} speedy delete notice.
  5. A well-meaning administrator who has not read the news or is familiar with the field deletes the article.
I have been involved with article rescue before, & IMHO there are many deletionists who are trigger happy & who fail to do the due dilligence of performing a rudimentary search to see if someone is actually notable or not. Also, IMHO, a disproportionate of speedy deletion tags end up on women's articles.
I have also seen instances of administrators taking the speedy deletion tags at face value, rather than move an article into the draft namespace. I do not think I need to emphasize that it is more difficult to get an article created after it has been deleted.
While some may feel that I have described a hypothetical situation, I have been around long enough & have enough edits under my belt to assure you that the deletionist tagging & subsequent deletions are not isolated scenarios. It happens all the time.
In this regard, I strongly feel that the number of references that WP:BIO, the notability guideline, trumps the WP:OVERCITE essay. For that reason I will strongly oppose any bot that does not allow a minimum of ten in-line references before warning about WP:OVERCITE. Peaceray (talk) 20:51, 12 June 2021 (UTC)
It is now making sense to me too. I'd feel comfortable with a bot that'd get triggered to display the notice to the editor only after a certain threshold of in-line references has been cleared. Based on my experience with blatant citation overkill it's nearly always the extremes, e.g this Draft:Savannah St. Jean, so the bot would still technically perform its function with a minimum of 10 or 15 in-line references. It could, for example, pick up citation overkill in the linked draft by triggering two conditions: 1. Draft has over 10 in-line referenes 2. It has an unreasonable number of references for one particular paragraph (1 reference per every 4 words, for example, or multiple words with over 5 references). nearlyevil665 07:03, 13 June 2021 (UTC)
I am on board with that. Peaceray (talk) 20:14, 14 June 2021 (UTC)


  1. ^ Bazely, Dawn (2018-10-08). "Perspective - Why Nobel winner Donna Strickland didn't have a Wikipedia page". Washington Post. Retrieved 2021-06-12.
  • I am not at all OK with this.

There are many list type articles, or articles containing a bibliography, or scientific details, where a large number of citation is essentia, and it is the accepted practice in medical articles to give what would probably be considered an excessive number in any other field. Any notice that might lead to people removing such references would be giving exactly the wrong advice. There are however several real problems, but I do not see how they are capable of easy solution by bot.

(1)Multiple citations for the same point, especially when some of the references are copies of each other.
(2)inclusion of unnecessary references from low quality sources, or from non-independent sources
(3)Short articles where the references compose most of the article
(4)Reopeated references from the same source to multiple places in the same sentence.

I do not think articles are often declined on this reason alone; and if they are, it is incorrect, and should be brought to attention of the deleting editor or if necessary at Deletion Review. Rather, the inclusion of excess referencing is often a sign of promotional editing, or editing by a fan. It is bad style, and while it is neve correct to delete for style alone, bad style often indicates problems, and will certainly cause an article to be looked at carefully--perhaps even hyper-carefully. It's not currently concentrated on women; rather, a few years ago some of those running editathons and projects on undercovered areas were somewhat careless of ensuring that the articles written were of more than borderline notability . This did encourage the tendency of some editors with traces of misogeny to be over-critical in this area. But those running such projects have learned, and so have most of the misogynists. DGG ( talk ) 06:48, 16 June 2021 (UTC)

Add Archive URLs for Showbuzz Daily refs[edit]

Moved to WP:URLREQ#Add_Archive_URLs_for_Showbuzz_Daily_refs

Removal of spam links to[edit]

Moved to

Wikilink rename request[edit]

Please, rename "Stadio Pierluigi Penzo" to "Stadio Pier Luigi Penzo" in this pages. Thanks in advance!!! --2001:B07:6442:8903:D4D:F67B:CF18:C681 (talk) 13:36, 14 June 2021 (UTC)

Doing... I'll see what's appropriate (via AWB). 🐶EpicPupper (he/him | talk, FAQ, contribs) 20:11, 14 June 2021 (UTC)
Y Done 🐶EpicPupper (he/him | talk, FAQ, contribs) 20:27, 14 June 2021 (UTC)

Help needed[edit]

I'm not really sure what bot is involved with this but we have had ongoing problems with Category:AfC G13 eligible soon submissions. When things are running normally, it holds between 4,000 -5,000+ draft articles that are between 5 and 6 months since their last edit. When they hit 6 months without a human edit, they are deleted per CSD G13. Also, reviewers from AFC (particularly DGG) go through this category and "rescue" promising drafts and postpone their deletion and sometimes even move good drafts into main space.

What has happened this past year is that this category starts going down to 3,000 drafts, 2,000 drafts, 1,000 drafts and now it is only holding 478 expiring drafts. When this has happened in the past, I have asked ProcrastinatingReader for help and he has been able to do some technical task that causes the category to, over a few days, fill back up again. Right now though, he can't get to this task and advised me to come here and ask for help.

I have little information to offer beyond a description of the problem. I have no idea what bot or template categorizes these drafts or what ProcrastinatingReader did to fix this problem. I know that having categories filled has been an ongoing problem because I have brought the issue to the Village Pump and other individuals several times over the past few years. So, I'm not sure what the fix would be. If you could find a permanent solution, that would be awesome. Thank you. Liz Read! Talk! 02:20, 16 June 2021 (UTC)

Here is the list of pages that should have been in that category, which is no less than 4808 in number. If all those pages are purged, the category will fill up. But IMHO this seems like an artificial solution when the real solution would be to use the database report directly. The way this particular category is populated will always be really unreliable (since it relies on an edit not being made to the draft, which is the opposite of what attracts the attention of MW job queue). If people are relying on this exclusively to review old drafts, well, they're going to miss out on a lot. – SD0001 (talk) 11:49, 16 June 2021 (UTC)
Liz, If needed, we could have a bot dump the query that SD0001 gave (which is very similar to the one my bot uses for its G13 warnings) onwiki somewhere for people to review as they wish. firefly ( t · c ) 12:21, 16 June 2021 (UTC)
Well, whatever you did, it worked! Many thanks!
Personally, I rely on SDZeroBot's reports from SD0001 but to see expiring drafts, it involves going 7 days back into User:SDZeroBot/G13 soon's edit history and then sorting the page by date and time. This is no problem once you are used to it but I think AFC patrollers find it easier to use the Category:AfC G13 eligible soon submissions where the drafts that are expiring the soonest are at the top of the category and they can just scan the category. I know that SDZeroBot's reports are more complete than the category is which is why I use them. There is also a problems with using a 7 day old page history from SDZeroBot as you have to check the edit history of every draft to make sure there haven't been edits to the draft in the past 7 days which is not the case when using the category which removes drafts if they've been recently edited. I don't know how we'd make use of the query list as the pages aren't linked on this list.
I'm not sure of the technical stuff you mention but both the category & SDZeroBot's reports serve a purpose, it's useful to have a 30 day, 7 day and current day list of drafts that will be expiring soon. The 30 day category helps us know how many drafts are expiring in the coming month, the 7 day report helps AFC reviewers like DGG target promising drafts that are expiring soon and postpone their deletion and the current day list helps admins track drafts that are expiring today.
Is "purging" something that I or DGG can do? Or maybe we could adapt the Firefly bot to tag eligible drafts a month ahead of time when it posts its talk page notices? Liz Read! Talk! 19:57, 16 June 2021 (UTC)
I ideally would work at 30 days using the category , .but it's been months since I've been able to get that far. At the moment I working at 1-2 days and don't have any margin. The category page is supposed to be sorted by time, and usually it is, and I can work on about 1.5 to 2 days worth per day in the time i have for this -- if I don't find myself getting diverted and there's no emergency elsewhere on WP or in my real life. I agree with Liz that it's critical to have the entries linked to the drafts so pop-ups work. . DGG ( talk ) 05:22, 17 June 2021 (UTC)

Automatic lists of images in rejected or deleted drafts[edit]

When a draft is deleted images uploaded to Commons are not always checked and might be left to languish. Even if the images are acceptable they may be uncategorized.

To help with this I would request to have a bot automatically create a list of images in rejected (or deleted, if possible) drafts, with the following conditions:

  • Add to list if a rejected or deleted draft contains images that were uploaded by the draft creator.

Optional features:

  • Limit to new users (account less than 100 days old; it may take a while before a draft is checked).
  • If the image is already marked for deletion, include it in the list but mark it in someway.
  • If the uploader has previously deleted images highlight other images as possibly problematic.

I am bringing this here after comments in Wikipedia:Village pump (proposals)#Automatic lists of images in rejected or deleted drafts MKFI (talk) 19:54, 16 June 2021 (UTC)

Bulk XfD request[edit]

Please tag all of the following articles included in Wikipedia:Articles for deletion/List of names of European cities in different languages:

LaundryPizza03 (d) 21:27, 17 June 2021 (UTC)

LaundryPizza03, this request might be a better fit for WP:AWBREQ. Also, would it be a good idea to include your bulleted list of Wikilinks in the AFD, so that people know that those articles are included in the AFD? Just throwing out some ideas, hope this helps. –Novem Linguae (talk) 22:01, 17 June 2021 (UTC)

A bot to help maintain and identify inspiration articles[edit]

At the idea lab a while back, I floated the idea of identifying inspiration articles for a given page, GAs or FAs on similar topics that could serve as inspiration for helping get that page to a higher level, and got some positive feedback. Following some additional discussion on Discord the other day, I've created {{Inspiration page}}. I'd like bot (or maybe tool) help for two things:

  1. Maintenance, such that if an article is demoted, any pages using it have their banner removed.
  2. Identifying new pages where it would be helpful to add the banner. This could possibly be done by searching for pages that share a substantial number of categories/wikiprojects, but where one is FA and the other is C-class or below.

Let me know if this sounds feasible! {{u|Sdkb}}talk 03:12, 18 June 2021 (UTC)