Wikipedia talk:Article alerts/Feature requests

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Please use this page to request new features for AAlertbot, and suggestions to extend the scope of AAlertbot to additional workflows.

Click here to request a new feature.

Reboot of Article Alerts[edit]

After several months of inactivity, a new bot has been coded to replace User:ArticleAlertbot. See the bot request for approval for details. As this represent a total reboot of the project, all previous discussions have been archived under "ArticleAlertbot (old bot)" list just above. Headbomb {talk / contribs / physics / books} 22:19, 12 December 2010 (UTC)

FFD and PUF (and possibly other file) worklows[edit]

Gnome-emblem-default.svg   Implemented  (FFD)
Gnome-appointment-soon.svg   Proposal on hold  (PUF)

Filled by: Acather96

Time filed: 12:40, 21 December 2010 (UTC)

Description: Please could you implement reports for files? By that I mean FFD, PUF and also, when files are tagged for pseudo-speedy, when they have 7 days to fix a certain copyright problem. I think this would be really useful, as projects could save important images from deletion, when only a small amount of time is needed to resolve the issue. And as for PUF, project members may have specalist knowledge that could help with clarifying the copyright status. I think the implementation of FFD support also brings obvious benefits :) Thanks.


I don't see why not. The bot is still not finalized, so we're focusing on covering these and making sure they behave as they should. When that's done, we'll start adding new workflows. Headbomb {talk / contribs / physics / books} 13:00, 21 December 2010 (UTC)
None of the current files in either FFD or PUF have banners or categories that would put them as belonging to any project. —  HELLKNOWZ  ▎TALK 13:16, 21 December 2010 (UTC)
You're right, many projects do not tag images. However some do, or some may start to. Also, projects like WikiProject Albums and WikiProject Schools can use cats embedded in the Non-free licenses and FUR's. And even if the bot only does pick up a few image using project banners, its better than none. Thanks, Acather96 (talk) 17:00, 21 December 2010 (UTC)
I can use categories, but they have to be either be on file page xor file talk page. In any case, this is easily implementable. Just need some examples. —  HELLKNOWZ  ▎TALK 17:19, 21 December 2010 (UTC)
For example, Category:Album covers, Category:Video game logos, Category:Game developer logos, Category:Academic institution logos. I could go on, just mainly non-free cats, as free media should be on Commons anyway. Though please do still implement project banners :) Acather96 (talk) 06:30, 22 December 2010 (UTC)
I already have enough category examples :) I meant an example article put up for deletion by a project that has tagged/categorized it. —  HELLKNOWZ  ▎TALK 09:03, 22 December 2010 (UTC)
One more thing, with regards to MFD, I think that should be implemented, when you consider that some projects like WikiProject Australia have about 130+ project-class articles.Acather96 (talk) 06:38, 22 December 2010 (UTC)
MfD is now will be implemented. —  HELLKNOWZ  ▎TALK 09:03, 22 December 2010 (UTC)
I know that the Michigan State Highways Project has tagged all of its files. It's probably outside of the scope of the bot in the near future, but it would be very handy if the bot could report if a file is up for deletion on Commons. (The US Roads parent project has had two maps recently set up for deletion on Commons, and we didn't know about the second until it was deleted and removed from its article. It turned out to be a false alarm copyvio report.) Imzadi 1979  13:13, 22 December 2010 (UTC)
Please see Category:File-Class United States articles, which contains over 12,000 files :)Acather96 (talk) 17:11, 4 January 2011 (UTC)
The problem is not the lack if tagged article examples, but example of articles nominated for deletion that are also tagged. Anyway, File talk:Bankim.jpg File talk:Deet.png File talk:Ferrocene.png are now up for deletion and are also tagged. —  HELLKNOWZ  ▎TALK 18:25, 4 January 2011 (UTC)

Custom categories[edit]

Dialog-information on.svg   New proposal

Filled by: Headbomb

Time filed: 04:18, 6 March 2009 (UTC)

Description: Could the bot be extended include custom categories? For example say WP Chemistry is interested in monitoring a hypothetical what is covered by the "Chemist biography taskforce" (from the Biography banner) and "History of Chemistry taskforce" (from the History of Science banner). It would then add something like |extracats=Chemist biography articles, History of Chemistry taskforce articles" to the subscription template.


De-archived. —  HELLKNOWZ  ▎TALK 14:25, 21 December 2010 (UTC)

A parameter to simplify the output[edit]

Dialog-information on.svg   New proposal  (will implement)

Filled by: Skotywa

Time filed: 06:38, 31 December 2010 (UTC)

Description: A parameter to simplify the output

Comments: It would be great if we could add a parmeter that caused the output to be greatly simplified. The simplified output would just have the headings and a bulleted list of articles under each. No dates, no talk-edit-hist links, no last updated footer, no credits to the editors initiating the activity, but maybe still a link to the review page when appropriate. This new feature would make the bot's output potentially very useful/versitile for transclusion in various project/taskforce related templates. Thanks for considering this request.

Noted. Will implement this in the future. —  HELLKNOWZ  ▎TALK 10:10, 31 December 2010 (UTC)
Out of all of these, the dates should probably be kept. Headbomb {talk / contribs / physics / books} 05:21, 3 January 2011 (UTC)
I suppose I can imagine both cases with and without dates useful. If I implement one, the other is a simple mod. —  HELLKNOWZ  ▎TALK 10:43, 3 January 2011 (UTC)

Mergers and Splits[edit]

Dialog-information on.svg   New proposal

Filled by: Simply south (talk · contribs)

Time filed: 14:45, 4 May 2009 (UTC)


