Tutorial | Discussion |
New page feed |
Reviewers |
Curation tool Suggestions |
Coordination |
Any bug reports or suggestions for new features should be made at Phabricator using this form (or at the NPP reviewers discussion page). |
This is a list of required features to the Page Curation software since it was rolled out in 2012 but were not followed up, and more recent ideas (as well as bug fixes). Please add your own suggestions or comment on existing ones. |
This page in a nutshell: Some experienced, regular patrollers have from time to time made suggestions for useful and/or missing features and functions of the New Pages Patrol system. The effort is to make suggestions that will improve the way the Curation system works, and make it easier to use, but without adding unnecessary clutter and complexity to it. |
WP:ACTRIAL, a proposal to limit new page creation to autoconfirmed editors, was proposed in 2011 and influenced the creation of PageTriage.
PageTriage was created by the WMF in direct collaboration with some New Page Patrollers in 2012 as a feature-rich New Page Feed and Curation Tool to replace the much simpler 2006 patrolled edits feature that comes pre-installed on all wikis. This process was driven forward by Kudpung with help from Erik Moeller (WMF). The developers that created PageTriage were Kaldari and Bsitu.
In 2016, the new page patroller permission was created, limiting marking a page as reviewed to these editors (and to admins).
In 2018, the WMF Growth Team did some work on PageTriage, again in direct collaboration with some New Page Patrollers as part of Wikipedia:WikiProject Articles for creation/AfC Process Improvement May 2018. This resulted in ORES and Articles for Creation being added to the New Pages Feed. MMiller (WMF) was the product manager that helped implement this.
In 2019, after a large backlog of Phabricator tickets developed, NPP added Page Curation and New Pages Feed improvements to the Community Wishlist. It was voted #1, which helped to get the WMF Community Tech Team to add new features and to reduce the backlog of Phabricator tickets.
Except for these brief spurts of activity, the tool doesn't receive much technical support. As of 2022, we are making a renewed push to collect issues (bugs and required features), create Phabricator tickets, and convince developers to work on PageTriage. Wikipedia:New pages patrol/Coordination/2022 WMF letter received 444 signatures, possibly making it the largest open letter in the history of enwiki.
It has been suggested that Twinkle may be a workaround for some issues. However, Page Triage was expressly designed in 2012 to be a "one stop" tool to avoid switching back and forth between various menus, scripts, and gadgets.
Redirects converted to articles should be in the feed but indexed by the date of creation of the article, not of the redirect, and by the username of the creator of the article, not of the redirect.
When an article is created from a redirect the "was created by" data should be whoever created the article not the redirect. This both allows for correct filtering and also closes a loophole where a reviewer could reviewe their own articles. Best, Barkeep49 ( talk) 22:50, 24 January 2020 (UTC)
Perhaps more difficult: when an article is converted to a redirect and that action is then reverted, it should not appear in the New Page feed. : Noyster (talk), 11:36, 2 September 2016 (UTC)
Pages that have been tagged for maintenance issues (but not for deletion) andare otherwise just acceptable for inclusion, should be shown not with the green 'checked' icon, but with an orange blob that contains a capital T. It should be obvious that this would enable admins who are patrolling the quality of the patrollers themselves rather than new pages, can immediately revert any tags that have been inappropriately or erroneously applied, and replace them with correct ones or use the 'unreview button' which should then send the 'unreviewed' message automatically to the patroler, using a dropdown list of canned reasons. Kudpung กุดผึ้ง ( talk) 04:48, 4 September 2016 (UTC)
Include a button to optionally place a "welcome newbie" on a creator's talk page. First suggested by WereSpielChequers in 2012, this could offer a dropdown à la Twinkle of some of the more relevant wecome message templates. Kudpung กุดผึ้ง ( talk) 21:43, 7 September 2016 (UTC)
Barkeep49, can you follow up at Phab, because I don't have a clue what all their statuses mean. If it means that it has been put at the end of the 500+ tasks in waiting, we may have to make a new case for it in the next Wishlist. Kudpung กุดผึ้ง ( talk) 03:00, 13 September 2019 (UTC)
Reproducing here the original 2012 suggestion by WereSpielChequers: There are three bits of information that would be really useful to know re the previous articles created by the same editor. For badfaith editors who've had articles deleted G3 or G10 it would be really useful if their subsequent articles were highlighted in red on the screen so that people knew to check them first. For Goodfaith articles it would be useful to know how many articles someone has previously created, or at least to have a little prompt or filter for those who've done 50 or more so you can easily spot candidates for Autopatroller status. Also if you've just patrolled or tagged an article having the option "Look at x other unpatrolled articles by this author?. Kudpung กุดผึ้ง ( talk) 22:48, 7 September 2016 (UTC)
Would be technically complicated to implement. Would need a hook to listen for CSD taggings, and then an SQL table to keep count somewhere for each user. Can't use pagetriage_page_tags because that is per page. Can't use pagetriage_log because it only logs patrollers, not all users. Edge cases would include aliases of the CSD templates, and the case of untagging it instead of deleting it (false positive). – Novem Linguae ( talk) 17:05, 29 October 2022 (UTC)
Would be technically complicated to implement. Would need to track a user's article creation count (either using a hook, or an SQL query), and then store the data somewhere. As above, PageTriage doesn't have a table yet with the user as a primary key. An edge case would be deleted articles, which might not show up in the count depending on how it was implemented. – Novem Linguae ( talk) 17:08, 29 October 2022 (UTC)
Technically easy to implement. If this feature is requested by a couple people, let's make a ticket. – Novem Linguae ( talk) 17:09, 29 October 2022 (UTC)
Some people (generally older users) are still patrolling from Special:NewPages and Twinkle. As here is a delay in display time of the New Pages Feed (it is only refreshed when updated by the patroler), it would be useful if a 'T' icon could be displayed indicating that the article was already patrolled from the old feed. This would help recognise articles that are copy-and-paste creations. Kudpung กุดผึ้ง ( talk) 23:09, 7 September 2016 (UTC)
Mentioned several times around the site but first suggested here 13 December 2015 by czar. Kudpung กุดผึ้ง ( talk) 14:16, 8 September 2016 (UTC)
We will need to impress upon patrollers however that this feature should not be over used or as a get out for not knowing how to tag the article.
Move the page to Draft:articlename without leaving a redirect– this is technically impossible unless you are a page mover or admin. We could make it tag the redirect as WP:G6, though — MusikAnimal talk 23:02, 15 October 2016 (UTC)
I first mentioned this about a year ago; but it would be nice if, when NPP patrollers find an article that is decent and mark it patrolled without adding any clean up tags, there was an easy way to either nominate it for DYK or at least send a message to the contributor informing them of the existence of DYK as a showcase for their article. Actually nominating it might be a bit much because of the burden on the nominator to do a QPQ, but if we have new users contributing good content the opportunity to have their work showcased on the main page is incentive to continue contributing, and NPPers should be informing them of that possibility. ~ ONUnicorn( Talk| Contribs) problem solving 14:53, 9 September 2016 (UTC)
Together with Wikipedia:Page_Curation/Suggested_improvements#50._Proposing_Autopatrolled_for_user_creating_new_articles_of_a_very_high_quality, I have put these through as a request to be added to the 'Wikilove' section as templated options for High Quality Submissions. — Insertcleverphrasehere ( or here) 08:10, 19 October 2018 (UTC)
So that I don't have to wear out my finger pressing the accept button twice, and then advancing the next page. Wikipedia is not a video game, and if it is, controllers should be sent to all page patrollers for ease of use. L3X1 (distant write) 01:01, 10 April 2017 (UTC)
I would like one shortcut. Sometimes when reviewing redirects, I find a whole series created by the same editor and after checking several I determine that I am going to pass them all. I would like one-click review option. Perhaps SHIFT-click on the check button for "mark as reviewed and advance" or maybe CTRL-SHIFT-click to make if more difficult to do by accident. Alternatively, some way to review all articles in the (filtered) feed with one click would be even more efficient - but that would need to have a confirmation, something like "Are you sure you want to mark all 23 as reviewed?" MB 14:12, 18 October 2022 (UTC)
filter the content by a score that arbitrarily estimates public interest (pageviews x # of editors?) that way I would know that I would be spending time on the complicated judgement calls that count (I am an eventualist when it comes to backlogs: it doesn't really scare me that the backlog is massive, as long as the higher priority bits get taken care of first). I do article assessment for WikiProject Novels, and use the score filter, to prioritize which ones to assess of the multi-thousand article backlogs. This gives me the sense of hacking away at the relatively important, even if the backlog is never ending (for example, I would use this queue to pick the stubs that I would assess for relative importance to novels). Sadads ( talk) 22:29, 19 June 2017 (UTC)
I think it could it be very helpful if the Page Curation Tool could permit a patroller who has decided to review an article to then temporarily flag that page as being 'on hold', and for it to be automatically removed from the review list for, say, a period of 10 to 15 minutes. This should give a review enough time to do their work and would avoid a lot of overlaps and frustrating duplication of effort if it did. This seems to be quite a common experience at both the 'very recent' and the 'very old' end of the review list. By the time I've reviewed or tagged an article - and drafted helpful feedback for its creator - I commonly find another patroller has also reviewed that same page. I get the impression I'm not alone in experiencing these edit conflicts. If this is happening a lot, then it must not only be confusing for page creators, but is surely an inefficient use of limited volunteer resources, too. Is this a need perceived by others? Nick Moyes ( talk) 22:42, 8 June 2017 (UTC)
Include a ‘declined PROD/BLPPROD/CSD’ feature the choice of these messages.This would bring Curation in line with Twinkle and go a step further:
Hi. I’m just letting you know I have declined the CSD you placed on xxxxxxx because either it is either not covered by a criterion or this was not the approriate criterion. If you still feel the article should be deleted please use a different CSD rationale, or PROD it (recommended), or send it to AfD
Hi. I’m just letting you know I have declined the BLPPROD you placed on xxxxxxx because the article already has a link. If you still feel the article should be deleted please PROD it (recommended) or send it to AfD
Hi. I’m just letting you know I have replaced the PROD you placed on xxxxxxx with an appropriate CSD tag because the article is a clear case for speedy deletion.
Kudpung กุดผึ้ง ( talk) 01:03, 9 June 2017 (UTC)
Some editors still use Twinkle to record their CSD taggings and editors can only look at logs made by using Twinkle. I think adding this feature will be a good idea for most editors. KGirl (Wanna chat?) 22:15, 24 July 2017 (UTC)
Serious BLP violations, swrious spam, serious vandalism. Kudpung กุดผึ้ง ( talk) 13:34, 31 August 2017 (UTC)
The page curation list should show if a new page could have a potential COI issue or notability due to someone being a close subject. It should detect the tag or use a filter judging by things such as the username. Example a page created called "ExampleIncorporated" was made by a user called "JohnatExampleInc". A match program could be used to detect if a COI issue could be a problem with the page. AmericanAir88( talk) 02:22, 22 October 2018 (UTC)
The NewPagesFeed can get very long and require considerable effort to navigate to point in the queue that is not "newest" or "oldest". I would like an easier way to find unreviewed articles that I haven't seen yet. I often look through large numbers of articles to see if I note something that requires urgent attention. I also skip a lot of articles, especially when there are many on a topic where I would need to re-acquaint myself with subject-specific notability guidelines to review properly.
I would be able to navigate the NewPagesFeed faster if I could skip articles that I have already seen but for some reason decided not to review. That issue is most apparent in the curation toolbar, where the next button may take me to a a page I have already seen, but do not want to review. It can take a very long time to find articles that I am interested in reviewing by clicking next in the Curation Toolbar, and it can cause me to "get stuck" on a group of articles that remain in my queue. I then have to return to the NewPagesFeed, ignore the visited links (using a local CSS) scroll down to where I want to work, and continue with the Curation Toolbar from there. Eventualy, I keep returning to that same group of articles I do not want to review at that time.
I would like to see a new feature that allows me to see only those articles that I haven't seen yet. It does not require a change in the curation toolbar interface: clicking next always means skip this article; if I just reviewed it, it is also not shown to me again. The UI change that is required is an option box in the NewPagesFeed that lets me ignore those articles where I have clicked the next button. Call that "hide viewed" or "only show unseen" or something similar.
It would make my reviewing more efficient by facilitating a quick scan of unreviewed pages I have not seen yet, and selection of the ones I think need the most urgent attention. -- Vexations ( talk) 23:06, 22 October 2018 (UTC)
Thanks for the tip about the https://tools.wmflabs.org/nppbrowser/. I found the ability to search by keywords to be very helpful.
I don't see this functionality in the Special:NewPagesFeed. It does include AfC but seems to lack the functionality / view of tools.wmflabs.org/nppbrowser. Is there perhaps a way to have the same keyword search for AfC drafts? The current options are
It would seem to be fairly straightforward to add a "(_) drafts" option, but I'm not sure what would be involved. K.e.coffman ( talk) 18:14, 13 October 2018 (UTC)
Right now the feed relies on ORES related criteria for certain labels in the feed, eg SPAM, attack, etc. That's all well and good and we should keep making use of ORES' abilities. However, it might be nice, spurred on by recent discussion around adding a COI label, if the community had some ability to add its own labels, perhaps through tie ins to Edit Filters, so that development of this feature were not dependent on criteria that we have to go to the foundation to get updated/changed/etc. Best, Barkeep49 ( talk) 01:34, 26 July 2019 (UTC)
better COI detection toolwill be near-certainly this ORES-COI-model, for the integration of which, we (obviously) need to go back to WMF.
Scoring Platform Team is very understaffed with no dedicated product support.FWIW, since then, the team has got reduced even more and Halfaker has been mentioning of the need of a bigger budget, of late.
This has been copied over from Kudpung's writing here:
have been expecting something on the lines of:
Tagging, but leaving unreviewed: Thank you for creating xxxxxx. A reviewer has tagged the article as needing your attention before it can be accepted for indexing by search engines."
Tagging, but passing as patrolled: The standard message, with the message details completed by the reviewer.
A further idea: For all new articles passed as patrolled, a thank you template with a few (really just a few) links to help pages, the Teahouse, and 'Your first article'. Most of the new articles are created by new users and this would also help demonstrate that there are a humans behind Wikipedia.
Suggested responses:
1. New template: "Thank you for creating xxxxxx. A reviewer has tagged the article as needing your attention before it can be accepted for indexing by search engines.""
2. Template:Reviewednote-NPF
3. A new template that should automatically be sent when an article is passed as patrolled without further comment.
At present, on disambiguation (dab) pages the "Page info" symbol, , is covered by a little white "1" on a red square background, and the "Possible issues" section comments: "No citations - This page does not cite any sources." Since reference citations are not allowed on dab pages, it seems that there should be a way to sense the dab page and not specify a need for the citations. P.I. Ellsworth ed. put'r there 03:44, 23 December 2020 (UTC)
There are examples of this at the
Chicago Storm –
Bringing It Back –
Kill Devil Hill –
J Street (disambiguation) (dab) –
Formal semantics (disambiguation) (redirect) and
Lil Bit (disambiguation) (dab) pages.
P.I. Ellsworth
ed.
put'r there 03:48, 23 December 2020 (UTC)
After checking several dab pages, I see that the bar on the right side that holds the various icons sometimes no longer appears. So the solution was to remove that sidebar from the dab pages?
P.I. Ellsworth
ed.
put'r there 04:41, 29 January 2021 (UTC) 13:08, 12 February 2021 (UTC)
I propose that in the New Pages Feed, AfC drafts will also be able to be filtered by having no citations, having been previously deleted, created by new users, created by blocked users, etc., as opposed to just filtering them based on potential issues and ORES-given ratings. JJP...MASTER! [talk to] JJP... master? 22:30, 22 March 2021 (UTC)
My main use of the New Pages Feed involves filtering for Were previously deleted. At the moment these are highlighted in red as Previously deleted. Nowadays, however, a high proportion have been cycled from mainspace to Draft then back to mainspace (ideally with AfC eyes in between, but often not), which triggers this filter. It would be helpful if the Previously deleted text could be expanded to identify particular circumstances, for example:
Both of these would involve just file-exists tests based on the article title. A more ambitious option 3 would involve appending an icon alongside all Previously deleted texts, to allow the user to click through to a new tab showing Special:Log?page=XY so that the actual history of prior instances can be viewed.
Each or all of these changes could I think increase the effective scrutiny of articles recurring into mainspace. AllyD ( talk) 08:50, 18 November 2021 (UTC)
@ MPGuy2824 and Novem Linguae:. With the recent patch, the number in the footer now closely matches the number of unreviewed articles in the queue. Right now, I see the footer says 7 and the feed says 5. That is a minor difference due to the caching issue. No big deal. But the queue actually contains 48 unreviewed articles right now - there are another 43 with Prod tags. So the count in the footer doesn't actually match the review status (green check or not); it is actually the number of unreviewed articles that are not currently nominated for deletion. Do we want to "fix" that to make it technically accurate? On the other hand, there is nothing to do with those articles. Which number is picked up in {{ NPP backlog}} and the report/graph? Which number to we want to "publicize" as the queue size? — Preceding unsigned comment added by MB ( talk • contribs) 14:26, 20 October 2022 (UTC)
Since ACPERM was rolled out, 'Were created by newcomers (non-autoconfirmed users)' can be removed, because they no longer can anyway. Kudpung กุดผึ้ง ( talk) 21:41, 7 July 2022 (UTC)
Display 'Predicted class' and 'Potential issues' in the feed list by default and remove these options from the panel to reduce clutter and banner blindness.
Kudpung กุดผึ้ง ( talk) 21:41, 7 July 2022 (UTC)
Novem Linguae, coming back to
I am reminded of something
Kaldari (former WMF Head of Engineering) said a few years ago with a link to an external article: An abundance of user preferences, however, can lead to
decision fatigue. So it's important to only provide preferences that will actually be used.
[4]
It is indeed something I was taught at uni in Berlin 36 years ago on a lecture called Qual der Wahl. I think we should open a ticket on this or perhaps you can write a patch yourself.
Kudpung กุดผึ้ง (
talk) 11:15, 17 July 2022 (UTC)
After reviewing one article/redirect, I often want to see others created by the same user. In the filters, there is the choice to specify a username. It is a bit arduous to copy/paste the username into this field. I would like another option (probably to the right of the user name box) that if checked, will fill in the field with the username from my last patrol. Comments? MB 04:19, 11 July 2022 (UTC)
It would be good if the edit summaries for articles when adding an AfD tag could mimic Twinkle and read "Afd: Nominated for deletion; see Wikipedia:Articles for deletion/NominationName" - ditto RfD, MfD, etc.
Make it optional to post the message to the talk page. Some messages are appropriate for the creator only. I'm not as prolific nowadays as many reviewers, but I do find very often that I don't want the message posted to the talk page especially when I'm offering advice to a new user which I do quite often. If posting the message to the talk age is opional, perhaps more reviewers would leave a message of advice or encouragement for the creator. Kudpung กุดผึ้ง ( talk) 02:57, 23 July 2022 (UTC)
This edit shows a tag added before the {{ short description}}, which is out of order per WP:ORDER. This is really minor and makes no real difference, but would be moved by AWB, so better to put in the right place to begin with. MB 15:33, 2 August 2022 (UTC)
I'm not sure at what point this would occur but I'm of the mind that once an article is added to the NPP queue, a TP should automatically be created with header and relevant WikiProjects listed in the banner, if it doesn't already have one. By doing so, some of the project teams can help with article clean-up instead of leaving that chore for NPP. Atsme 💬 📧 20:10, 22 August 2022 (UTC)
...not sure it'd be fair to require that of autopatrollers
, I beg to differ,
NL. Like
Atsme I've always been convinced that the talk page shoud be processed at the point of creation. While there's an excuse for newbies, an autopatroller is generally expected to produce 100% complete articles (except for eventual future expansion). At least that's what I do and I'm rather proud of it. Or am I wasting my time making clean articles? Not that anyone bothers to read them so it's not even leading by example - unless I link to them when I'm teaching others. Having a tool for NPPers to do it would be handy, but I don't think it's high on the priorities until at least the PageTriage codebase has been rewritten.
Kudpung กุดผึ้ง (
talk) 03:57, 27 August 2022 (UTC)
Since AFDed articles can be marked as reviewed with just a quick check that there is a valid deletion discussion, it would be handy to find easily find these. The page feed has the option "Nominated for deletion", but that includes CSD & PROD. I just went through all those and found around 60, and about 2/3s were AFD meaning I had to skip through 20 others. It would be more convenient to be able to filter on just AFDs (don't see a reason to need only CSD or only PROD). MB 20:02, 25 August 2022 (UTC)
Autopatrolled articles are becoming increasingly problematic - either that or we are getting a bit better at serendipitously finding them. Alreadty the Autopatrolled righ has been removed from the Admin privileges.
Keep 'from Autopatrolled' in the filter options but:
This would inform the reviewers of any issues and leave them to take a closer look at their discretion. Kudpung กุดผึ้ง ( talk) 02:50, 14 September 2022 (UTC)
which incidentally doesn't seem to work at the moment. Did you try ticking the check box for "State: Reviewed"? That needs to be paired with the autopatrolled filter for it to display results. Hope that helps. – Novem Linguae ( talk) 13:54, 15 September 2022 (UTC)
OK. So that works now, but still needs my suggested red alert in the feed, otherwise there's no point in having the radio button 'Were created by autopatrolled users' at all. As this only affects the work of reviewers and is only visible to them, a site-wide or any other RfC is superfluous. As I said earlier, we don't need consensus for every minor improvement to the GUI of a specialised tool. Believe me, if I knew how to do it I would boldly do it myself as I have many other things in the past (and recently) on templates and tools. We can refine the selection options further, and how they are displayed in the filter panel, but at least let's discuss it rather than ruling it out - I'm not one for making usage suggestions just for the sake of it.
We're all agreed that to save NPP we need to start thinking outside the box, and streamlining the work is part of making NPP sexy enough for editors to want to do it. That said, I'm not ignoring the fact that a lot of articles and redirects are created by autopatrollers and it is a help not to have to review them (generally), but we are well aware that it is abused and even by admins - that's why it was removed recently from the admin toolset. Kudpung กุดผึ้ง ( talk) 00:30, 16 September 2022 (UTC)
@ MB, Novem Linguae, and MPGuy2824:. Proposed here. --Kudpung
When all or a very large proportion of an article's content is overwritten with new material, the article should be marked as unpatrolled and added to the NPR queue. This is virtually creation of a new article, but can be done by IPs and new accounts, and is often a sign of conflict-of-interest editing : Noyster (talk), 11:03, 16 January 2018 (UTC)
Thank you for creating xxxxxx. Your article has been passed by a New Page Reviewer. If you have any questions don't hesitate to ask at the Teahouse
This lets the creator know that s/he is not an island, and it serves to let them know that their work has been noticed. Just one of those nice little things that no one has ever thought of. Kudpung กุดผึ้ง ( talk) 12:11, 18 October 2022 (UTC)
I'm fairly certain this used to exist, but maybe it's wishful thinking. There are plenty of cases where a reviewer might message the creator without wanting to mark the page as reviewed. For example, by the time the next reviewer arrives, the creator may have addressed the issue. In any case, it will warn the reviewer that the creator has already been messaged.
See the example of the added alert in red.
As an extension to this feature - but on the 'Mark as reviewed' pane, apparently creators get a notification when their article has been reviewed, but are they automatically informed if a successful review is also accompanied by some tags on the article? The tags might not be a deal breaker for a review, but they are there because they nevertheless need to be addressed. Kudpung กุดผึ้ง ( talk) 09:59, 23 October 2022 (UTC)
According to this quarry, the top-10 most commonly used tags are (in descending order): notability, stub, refimprove, one source, orphan, linkrot, unreferenced, uncategorized, copy edit and primary sources.
The 'common' section of the toolbar has the following tags: under review, linkrot, copy edit, more footnotes, refimprove, unreferenced, stub, uncategorized and orphan.
I'm not sure about 'under review', but we should remove "more footnotes" and add "notability (General)", "one source" and "primary sources" to the common section of the toolbar. - MPGuy2824 ( talk) 04:28, 29 November 2022 (UTC)
Note: This discussion is now moot, since the common tags have been removed. -
MPGuy2824 (
talk) 07:20, 3 December 2023 (UTC)
As I've patrolled the New Pages Feed, I noticed that most of the time if a page is marked as having previously been deleted, it was deleted under one of the redirect criteria, an RfD (and the new page is not a redirect), or G7. I think that the New Pages Feed should ignore these deletions and not mark that the page was previously deleted if it were under these criteria (unless its a redirect and it was deleted under an RfD or R crtieria), as often these deletion have no merit on whether or not the page should remain. As an example, Kenangan Masa is marked as previously deleted because it was a page that was moved to draftspace and the redirect was deleted under R2. The deletion has no merits on the actual article itself since it was unrelated to the article content. ― Blaze Wolf TalkBlaze Wolf#6545 13:53, 10 May 2023 (UTC)
Is there a preferences panel to allow the Page Curation toolbar to track PROD, XfD, and CSD like Twinkle does, and like MoveToDraft allows? Am I missing this somewhere? If not, can it be added? microbiologyMarcus ( petri dish• growths) 21:24, 29 November 2023 (UTC)
Tutorial | Discussion |
New page feed |
Reviewers |
Curation tool Suggestions |
Coordination |
Any bug reports or suggestions for new features should be made at Phabricator using this form (or at the NPP reviewers discussion page). |
This is a list of required features to the Page Curation software since it was rolled out in 2012 but were not followed up, and more recent ideas (as well as bug fixes). Please add your own suggestions or comment on existing ones. |
This page in a nutshell: Some experienced, regular patrollers have from time to time made suggestions for useful and/or missing features and functions of the New Pages Patrol system. The effort is to make suggestions that will improve the way the Curation system works, and make it easier to use, but without adding unnecessary clutter and complexity to it. |
WP:ACTRIAL, a proposal to limit new page creation to autoconfirmed editors, was proposed in 2011 and influenced the creation of PageTriage.
PageTriage was created by the WMF in direct collaboration with some New Page Patrollers in 2012 as a feature-rich New Page Feed and Curation Tool to replace the much simpler 2006 patrolled edits feature that comes pre-installed on all wikis. This process was driven forward by Kudpung with help from Erik Moeller (WMF). The developers that created PageTriage were Kaldari and Bsitu.
In 2016, the new page patroller permission was created, limiting marking a page as reviewed to these editors (and to admins).
In 2018, the WMF Growth Team did some work on PageTriage, again in direct collaboration with some New Page Patrollers as part of Wikipedia:WikiProject Articles for creation/AfC Process Improvement May 2018. This resulted in ORES and Articles for Creation being added to the New Pages Feed. MMiller (WMF) was the product manager that helped implement this.
In 2019, after a large backlog of Phabricator tickets developed, NPP added Page Curation and New Pages Feed improvements to the Community Wishlist. It was voted #1, which helped to get the WMF Community Tech Team to add new features and to reduce the backlog of Phabricator tickets.
Except for these brief spurts of activity, the tool doesn't receive much technical support. As of 2022, we are making a renewed push to collect issues (bugs and required features), create Phabricator tickets, and convince developers to work on PageTriage. Wikipedia:New pages patrol/Coordination/2022 WMF letter received 444 signatures, possibly making it the largest open letter in the history of enwiki.
It has been suggested that Twinkle may be a workaround for some issues. However, Page Triage was expressly designed in 2012 to be a "one stop" tool to avoid switching back and forth between various menus, scripts, and gadgets.
Redirects converted to articles should be in the feed but indexed by the date of creation of the article, not of the redirect, and by the username of the creator of the article, not of the redirect.
When an article is created from a redirect the "was created by" data should be whoever created the article not the redirect. This both allows for correct filtering and also closes a loophole where a reviewer could reviewe their own articles. Best, Barkeep49 ( talk) 22:50, 24 January 2020 (UTC)
Perhaps more difficult: when an article is converted to a redirect and that action is then reverted, it should not appear in the New Page feed. : Noyster (talk), 11:36, 2 September 2016 (UTC)
Pages that have been tagged for maintenance issues (but not for deletion) andare otherwise just acceptable for inclusion, should be shown not with the green 'checked' icon, but with an orange blob that contains a capital T. It should be obvious that this would enable admins who are patrolling the quality of the patrollers themselves rather than new pages, can immediately revert any tags that have been inappropriately or erroneously applied, and replace them with correct ones or use the 'unreview button' which should then send the 'unreviewed' message automatically to the patroler, using a dropdown list of canned reasons. Kudpung กุดผึ้ง ( talk) 04:48, 4 September 2016 (UTC)
Include a button to optionally place a "welcome newbie" on a creator's talk page. First suggested by WereSpielChequers in 2012, this could offer a dropdown à la Twinkle of some of the more relevant wecome message templates. Kudpung กุดผึ้ง ( talk) 21:43, 7 September 2016 (UTC)
Barkeep49, can you follow up at Phab, because I don't have a clue what all their statuses mean. If it means that it has been put at the end of the 500+ tasks in waiting, we may have to make a new case for it in the next Wishlist. Kudpung กุดผึ้ง ( talk) 03:00, 13 September 2019 (UTC)
Reproducing here the original 2012 suggestion by WereSpielChequers: There are three bits of information that would be really useful to know re the previous articles created by the same editor. For badfaith editors who've had articles deleted G3 or G10 it would be really useful if their subsequent articles were highlighted in red on the screen so that people knew to check them first. For Goodfaith articles it would be useful to know how many articles someone has previously created, or at least to have a little prompt or filter for those who've done 50 or more so you can easily spot candidates for Autopatroller status. Also if you've just patrolled or tagged an article having the option "Look at x other unpatrolled articles by this author?. Kudpung กุดผึ้ง ( talk) 22:48, 7 September 2016 (UTC)
Would be technically complicated to implement. Would need a hook to listen for CSD taggings, and then an SQL table to keep count somewhere for each user. Can't use pagetriage_page_tags because that is per page. Can't use pagetriage_log because it only logs patrollers, not all users. Edge cases would include aliases of the CSD templates, and the case of untagging it instead of deleting it (false positive). – Novem Linguae ( talk) 17:05, 29 October 2022 (UTC)
Would be technically complicated to implement. Would need to track a user's article creation count (either using a hook, or an SQL query), and then store the data somewhere. As above, PageTriage doesn't have a table yet with the user as a primary key. An edge case would be deleted articles, which might not show up in the count depending on how it was implemented. – Novem Linguae ( talk) 17:08, 29 October 2022 (UTC)
Technically easy to implement. If this feature is requested by a couple people, let's make a ticket. – Novem Linguae ( talk) 17:09, 29 October 2022 (UTC)
Some people (generally older users) are still patrolling from Special:NewPages and Twinkle. As here is a delay in display time of the New Pages Feed (it is only refreshed when updated by the patroler), it would be useful if a 'T' icon could be displayed indicating that the article was already patrolled from the old feed. This would help recognise articles that are copy-and-paste creations. Kudpung กุดผึ้ง ( talk) 23:09, 7 September 2016 (UTC)
Mentioned several times around the site but first suggested here 13 December 2015 by czar. Kudpung กุดผึ้ง ( talk) 14:16, 8 September 2016 (UTC)
We will need to impress upon patrollers however that this feature should not be over used or as a get out for not knowing how to tag the article.
Move the page to Draft:articlename without leaving a redirect– this is technically impossible unless you are a page mover or admin. We could make it tag the redirect as WP:G6, though — MusikAnimal talk 23:02, 15 October 2016 (UTC)
I first mentioned this about a year ago; but it would be nice if, when NPP patrollers find an article that is decent and mark it patrolled without adding any clean up tags, there was an easy way to either nominate it for DYK or at least send a message to the contributor informing them of the existence of DYK as a showcase for their article. Actually nominating it might be a bit much because of the burden on the nominator to do a QPQ, but if we have new users contributing good content the opportunity to have their work showcased on the main page is incentive to continue contributing, and NPPers should be informing them of that possibility. ~ ONUnicorn( Talk| Contribs) problem solving 14:53, 9 September 2016 (UTC)
Together with Wikipedia:Page_Curation/Suggested_improvements#50._Proposing_Autopatrolled_for_user_creating_new_articles_of_a_very_high_quality, I have put these through as a request to be added to the 'Wikilove' section as templated options for High Quality Submissions. — Insertcleverphrasehere ( or here) 08:10, 19 October 2018 (UTC)
So that I don't have to wear out my finger pressing the accept button twice, and then advancing the next page. Wikipedia is not a video game, and if it is, controllers should be sent to all page patrollers for ease of use. L3X1 (distant write) 01:01, 10 April 2017 (UTC)
I would like one shortcut. Sometimes when reviewing redirects, I find a whole series created by the same editor and after checking several I determine that I am going to pass them all. I would like one-click review option. Perhaps SHIFT-click on the check button for "mark as reviewed and advance" or maybe CTRL-SHIFT-click to make if more difficult to do by accident. Alternatively, some way to review all articles in the (filtered) feed with one click would be even more efficient - but that would need to have a confirmation, something like "Are you sure you want to mark all 23 as reviewed?" MB 14:12, 18 October 2022 (UTC)
filter the content by a score that arbitrarily estimates public interest (pageviews x # of editors?) that way I would know that I would be spending time on the complicated judgement calls that count (I am an eventualist when it comes to backlogs: it doesn't really scare me that the backlog is massive, as long as the higher priority bits get taken care of first). I do article assessment for WikiProject Novels, and use the score filter, to prioritize which ones to assess of the multi-thousand article backlogs. This gives me the sense of hacking away at the relatively important, even if the backlog is never ending (for example, I would use this queue to pick the stubs that I would assess for relative importance to novels). Sadads ( talk) 22:29, 19 June 2017 (UTC)
I think it could it be very helpful if the Page Curation Tool could permit a patroller who has decided to review an article to then temporarily flag that page as being 'on hold', and for it to be automatically removed from the review list for, say, a period of 10 to 15 minutes. This should give a review enough time to do their work and would avoid a lot of overlaps and frustrating duplication of effort if it did. This seems to be quite a common experience at both the 'very recent' and the 'very old' end of the review list. By the time I've reviewed or tagged an article - and drafted helpful feedback for its creator - I commonly find another patroller has also reviewed that same page. I get the impression I'm not alone in experiencing these edit conflicts. If this is happening a lot, then it must not only be confusing for page creators, but is surely an inefficient use of limited volunteer resources, too. Is this a need perceived by others? Nick Moyes ( talk) 22:42, 8 June 2017 (UTC)
Include a ‘declined PROD/BLPPROD/CSD’ feature the choice of these messages.This would bring Curation in line with Twinkle and go a step further:
Hi. I’m just letting you know I have declined the CSD you placed on xxxxxxx because either it is either not covered by a criterion or this was not the approriate criterion. If you still feel the article should be deleted please use a different CSD rationale, or PROD it (recommended), or send it to AfD
Hi. I’m just letting you know I have declined the BLPPROD you placed on xxxxxxx because the article already has a link. If you still feel the article should be deleted please PROD it (recommended) or send it to AfD
Hi. I’m just letting you know I have replaced the PROD you placed on xxxxxxx with an appropriate CSD tag because the article is a clear case for speedy deletion.
Kudpung กุดผึ้ง ( talk) 01:03, 9 June 2017 (UTC)
Some editors still use Twinkle to record their CSD taggings and editors can only look at logs made by using Twinkle. I think adding this feature will be a good idea for most editors. KGirl (Wanna chat?) 22:15, 24 July 2017 (UTC)
Serious BLP violations, swrious spam, serious vandalism. Kudpung กุดผึ้ง ( talk) 13:34, 31 August 2017 (UTC)
The page curation list should show if a new page could have a potential COI issue or notability due to someone being a close subject. It should detect the tag or use a filter judging by things such as the username. Example a page created called "ExampleIncorporated" was made by a user called "JohnatExampleInc". A match program could be used to detect if a COI issue could be a problem with the page. AmericanAir88( talk) 02:22, 22 October 2018 (UTC)
The NewPagesFeed can get very long and require considerable effort to navigate to point in the queue that is not "newest" or "oldest". I would like an easier way to find unreviewed articles that I haven't seen yet. I often look through large numbers of articles to see if I note something that requires urgent attention. I also skip a lot of articles, especially when there are many on a topic where I would need to re-acquaint myself with subject-specific notability guidelines to review properly.
I would be able to navigate the NewPagesFeed faster if I could skip articles that I have already seen but for some reason decided not to review. That issue is most apparent in the curation toolbar, where the next button may take me to a a page I have already seen, but do not want to review. It can take a very long time to find articles that I am interested in reviewing by clicking next in the Curation Toolbar, and it can cause me to "get stuck" on a group of articles that remain in my queue. I then have to return to the NewPagesFeed, ignore the visited links (using a local CSS) scroll down to where I want to work, and continue with the Curation Toolbar from there. Eventualy, I keep returning to that same group of articles I do not want to review at that time.
I would like to see a new feature that allows me to see only those articles that I haven't seen yet. It does not require a change in the curation toolbar interface: clicking next always means skip this article; if I just reviewed it, it is also not shown to me again. The UI change that is required is an option box in the NewPagesFeed that lets me ignore those articles where I have clicked the next button. Call that "hide viewed" or "only show unseen" or something similar.
It would make my reviewing more efficient by facilitating a quick scan of unreviewed pages I have not seen yet, and selection of the ones I think need the most urgent attention. -- Vexations ( talk) 23:06, 22 October 2018 (UTC)
Thanks for the tip about the https://tools.wmflabs.org/nppbrowser/. I found the ability to search by keywords to be very helpful.
I don't see this functionality in the Special:NewPagesFeed. It does include AfC but seems to lack the functionality / view of tools.wmflabs.org/nppbrowser. Is there perhaps a way to have the same keyword search for AfC drafts? The current options are
It would seem to be fairly straightforward to add a "(_) drafts" option, but I'm not sure what would be involved. K.e.coffman ( talk) 18:14, 13 October 2018 (UTC)
Right now the feed relies on ORES related criteria for certain labels in the feed, eg SPAM, attack, etc. That's all well and good and we should keep making use of ORES' abilities. However, it might be nice, spurred on by recent discussion around adding a COI label, if the community had some ability to add its own labels, perhaps through tie ins to Edit Filters, so that development of this feature were not dependent on criteria that we have to go to the foundation to get updated/changed/etc. Best, Barkeep49 ( talk) 01:34, 26 July 2019 (UTC)
better COI detection toolwill be near-certainly this ORES-COI-model, for the integration of which, we (obviously) need to go back to WMF.
Scoring Platform Team is very understaffed with no dedicated product support.FWIW, since then, the team has got reduced even more and Halfaker has been mentioning of the need of a bigger budget, of late.
This has been copied over from Kudpung's writing here:
have been expecting something on the lines of:
Tagging, but leaving unreviewed: Thank you for creating xxxxxx. A reviewer has tagged the article as needing your attention before it can be accepted for indexing by search engines."
Tagging, but passing as patrolled: The standard message, with the message details completed by the reviewer.
A further idea: For all new articles passed as patrolled, a thank you template with a few (really just a few) links to help pages, the Teahouse, and 'Your first article'. Most of the new articles are created by new users and this would also help demonstrate that there are a humans behind Wikipedia.
Suggested responses:
1. New template: "Thank you for creating xxxxxx. A reviewer has tagged the article as needing your attention before it can be accepted for indexing by search engines.""
2. Template:Reviewednote-NPF
3. A new template that should automatically be sent when an article is passed as patrolled without further comment.
At present, on disambiguation (dab) pages the "Page info" symbol, , is covered by a little white "1" on a red square background, and the "Possible issues" section comments: "No citations - This page does not cite any sources." Since reference citations are not allowed on dab pages, it seems that there should be a way to sense the dab page and not specify a need for the citations. P.I. Ellsworth ed. put'r there 03:44, 23 December 2020 (UTC)
There are examples of this at the
Chicago Storm –
Bringing It Back –
Kill Devil Hill –
J Street (disambiguation) (dab) –
Formal semantics (disambiguation) (redirect) and
Lil Bit (disambiguation) (dab) pages.
P.I. Ellsworth
ed.
put'r there 03:48, 23 December 2020 (UTC)
After checking several dab pages, I see that the bar on the right side that holds the various icons sometimes no longer appears. So the solution was to remove that sidebar from the dab pages?
P.I. Ellsworth
ed.
put'r there 04:41, 29 January 2021 (UTC) 13:08, 12 February 2021 (UTC)
I propose that in the New Pages Feed, AfC drafts will also be able to be filtered by having no citations, having been previously deleted, created by new users, created by blocked users, etc., as opposed to just filtering them based on potential issues and ORES-given ratings. JJP...MASTER! [talk to] JJP... master? 22:30, 22 March 2021 (UTC)
My main use of the New Pages Feed involves filtering for Were previously deleted. At the moment these are highlighted in red as Previously deleted. Nowadays, however, a high proportion have been cycled from mainspace to Draft then back to mainspace (ideally with AfC eyes in between, but often not), which triggers this filter. It would be helpful if the Previously deleted text could be expanded to identify particular circumstances, for example:
Both of these would involve just file-exists tests based on the article title. A more ambitious option 3 would involve appending an icon alongside all Previously deleted texts, to allow the user to click through to a new tab showing Special:Log?page=XY so that the actual history of prior instances can be viewed.
Each or all of these changes could I think increase the effective scrutiny of articles recurring into mainspace. AllyD ( talk) 08:50, 18 November 2021 (UTC)
@ MPGuy2824 and Novem Linguae:. With the recent patch, the number in the footer now closely matches the number of unreviewed articles in the queue. Right now, I see the footer says 7 and the feed says 5. That is a minor difference due to the caching issue. No big deal. But the queue actually contains 48 unreviewed articles right now - there are another 43 with Prod tags. So the count in the footer doesn't actually match the review status (green check or not); it is actually the number of unreviewed articles that are not currently nominated for deletion. Do we want to "fix" that to make it technically accurate? On the other hand, there is nothing to do with those articles. Which number is picked up in {{ NPP backlog}} and the report/graph? Which number to we want to "publicize" as the queue size? — Preceding unsigned comment added by MB ( talk • contribs) 14:26, 20 October 2022 (UTC)
Since ACPERM was rolled out, 'Were created by newcomers (non-autoconfirmed users)' can be removed, because they no longer can anyway. Kudpung กุดผึ้ง ( talk) 21:41, 7 July 2022 (UTC)
Display 'Predicted class' and 'Potential issues' in the feed list by default and remove these options from the panel to reduce clutter and banner blindness.
Kudpung กุดผึ้ง ( talk) 21:41, 7 July 2022 (UTC)
Novem Linguae, coming back to
I am reminded of something
Kaldari (former WMF Head of Engineering) said a few years ago with a link to an external article: An abundance of user preferences, however, can lead to
decision fatigue. So it's important to only provide preferences that will actually be used.
[4]
It is indeed something I was taught at uni in Berlin 36 years ago on a lecture called Qual der Wahl. I think we should open a ticket on this or perhaps you can write a patch yourself.
Kudpung กุดผึ้ง (
talk) 11:15, 17 July 2022 (UTC)
After reviewing one article/redirect, I often want to see others created by the same user. In the filters, there is the choice to specify a username. It is a bit arduous to copy/paste the username into this field. I would like another option (probably to the right of the user name box) that if checked, will fill in the field with the username from my last patrol. Comments? MB 04:19, 11 July 2022 (UTC)
It would be good if the edit summaries for articles when adding an AfD tag could mimic Twinkle and read "Afd: Nominated for deletion; see Wikipedia:Articles for deletion/NominationName" - ditto RfD, MfD, etc.
Make it optional to post the message to the talk page. Some messages are appropriate for the creator only. I'm not as prolific nowadays as many reviewers, but I do find very often that I don't want the message posted to the talk page especially when I'm offering advice to a new user which I do quite often. If posting the message to the talk age is opional, perhaps more reviewers would leave a message of advice or encouragement for the creator. Kudpung กุดผึ้ง ( talk) 02:57, 23 July 2022 (UTC)
This edit shows a tag added before the {{ short description}}, which is out of order per WP:ORDER. This is really minor and makes no real difference, but would be moved by AWB, so better to put in the right place to begin with. MB 15:33, 2 August 2022 (UTC)
I'm not sure at what point this would occur but I'm of the mind that once an article is added to the NPP queue, a TP should automatically be created with header and relevant WikiProjects listed in the banner, if it doesn't already have one. By doing so, some of the project teams can help with article clean-up instead of leaving that chore for NPP. Atsme 💬 📧 20:10, 22 August 2022 (UTC)
...not sure it'd be fair to require that of autopatrollers
, I beg to differ,
NL. Like
Atsme I've always been convinced that the talk page shoud be processed at the point of creation. While there's an excuse for newbies, an autopatroller is generally expected to produce 100% complete articles (except for eventual future expansion). At least that's what I do and I'm rather proud of it. Or am I wasting my time making clean articles? Not that anyone bothers to read them so it's not even leading by example - unless I link to them when I'm teaching others. Having a tool for NPPers to do it would be handy, but I don't think it's high on the priorities until at least the PageTriage codebase has been rewritten.
Kudpung กุดผึ้ง (
talk) 03:57, 27 August 2022 (UTC)
Since AFDed articles can be marked as reviewed with just a quick check that there is a valid deletion discussion, it would be handy to find easily find these. The page feed has the option "Nominated for deletion", but that includes CSD & PROD. I just went through all those and found around 60, and about 2/3s were AFD meaning I had to skip through 20 others. It would be more convenient to be able to filter on just AFDs (don't see a reason to need only CSD or only PROD). MB 20:02, 25 August 2022 (UTC)
Autopatrolled articles are becoming increasingly problematic - either that or we are getting a bit better at serendipitously finding them. Alreadty the Autopatrolled righ has been removed from the Admin privileges.
Keep 'from Autopatrolled' in the filter options but:
This would inform the reviewers of any issues and leave them to take a closer look at their discretion. Kudpung กุดผึ้ง ( talk) 02:50, 14 September 2022 (UTC)
which incidentally doesn't seem to work at the moment. Did you try ticking the check box for "State: Reviewed"? That needs to be paired with the autopatrolled filter for it to display results. Hope that helps. – Novem Linguae ( talk) 13:54, 15 September 2022 (UTC)
OK. So that works now, but still needs my suggested red alert in the feed, otherwise there's no point in having the radio button 'Were created by autopatrolled users' at all. As this only affects the work of reviewers and is only visible to them, a site-wide or any other RfC is superfluous. As I said earlier, we don't need consensus for every minor improvement to the GUI of a specialised tool. Believe me, if I knew how to do it I would boldly do it myself as I have many other things in the past (and recently) on templates and tools. We can refine the selection options further, and how they are displayed in the filter panel, but at least let's discuss it rather than ruling it out - I'm not one for making usage suggestions just for the sake of it.
We're all agreed that to save NPP we need to start thinking outside the box, and streamlining the work is part of making NPP sexy enough for editors to want to do it. That said, I'm not ignoring the fact that a lot of articles and redirects are created by autopatrollers and it is a help not to have to review them (generally), but we are well aware that it is abused and even by admins - that's why it was removed recently from the admin toolset. Kudpung กุดผึ้ง ( talk) 00:30, 16 September 2022 (UTC)
@ MB, Novem Linguae, and MPGuy2824:. Proposed here. --Kudpung
When all or a very large proportion of an article's content is overwritten with new material, the article should be marked as unpatrolled and added to the NPR queue. This is virtually creation of a new article, but can be done by IPs and new accounts, and is often a sign of conflict-of-interest editing : Noyster (talk), 11:03, 16 January 2018 (UTC)
Thank you for creating xxxxxx. Your article has been passed by a New Page Reviewer. If you have any questions don't hesitate to ask at the Teahouse
This lets the creator know that s/he is not an island, and it serves to let them know that their work has been noticed. Just one of those nice little things that no one has ever thought of. Kudpung กุดผึ้ง ( talk) 12:11, 18 October 2022 (UTC)
I'm fairly certain this used to exist, but maybe it's wishful thinking. There are plenty of cases where a reviewer might message the creator without wanting to mark the page as reviewed. For example, by the time the next reviewer arrives, the creator may have addressed the issue. In any case, it will warn the reviewer that the creator has already been messaged.
See the example of the added alert in red.
As an extension to this feature - but on the 'Mark as reviewed' pane, apparently creators get a notification when their article has been reviewed, but are they automatically informed if a successful review is also accompanied by some tags on the article? The tags might not be a deal breaker for a review, but they are there because they nevertheless need to be addressed. Kudpung กุดผึ้ง ( talk) 09:59, 23 October 2022 (UTC)
According to this quarry, the top-10 most commonly used tags are (in descending order): notability, stub, refimprove, one source, orphan, linkrot, unreferenced, uncategorized, copy edit and primary sources.
The 'common' section of the toolbar has the following tags: under review, linkrot, copy edit, more footnotes, refimprove, unreferenced, stub, uncategorized and orphan.
I'm not sure about 'under review', but we should remove "more footnotes" and add "notability (General)", "one source" and "primary sources" to the common section of the toolbar. - MPGuy2824 ( talk) 04:28, 29 November 2022 (UTC)
Note: This discussion is now moot, since the common tags have been removed. -
MPGuy2824 (
talk) 07:20, 3 December 2023 (UTC)
As I've patrolled the New Pages Feed, I noticed that most of the time if a page is marked as having previously been deleted, it was deleted under one of the redirect criteria, an RfD (and the new page is not a redirect), or G7. I think that the New Pages Feed should ignore these deletions and not mark that the page was previously deleted if it were under these criteria (unless its a redirect and it was deleted under an RfD or R crtieria), as often these deletion have no merit on whether or not the page should remain. As an example, Kenangan Masa is marked as previously deleted because it was a page that was moved to draftspace and the redirect was deleted under R2. The deletion has no merits on the actual article itself since it was unrelated to the article content. ― Blaze Wolf TalkBlaze Wolf#6545 13:53, 10 May 2023 (UTC)
Is there a preferences panel to allow the Page Curation toolbar to track PROD, XfD, and CSD like Twinkle does, and like MoveToDraft allows? Am I missing this somewhere? If not, can it be added? microbiologyMarcus ( petri dish• growths) 21:24, 29 November 2023 (UTC)