De-archived from Wikipedia_talk:Article_alerts/Feature_requests/Archive/Old/Unresolved#Splits_and_merges.

Could there be notices for proposed merges and and splits on articles? It would be useful to save having to notify at numerous places manually and that. It would be useful as it would in some cases more quikly notify project users and potential people involved on what's going on.


A significant ease should be that if on the article splits are proposed or merges, shouldn't people be notified of these? Simply south (talk) 21:37, 3 May 2009 (UTC)

I personally wouldn't mind having these notices. Currently WolterBot handle these, but I think splits and merge as different enough from cleanup to warrant being on the alerts. In the meantime, I suggest making a feature request (link is given above) so it gets lumped with the other requests and archive propely once tackled etc.... Headbomb {ταλκκοντριβς – WP Physics} 23:53, 3 May 2009 (UTC)
I don't think that proposed merges would be suitable for short-term alerts. They have a very significant backlog, actually more than 1 1/2 years. See Category:Articles to be merged. --B. Wolterding (talk) 20:58, 4 May 2009 (UTC)
Well I was thinking of a more "ticker-like" notice, where the bot picks up the new proposals, and if they don't get merged after the archive time, they are simply dropped from the alerts. And (depending on technical feasibility), the bot could report what got merged and what was chosen to be left as seperate articles, etc... It wouldn't reduce the backlog, but it would diminish the rate at which backlogs would build up, perhaps to the point that it would now be possible to clear the backlogs without being overwhelmed by the new entries.Headbomb {ταλκκοντριβς – WP Physics} 04:08, 5 May 2009 (UTC)
I also notice that the backlog isn't all that big. 1425 or so articles really isn't that much. And when you spread those over the 1500 or so projects... Headbomb {ταλκκοντριβς – WP Physics} 04:18, 5 May 2009 (UTC)
Also this is a bit different from the other cleanup categories, as more often than not involves a discussion (or at least that's my impression). It's not something long-term and vague like "expand" or "needs more refs". Headbomb {ταλκκοντριβς – WP Physics} 05:45, 21 May 2009 (UTC)
I think it would be good if each WikiProject was reminded (say, once per week) of all open merger proposals that fell within its scope . As I reader, I certainly find articles with open merger proposals to be disturbing; moreover, there is often merit to long-delayed proposals. A once-per week reminder might light some (much-needed) fires to fix this backlog problem. -- John Broughton (♫♫) 18:34, 2 June 2009 (UTC)

(outdent) The backlog is actually ~15.000 articles long (not 1425), see Category:Articles to be merged. It's in the top-15 of Wikipedia backlogs, so to speak. I personally think that the WolterBot reporting is completely appropriate. --B. Wolterding (talk) 23:45, 4 September 2009 (UTC)

I was about to propose that {{mergeto}} and {{mergefrom}} be added to the workflows covered. I think these are a different set of articles than Category:Articles to be merged. I think these are articles under consideration to be merged with current ongoing discussions that project members should be alerted about and the category you are pointing to is the one where merger discussions resulting in consensus to move have caused an article to be placed in a category of articles to be merged.--TonyTheTiger (t/c/bio/WP:CHICAGO/WP:LOTM) 02:25, 11 September 2009 (UTC)
Again, 15 K spread on 1.5K projects and taskforces is not that much (and yes, the distribution isn't uniform, some projects with have hundreds, others 5, and so on). That's still something of a different nature than the "add more refs" and "remove weasel words" type of cleanup. These need to be discussed and thus should be covered in the Alerts. Simply report the new merge proposals and those which have been resolved. Those without activity can be removed after the archive time is up. See my 04:08, 5 May 2009 (UTC) post above. Headbomb {ταλκκοντριβς – WP Physics} 07:58, 11 September 2009 (UTC)
End of de-archived section.
  • I strongly support this request. Although the backlog may be significant, the number of articles per project will be quite moderate. Also, I believe that this notification will help decreasing the backlog. Beagel (talk) 05:41, 17 January 2011 (UTC)

Endorsements noted. —  HELLKNOWZ  ▎TALK 19:49, 2 February 2011 (UTC)

It seems that this feature is not endorsed yet. Could you please go forward with this endorsement. Beagel (talk) 17:17, 20 July 2011 (UTC)
It's "endorsed" in the sense of the word that I have not forgotten about it. It's close to top on my very long todo list. The logic of the workflow is very easy. It's just that 14,182 pages take forever to correlate between projects. It's about a minute to parse 500 pages, so about 30 min to parse them all. That's longer than the whole bot run currently. I'm in the countryside now and on very slow internet, so I don't have a chance of making it work now. —  HELLKNOWZ  ▎TALK 17:58, 20 July 2011 (UTC)

I'm still interested in this feature, it might even help WP:MERGE reduce some of its backlog! Is there any chance it will be added? Jack (talk) 16:20, 11 March 2013 (UTC)

Agree. This feature would be greatly greatly appreciated, although given the large number of mergers at any one time in a project, initially only mergers proposed in the last month may need to be displayed. --LT910001 (talk) 13:21, 2 January 2014 (UTC)
Strong support for adding proposed merges to the article alerts to give these a higher visibility and help editors clean up merge backlogs.--Wolbo (talk) 17:11, 27 October 2014 (UTC)

Betterly and more intelligenterer media-related alerts[edit]

Dialog-information on.svg   New proposal

Filled by: Headbomb (talk · contribs)

Time filed: 10:04, 19 January 2011 (UTC)

Description: Several project do not tag important files related to their projects. So in addition to the usual "Check for banners present on (for example) File talk:Quark structure proton.svg", there should be a "super search mode" for everything in the File: namespace. What I mean by that is that AAlertbot should not only check for the banners present on File talk:Quark structure proton.svg, but also the banners present on all the talk pages of articles/pages that make use of File:Quark structure proton.svg. For this file, this would mean

So, the report for WikiProject Physics could read something like

if it is tagged directly. And something like

if it is not tagged directly.

I've omitted the "talk edit hist" links out of simplicity / laziness, but the jist of what I'm saying should have gotten through. Headbomb {talk / contribs / physics / books} 10:04, 19 January 2011 (UTC)


Copyvio/project intersect[edit]

Dialog-information on.svg   New proposal

Filled by: Novickas (talk · contribs)

Time filed: 18:40, 23 January 2011 (UTC)

Description: A 'confirmed copyvio'/project intersection - for example, those articles with talk pages tagged as Wikipedia:WikiProject Lithuania and listed in Category:Articles tagged for copyright problems. These are deleted after about a week if not addressed.


Thanks! I will add the copyvio workflows eventually. —  HELLKNOWZ  ▎TALK 18:57, 23 January 2011 (UTC)

  • This would be a great idea. We delete anywhere from a couple to a dozen articles every day that could be salvaged if people knew they needed to be. --Moonriddengirl (talk) 21:36, 1 April 2011 (UTC)
See also Category:Possible copyright violations and subcats. Headbomb {talk / contribs / physics / books} 21:23, 31 July 2012 (UTC)

Redirects for Discussion Workflow[edit]

Gnome-emblem-default.svg   Implemented  (Raw RfD)
Dialog-information on.svg   New proposal  (Target page parsing)

Filled by: Admrboltz (talk · contribs)

Time filed: 04:22, 29 January 2011 (UTC)

Description: Would it be possible to add the Redirects for Discussion workflow? --Admrboltz (talk) 04:22, 29 January 2011 (UTC)


I will add this when I get to additional workflow implementations. RfD was planned from start, but there was something weird about it that prevented a straight-forward implementation so I left it for future. —  HELLKNOWZ  ▎TALK 10:40, 10 February 2011 (UTC)

The workflow is now implemented. The issue is, however, that very few projects bother to tag the redirect pages. What needs to be done is to check where the page redirects to and additionally check what subscriptions the page belongs to based on the target page's banner/categories. Unfortunately, from MediaWiki perspective, redirect pages with {{rfd}} are no longer redirects, so the API call is a big complex, needing to retrieve the actual content and parse it. Which I might do in future. —  HELLKNOWZ  ▎TALK 10:02, 18 February 2011 (UTC)

GTC/FTC child article listing[edit]

Gnome-emblem-default.svg   Implemented
Dialog-information on.svg   New proposal

Filled by: H3llkn0wz (talk · contribs)

Time filed: 11:21, 20 February 2011 (UTC)

Description: List "child" articles for featured/good topic candidates. Unfortunately, many editors nominate with {{GTC}} and {{FTC}} and not {{GTCmain}} {{FTCmain}}. Just GAC were not listed before and missed a bunch of articles. But also listing GAC creates a mess of entries.


Tagged "child" article now group "under" the parent and don't take up entry space. Now need to detect non-tagged articles. —  HELLKNOWZ  ▎TALK 17:02, 20 July 2011 (UTC)

AfD !votes summary[edit]

Gnome-emblem-default.svg   Implemented  (participant count)
Gnome-emblem-default.svg   Implemented  (!vote count)
Gnome-emblem-default.svg   Implemented  (relists)
Dialog-information on.svg   New proposal  (problem tags)

Filled by: H3llkn0wz (talk · contribs)

Time filed: 10:10, 21 February 2011 (UTC)

Description: Implement a rudimentary AfD discussion !vote count updating each run. Helps see which AfDs may nee further input. This is also relevant to future implementing "relisted" check or any other info (canvassing/delsorting) in some way.


This is implemented as of 20 Feb run. The rules is a simple regex, that gives a little leeway to formatting and surrounding text. —  HELLKNOWZ  ▎TALK 10:10, 21 February 2011 (UTC)

I really don't like the vote count. Maybe number of participants would be better if trying to encourage additional input. --Starcheerspeaksnewslostwars (talk) 02:28, 22 February 2011 (UTC)
Number of participants is useful and planned (for all discussion workflows, in fact), if a bit hard to implement. I guess !vote count isn't really the ideal statistic and may not be seen as what it's intended for. —  HELLKNOWZ  ▎TALK 09:15, 22 February 2011 (UTC)
AAlertbot is very cool, but I agree with Starcheerspeeksnewslostwars. Number of editors of the page, number of edits to the page, size of the page would be fine. Шизомби (Sz) (talk) 23:15, 22 February 2011 (UTC)
I think number of participants is good enough. Maybe something like Participation: X registered, Y IPs, or Participation: X autoconfirmed, Y others, or similar. Headbomb {talk / contribs / physics / books} 23:39, 22 February 2011 (UTC)
Perhaps. What value does differentiating registered and IP users add? zШизомби (Sz) (talk) 23:52, 22 February 2011 (UTC)
If you have 3 autoconfirmed editors and 2 IPs/new editors, it doesn't really tell you much. If you have 3 autoconfirmed editors and 25 IPs/New editors, then you most likely have a meatpuppet campaign. Headbomb {talk / contribs / physics / books} 00:26, 23 February 2011 (UTC)
I rather prefer reporting issues when the AfD gets canvass/SPA/sock tags, rather than post IP vs. registered editor count. That is the same kind of separation as !vote count, which was brought up. So something like "(12 participants, off-site canvassing)" may be better. Anyway, I understand WP is all about discussion and not voting, so posting !votes may seem like headcounting. I guess the number of participants should raise awareness about neglected AfDs just as well as low !vote counts. —  HELLKNOWZ  ▎TALK 09:08, 23 February 2011 (UTC)
Yeah, but how would the bot detect what's off-site canvassing, what's meatpuppetry, sockpuppetry, etc... ? So that extreme (complexity) doesn't seem viable. On the other extreme (simplicity), "20 participants" can mislead people into thinking "Well, enough people participated, so I don't need to" if it's 1 autoconfirmed editor 10 IPs and 9 newly created accounts. X autoconfirmed / Y non-autoconfirmed seems the simplest way to give an accurate report on the situation, without running into various political correctness problems. Headbomb {talk / contribs / physics / books} 09:34, 23 February 2011 (UTC)
"when the AfD gets canvass/SPA/sock tags", where "tags" are manually placed tag by editors ({{Not a ballot}}, {{spa}}, and such); no very complex guessing/detection. I, personally, have no objection to counting editors (I did !vote count after all), I'm just concerned it will be brought up again. —  HELLKNOWZ  ▎TALK 10:14, 23 February 2011 (UTC)
It should now report the number of participants and if the AfD has been relisted. I am only checking the revision info and not the page content, so it will not be always accurate (nominator, relists and delsorts are counted as -1 to participants). The !vote count is now hidden in a {{tooltip}} surrounding the participant count.
Looks like this: (7 participants; relisted) So it hides the !vote count except to those that want to know. I don't really like the tooltip form, but I can't think of a better compromise for both showing and not showing the !votes. —  HELLKNOWZ  ▎TALK 09:57, 28 February 2011 (UTC)

Project pages listed in reports[edit]

Dialog-information on.svg   New proposal

Filled by: H3llkn0wz (talk · contribs)

Time filed: 10:13, 21 February 2011 (UTC)

Description: Should a project page enter a workflow, it should be reported too. This mostly affects RfC. Basically, project pages are not banner/category tagged; at least not the same as pages. They all do start with the same prefix, i.e. project name, which would make sub-page detection quite easy. —  HELLKNOWZ  ▎TALK 10:13, 21 February 2011 (UTC)


DYK workflow[edit]

Dialog-information on.svg   New proposal

Filled by: Piotrus (talk · contribs)

Time filed: 18:16, 2 October 2011 (UTC)

Description: With each nomination having its own subpage, I wonder if AA could cover DYKs now? Checking the talk page of all nominated articles should not be impossible. --Piotr Konieczny aka Prokonsul Piotrus| talk to me 18:16, 2 October 2011 (UTC)


Copied from Wikipedia talk:Article alerts#Covering did you knows.

I'll try to implement it soon. I'm not quite sure what the new syntax is. Apparently subpages are created under Template:Did you know nominations/ but the articles themselves don't get marked. —  HELLKNOWZ  ▎TALK 09:03, 4 January 2012 (UTC)


Dialog-information on.svg   New proposal

Filled by: Resident Mario (talk · contribs)

Time filed: 21:33, 20 October 2012 (UTC)

Description: Would it be possible to implement some sort of mail client on specific article alerts? I don't always have time for Wikipedia, but I do want to keep track of what's going on with my project, and I check my e-mail very often. Thanks, ResMar 21:33, 20 October 2012 (UTC)


Post single events onto talk pages[edit]

Dialog-information on.svg   New proposal

Filled by: Ahnoneemoos (talk · contribs)

Time filed: 03:26, 31 December 2012 (UTC)

Description: ability to post a single change into a talk page.

Comments: the bot would post in Wikipedia talk:WikiProject Puerto Rico every single change as a new section. For example, the bot would post the following wiki code on the project talk page:

==Article nominated for deletion: name_of_article==
The article [[name_of_article]] has been nominated for deletion. This is a post by a bot. ~~~~

We could also specify which changes we would like to be posted; something like:

| afd = yes
| rfc = no
I don't know if that's in the scope of the bot. I don't see why the alert page needs to be duplicated on the project talk page. That is usually for pressing matters and non-routine nomination, and the bot can't make that distinction. Surely anyone wanting those notifications can just follow the alerts page. —  HELLKNOWZ  ▎TALK 10:53, 31 December 2012 (UTC)
I didn't mean the whole alert page. I meant individual changes to be posted on a talk page. That way I can be notified through MediaWiki's New Talk message functionality rather than through a Watchlist (since I don't use the Watchlist feature). It's equivalent to receiving an email but within Wikipedia's system. —Ahnoneemoos (talk) 15:40, 31 December 2012 (UTC)
Oh, you mean like on a user (e.g. your) talk page? —  HELLKNOWZ  ▎TALK 16:14, 31 December 2012 (UTC)
Yes, a User talk page or a Project talk page. We can test it on User talk pages first (mine) if you want. We can also add thresholds so that the bot doesn't massive spam. Kinda like how MiszaBot works. See User:MiszaBot/Archive HowTo#Parameters explained; re: parameters minthreadsleft and minthreadstoarchive but within AAlertBot's context. —Ahnoneemoos (talk) 16:50, 31 December 2012 (UTC)
By the way, so that you understand the rationale behind this: we have had a historic problem at WikiProject Puerto Rico where people nominate articles for deletion and don't notify the Project, its contributors, nor the person that created the article (see [1] [2] [3] and [4] for examples). Notifying people is not required but nominators usually do it. This requested feature would help alleviate this issue and allow us to participate in AfDs and RFCs promptly. We are only interested in AfDs, proposed deletions, categories for discussion, templates for discussion, files for deletions, and requested moves. Featured candidates, Good article candidates, and Peer reviews are irrelevant for us. —Ahnoneemoos (talk) 17:11, 31 December 2012 (UTC)
But that ("people nominate articles for deletion and don't notify") is exactly why AAB exists -- so that there is a centralized page with only the relevant notices that everyone can watch. Also, you can filter which workflows you want (AfD, PROD, not FAC, etc.). See Wikipedia:Article_alerts/Subscribing#Choosing_workflows, you don't need to receive stuff you don't want. You can even set up multiple pages, each for different purposes. Also, I don't quite understand how you can get a new talk page message from project talk pages, I thought that ever only works with user talk pages? —  HELLKNOWZ  ▎TALK 17:37, 31 December 2012 (UTC)
No no no, what I'm requesting is that the bot posts on your User talk page in order to leverage the New Talk message feature. The configuration can be done on the User Talk page so that we know that the user itself chose to be notified on his talk page. Remember, the way the bot works today is through the Watchlist feature, which I'm trying to avoid. People have to watch a page so that they can see it changes. However, by allowing the bot to notify on a User talk page we avoid the watchlist feature. It is more intrusive, but it's setup by the user itself, knowing that he will be spammed. —Ahnoneemoos (talk) 17:56, 31 December 2012 (UTC)

TAFI article alert[edit]

Dialog-information on.svg   New proposal

Filled by: NickPenguin (talk · contribs)

Time filed: 20:20, 23 April 2013 (UTC)

Description: Today's articles for improvement is a weekly article improvement drive that is featured on the Main Page. Every Monday, a new collection of ten articles are displayed in a random rotation on the Main Page. I would request that this bot grab a list of all the articles tagged with WikiProject tags, and leave a message on the WikiProject's talk pages.


Leaving messages on talk pages is outside the scope of this bot, but we could in principle add TAFI to the reports of relevant projects. I'll check it out. —  HELLKNOWZ  ▎TALK 11:01, 24 April 2013 (UTC)

Categories for speedy deletion and renaming[edit]

I may be mistaken, but it appears that the bot does not send alerts for categories tagged with {{Db-c1}} (deletion) or {{Cfr-speedy}} (renaming). I assumed that these were listed under the Article Alerts section: Categories for discussion, but I think I was mistaken. If they are not listed I would like to request that the bot add these category flags to the alerts. Since some at CFD already believe as I did that Article Alerts already does this 1, 2 3, I think it would be a good idea. (talk) 21:43, 2 May 2013 (UTC)

Hi, thanks for request. The bot does not list any speedy deletions, because they are just that - speedy. They can be gone in minutes. The bot only deals with workflows that are fairly long and/or require community input. Speedies should do not require discussion, just a sanity check from the admin before deleting. And, more importantly, they are placed/removed way too often to have a reliable report once a day. It will clog the history/watchlist with changes that basically don't need any input (except for some rare controversial cases, but those shouldn't have been speedied to begin with). Most of the time, they will become redlinks, that non-admins cannot check in any way. —  HELLKNOWZ  ▎TALK 08:16, 3 May 2013 (UTC)
Thanks for the quick response. I completely understand the concern that the the reports should not be clogged with unnecessary and uncontroversial deletions and renames. So leaving out the speedy renames makes sense in that regard. The {{Db-c1}}, however, seems more akin to the {{Prod}} flag used on articles which is listed in the article alerts. It requires 4 days on the category and requests that anyone that opposes the deletion remove the flag or populate the category, much like {{Prod}}s requirement that the flag be removed or the issues fixed or it will be deleted. This of course requires that people be aware that it was {{tl|Db-C1))'d in the first place. This flag is not used for vandalism and such just empty categories. I would like to request that at least this one be added to the article alerts. Thanks for your help. (talk) 20:50, 3 May 2013 (UTC)
I'm not sure I see how db-c1 needs more attention than other cases. Empty categories that are not used for anything seem like a very straight-forward case where there shouldn't be any need to notify a broad community. PRODs are very commonly contested, speedies aren't meant to be. In fact, there was consideration initially whether PRODs should even be reported. So the only factor I see is that it is supposed to be tagged for 4 days. That's a quite arbitrary case, and I still don't think it's in the scope of AA. —  HELLKNOWZ  ▎TALK 22:02, 3 May 2013 (UTC)
Thanks for your attention to this. While it is of coarse true that unused categories that aren't needed is a straight-forward case for deletion. Categories are often emptied out, not because they are not needed but because a user intentionally or more likely unintentionally emptied the category by removing or changing categories on pages. Unlike pages, categories are not emptied by going to them but by changes to its member pages. I'll respect your decision either way. I originally thought I was just reporting an oversight but apparently not.
Since editors at CFD cite article alerts as a reason not to notify creators and other interested parties (i.e. wikiprojects) when categories are deleted, 1, 2 3 it may be beneficial to inform them that this is not always true. Thanks again for your help. (talk) 01:23, 4 May 2013 (UTC)

Multi-page move notifications[edit]

I noticed that the discussion at Talk:Anila#suggested move which affects the disambiguation page Anila (disambiguation) and which had a notification of the discussion on the other page on its talk page did not show up in the alerts for the disambiguation project Wikipedia:WikiProject Disambiguation/Article alerts. Is there a way such multi-page moves can be included where the different pages affected might involve various project? olderwiser 13:06, 25 September 2013 (UTC)

The problem with multi-moves is that the extra pages aren't actually tagged in any way. Like, if you had a multi-page CfD, you would put a template on each one. Instead, requested moves only appear on 1 page. So the bot could only see them way after it has started looking through individual pages for extra info. The bot could list the extra pages under the main page. But at that point in processing, it's not really plausible to add more full pages to reports (so that they would get reported for other projects). Only way would be to read all the RMs (~150) beforehand and add the extra pages that way. But then you have cases that some projects tagged all the pages, some of the pages, not tagged the main page, etc. So it's a mess, but I'll look into it. —  HELLKNOWZ  ▎TALK 13:25, 25 September 2013 (UTC)
User:RMCD bot already adds a notification to the affected pages (at least when the multi-page move request is properly formed). Perhaps User:Wbm1058 could have RMCD bot also add a template of some sort along with the notification that your alert mechanism would then be able to pick up? olderwiser 13:47, 25 September 2013 (UTC)
Sure, it would be easy to add a template to the notification of the discussion on the other page if that would help. I could probably limit addition of such a template to {{WPDAB}}-tagged pages, if that's what's wanted. But there's no mechanism for removing that template. Either instructions for removal would be added to WP:RMCI, some other bot would need to remove it, or the tag would sit on these pages "forever". {{Ping}} me if you have specific specs for the template that you want RMCD bot to add. Wbm1058 (talk) 14:36, 25 September 2013 (UTC)
I can work with that, although obviously there needs to be another bot then. The template/category would probably go on all pages though, not just DAB. I don't think any are notified at the moment, but if I'm correct there used to be a bot? —  HELLKNOWZ  ▎TALK 14:47, 25 September 2013 (UTC)
There is currently, and has always been, just one bot handling the requested moves process, user:RMCD bot, formerly handled by user:RM bot. Multi-moves notification has been in place for a long time, since before I took on support for this process. All pages listed in {{subst:move-multi}} requests after the first page have notifications like Talk:Anila (disambiguation)#Move discussion in progress posted on their talk pages, and these notifications remain there, as-is, "forever", unless they are manually edited by a closing admin or other editor. WP:RMCI is fairly complicated, and currently there are no instructions there to "close" these notifications. I've thought about how the RM closing process might be semi-automated, but that's long been back-burner. Perhaps a new template {{Move notification}} could be added to these multi-notifications, then a new algorithm could be added to RMCD bot, that, after it was done with its current processing, pulled up all transclusions of this new template and checked to see if the RM that they linked to was still open (i.e., "Is there still a {{requested move/dated|multiple=yes on Talk:Anila?"), and if not, then removed the new template. That may be doable. Wbm1058 (talk) 16:32, 25 September 2013 (UTC)
Thanks folks. It looks like there may be some hope. Although I'm primarily interested in disambiguation pages, I'd think that if there is a discussion on one page that also affects another page tagged with some other projects, that those other projects might be interested in the move (assuming of course they've subscribed to the alerts). olderwiser 19:59, 26 September 2013 (UTC)

See Wikipedia talk:Requested moves#Implied move of a DAB for a related discussion. Andrewa (talk) 01:11, 27 September 2013 (UTC)

Archive TFAs[edit]

Dialog-information on.svg   New proposal

Filled by: Czar (talk · contribs)

Time filed: 18:08, 7 October 2013 (UTC)

Description: I noticed that TFA listings aren't archived, and I didn't see any obvious reason why not.


They have different logic for getting the pages and different logic for when to show and remove them, so that's basically why. TFA isn't shown after the day, there is no "closed" version. So it doesn't ever reach the 2 week archive limit. Basically this was a nice to have announcement, but not a true workflow. I'll check how easy it is to do and add it to my pile of todos. —  HELLKNOWZ  ▎TALK 18:45, 7 October 2013 (UTC)

Pages or files listed at WP:NFCR[edit]

Dialog-information on.svg   New proposal

Filled by: Redrose64 (talk · contribs)

Time filed: 11:12, 29 November 2013 (UTC)

Description: Pages or files that get listed at WP:NFCR don't get a mention on Article Alerts. For example, File:Sensorites.jpg is listed at WP:NFCR#File:Sensorites.jpg, and File talk:Sensorites.jpg bears {{WikiProject Doctor Who}}, but the page is not listed on Wikipedia:WikiProject Doctor Who/Article alerts. Similarly, An Unearthly Child is shown at WP:NFCR#An Unearthly Child but is not listed at Wikipedia:WikiProject Doctor Who/Article alerts; however, File:Doctor Who and an Unearthly Child.jpg, which is one of the three images under discussion at WP:NFCR#An Unearthly Child, is listed on Wikipedia:WikiProject Doctor Who/Article alerts - but that's only because it's going through WP:FFD as well as WP:NFCR.


Yeah, NFCR doesn't get reported to AA. I guess I could add it alongside FFD. —  HELLKNOWZ  ▎TALK 12:24, 29 November 2013 (UTC)

Page curation[edit]

Dialog-information on.svg   New proposal

Filled by: Schwede66 (talk · contribs)

Time filed: 17:43, 22 January 2014 (UTC)

Description: I was wondering why Wikipedia:Page Curation isn't showing up in article alerts. Ok, I appreciate that new articles are generally lacking project tags, but some new pages do get tagged without the reviewer noticing the page curation link on the article page. I'm sure that editors who keep an eye on a Wikiproject would be interested in new pages. Schwede66 17:43, 22 January 2014 (UTC)


@Schwede66: Sorry, when I first saw the request, I didn't quite understand it, and then I totally forgot about it.

Can you explain, please, what exactly related to page curation are you saying should show up in article alerts? I know new pages often get tagged and deleted before projects even see them, but there aren't any good ways to reliably determine that projects want to see them. That's pretty much new article bot (don't remember it's latest incarnation's name). I already detect infoboxes for some projects and even parse manual delsorts, but most new pages still need manual banner tagging before can pick them up among all the other pages. What do you suggest? —  HELLKNOWZ  ▎TALK 22:25, 20 February 2014 (UTC)

Well, yes, there is the new article bot. What I'm thinking of is slightly different, though. I'm suggesting that articles be included in article alerts when the following conditions have been met:
  1. The article appears in Special:NewPages. I believe that feed includes pages created in the last month.
  2. The article is unreviewed, i.e. it is highlighted in yellow on that page, and has the link [Mark this page as patrolled] on the article page.
  3. The talk page has been tagged as belonging to the project that warrants its inclusion in article alerts.
This will create a much shorter list for editors than what the new article bot produces, as it requires project tagging. I for one don't bother with the new article bot as that bot just guesses which articles belong to a project based on key words, and depending on the key words chosen, there may be many false entries that do not belong to a project. So what I'm suggesting is to simply include the pages where all three conditions listed above are met. The heading could be 'Page curation', and the text could be: "The following new pages are unreviewed:" Schwede66 18:16, 21 February 2014 (UTC)

Speedy deletions with a grace period[edit]

Dialog-information on.svg   New proposal

Filled by: Redrose64 (talk · contribs)

Time filed: 21:33, 20 February 2014 (UTC)

Description: I see at #Categories for speedy deletion and renaming above that speedy deletions are not listed because they are often actioned within minutes. I'm aware that it can take up to 24 hours for a normal XfD to show in Article Alerts; but there are some speedy deletion criteria that are not for immediate action - there is a grace period. These criteria include most of those applicable to files, and a seven-day grace period is typical. See discussion at Wikipedia talk:WikiProject Doctor Who#Image removal(s) where a recent post of mine concerns a file deleted under WP:CSD#F7 twelve days after tagging. I'm sure that the WikiProject would have liked to have been notified about that impending deletion, so that a FUR could be prepared. --Redrose64 (talk) 21:33, 20 February 2014 (UTC)


My worry is that listing all the CSD, even only those with longer grace periods, will just crowd up the alert page, which is supposed to be for participation foremost. I know we have PRODs, so it's not excluded. But CSDs are not supposed to be discussed, they are a shortcut for users without the delete button (or experience to be 100% accurate). That said, whatever CSDs are supposed to be, these cases are 7-day timeouts and apparently pretty much same as PRODs but for files. I'll take a look at how many there are, and may be just integrate it with FFD list, may be as extra items, may be as a new workflow. —  HELLKNOWZ  ▎TALK 22:19, 20 February 2014 (UTC)

Add "In The News" candidate articles.[edit]

Dialog-information on.svg   New proposal

Filled by: Balaenoptera musculus (talk · contribs)

Time filed: 10:44, 9 May 2014 (UTC)

Description: Add "In The News" candidate articles.

Comments: "In The News" candidates are listed at WP:ITN/C using template {{ITN candidate}}.

It would be super-helpful if this bot were aware when articles were nominated on that page, so that editors with an interest in those articles (e.g. through a relevant WikiProject) could be alerted and have the chance to comment on the nomination and help to improve the relevant article before the link to it goes live on the Main Page.

It's my belief that this would improve the standard and participation level of discussion at WP:ITN/C and also improve the quality of articles linked in ITN.


Draft namespace[edit]

Dialog-information on.svg   New proposal

Filled by: Ritchie333 (talk · contribs)

Time filed: 08:50, 29 August 2014 (UTC)

Description: Provide a mechanism to list all draft pages whose talk page is tagged as belonging to a specific project.

The motivation for this feature is a report here written by Jodi.a.schneider (talk · contribs) that discusses the failings of Articles for creation. Adding alerts for new drafts in projects would help bring awareness of expert subject knowledge to potential new articles and satisfy the report's proposed design implications of Determine which drafts need collaboration and Recommend drafts to potential collaborators, based on both user interest and the likelihood of creating an encyclopedia article from a given draft.

Related discussions :


I could theoretically list pages, but most pages without any workflows are never accessed/retrieved. The bot uses an API similar to that, but joins a bunch more stuff together (it would take 1000s of queries otherwise). Nothing happens on pages without workflows, so all the logic ignores them for now (I don't even retrieve those page names). There are probably easier ways to generate a bare list.
A bigger question is what is "recommended"? AAB tries to be as objective as it can, as it deals with pretty contested areas. So it tries not to guess or make (many) assumptions. "All" pages is probably not a good list, and I am not aware of any other way drafts are tagged for special attention (that would also be more important than a bunch of yet-unimplemented workflow in mainspace). —  HELLKNOWZ  ▎TALK 18:53, 22 June 2015 (UTC)

Simplify output if there are no alerts[edit]

Dialog-information on.svg   New proposal

Filled by: Stevietheman (talk · contribs)

Time filed: 15:12, 24 September 2014 (UTC)

Description: Perhaps this requires a new parameter, but in the case of there being no alerts, I would like to have an empty result rather than a message "No Article alerts at this time." appear. This is because I use these alerts within a project alerts banner, and I would like the banner to not appear if there are no alerts. For this purpose, it's much more straightforward to check against an empty result than a formatted message.

Comments: Checking against a formatted messaged is not really hard. The following

{{#ifeq:{{page}}|No Article alerts at this time.|Output if there is no alerts|Output if there are alerts}}

or some variation of it should work. Headbomb {talk / contribs / physics / books} 15:29, 24 September 2014 (UTC)

That doesn't work as I've already tried to do something similar. The output is not simply the flat text "No Article alerts at this time.". It's easier to check against empty results. Stevie is the man! TalkWork 15:46, 24 September 2014 (UTC)

Monitor articles needing expert attention[edit]

Dialog-information on.svg   New proposal

Filled by: Amatulic (talk · contribs)

Time filed: 15:53, 19 October 2014 (UTC)

Description: Monitor categories that request attention from an expert, update alert notice when there is a change.

Comments: A new Category:Wine articles needing expert attention has recently been created. It would be nice if the page Wikipedia:WikiProject Wine/Article alerts currently being maintained by AAlertBot would be updated when articles appear in this category, which should happen when {{Expert-subject}} is added to a page with the parameter "wine".

Automatic delsort page parsing for matching projects[edit]

Dialog-information on.svg   New proposal

Filled by: Hellknowz (talk · contribs)

Time filed: 18:14, 22 June 2015 (UTC)

Description: Automatic delsorts.


Basically, parse all pages in Wikipedia:WikiProject Deletion sorting that match the name/project, e.g. "WikiProject Video games" and "WikiProject Deletion sorting/Video games". Instead of explicit |delsort=, everyone gets the delsorts. Optionally, can opt out with |nodelsort= or something. This could catch a good hundred+ pages that are otherwise untagged. Plenty of users are sorting stuff in delsorts as they go through AfDs, but not actually tagging the articles. —  HELLKNOWZ  ▎TALK 18:14, 22 June 2015 (UTC)

Smarter template redirect and report page[edit]

Dialog-information on.svg   New proposal

Filled by: Hellknowz (talk · contribs)

Time filed: 18:25, 22 June 2015 (UTC)

Description: Automatic template redirect retrieval, check, and report page

Comments: Currently all the template names are hard-coded as part of workflow definitions. After like 5 years, they are more than likely at least partially outdated with new redirects and old deleted ones. This needs unreliable manual updating and should be done automatically. Some on-wiki page that reports what templates it found and used would help see what the bot actually does. —  HELLKNOWZ  ▎TALK 18:25, 22 June 2015 (UTC)

On-site workflow settings[edit]

Dialog-information on.svg   New proposal

Filled by: Hellknowz (talk · contribs)

Time filed: 18:28, 22 June 2015 (UTC)

Description: On-site workflow settings

Comments: Store the settings on a page on-site as part of AA pages and read/parse/use it when running instead of hard-coding everything in code. Biggest concern is how easy it can be messed up, so would require a dev "sign-off" for changes (bot should report there's pending changes). Biggest code-site issue is that many pre-run options need this info, which implies we need a local cached settings version. —  HELLKNOWZ  ▎TALK 18:28, 22 June 2015 (UTC)

TfD holding cell[edit]

Dialog-information on.svg   New proposal

Filled by: Hellknowz (talk · contribs)

Time filed: 15:59, 26 June 2015 (UTC)

Description: Detect when the actual workflow is closed in a way other than pure cetegory. Problem is Category:Templates for deletion is including closed ones (to be merged, renamed, etc.), so it appears as open to the bot. See Wikipedia_talk:Article_alerts/Bugs#Closed_TfDs_not_being_removed.


Smarter insertion parsing[edit]

Dialog-information on.svg   New proposal

Filled by: Hellknowz (talk · contribs)

Time filed: 16:12, 26 June 2015 (UTC)

Description: Restore the text insertion revision parsing, with an error allowance (for vandalism, reverts, and such). That is, check a few revision deeper before accepting the result. Already had this working before lost source code.


Externalize messages[edit]

Dialog-information on.svg   New proposal

Filled by: Hellknowz (talk · contribs)

Time filed: 15:58, 27 June 2015 (UTC)

Description: All messages, like first report, no pages, etc. to external AA pages that can get substed, otherwise it's all hard-coded.


A subscribe button for the article alerts template[edit]

Dialog-information on.svg   New proposal

Filled by: Fixuture (talk · contribs)

Time filed: 15:24, 18 July 2015 (UTC)

Description: For the article alerts template (Template:Article alerts columns) I suggest a subscribe button that adds the displayed article alerts to ones watchlist. I think this would be very useful as it is not quite clear that article alerts can be subscribed to...even though that's the best way to stay up to date with those "alerts". Probably the best place to put it would be the "Updated daily by..."-row on the bottom of the template.


Most (if not all) AA pages already have a "Watch this alert page" link, see the last line of e.g. Wikipedia:WikiProject Greater Manchester/Article alerts. All that {{Article alerts columns}} does is take one of those pages and reformat it as three columns. Only the centre part of the AA page is transcluded, because the top and bottom parts are normally wrapped in <noinclude>...</noinclude>, and the "Watch this alert page" link is included in the bottom noincluded part (it's part of the {{Wikipedia:Article alerts/Report page footer}}).
It shouldn't be too difficult to do what you want, probably by adding e.g. {{watch|{{{1}}}}} to the second grey stripe (the "Updated daily by" one) in the {{Article alerts columns}} template. --Redrose64 (talk) 16:50, 18 July 2015 (UTC)
Thank you! I've seen the "Watch this alert page"-button there, however most people never go to article alert pages but instead just see them embedded via the template (most probably don't even know that it's an embedded separate page). So if there are no objections I'm going to try to work this out using your tips. Haven't done much with templates yet though, but I'll figure it out if people are ok with this suggestion and nobody else edits it the next few days or so. --Fixuture (talk) 17:05, 18 July 2015 (UTC)

G13 notification[edit]

Dialog-information on.svg   New proposal

Filled by: Ricky81682 (talk · contribs)

Time filed: 06:25, 18 August 2015 (UTC)

Description: For the WikiProjects that have added the Draftspace category (the default is drafts go into NA-class), I was wondering about a possible alert if the drafts become G13 eligible from there. It would possibly be triggered if the draft-space article was moved into Category:G13 eligible AfC submissions or better yet Category:AfC G13 eligible soon submissions. - Ricky81682 (talk) 06:25, 18 August 2015 (UTC)