Index
|
||
2. Redirects
- Redirects when an RfD tag or any other material is added to them, but they remain redirects, should not be in the New Page feed. Done please verify. Kudpung กุดผึ้ง (talk) 02:38, 13 September 2019 (UTC)
- Concur.- MrX 12:45, 2 September 2016 (UTC)
- Agree Lineslarge (talk) 00:05, 25 September 2017 (UTC)
- 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.
- This would be very useful. Probably a little more complicated to code.- MrX 12:45, 2 September 2016 (UTC)
- Currently, if a five-year-old redirect becomes an article today it is posted to the back of the queue and looks like it has been there for five years. The creation date in this case should be the first date substantial content was added, not the date the redirect was created. VQuakr (talk) 23:32, 8 September 2016 (UTC)
- And the automatic "your page has been patrolled" message goes to the creator of the old redirect; no message goes to the creator of the article unless the patroller is aware of the situation and goes to the extra trouble: Noyster (talk), 11:13, 9 September 2016 (UTC)
- Agreed, especially since when a page is tagged for deletion the same thing happens. A notification should be posted to both the redirect and the article creator (as when a page is tagged for deletion the redirect creator may have comments too.) Blythwood (talk) 04:48, 4 October 2016 (UTC)
- Id like to see this. Lineslarge (talk) 00:05, 25 September 2017 (UTC)
- And the automatic "your page has been patrolled" message goes to the creator of the old redirect; no message goes to the creator of the article unless the patroller is aware of the situation and goes to the extra trouble: Noyster (talk), 11:13, 9 September 2016 (UTC)
- Phab status unclear. Kudpung กุดผึ้ง (talk) 02:46, 13 September 2019 (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)
- I'm not so sure about this one.- MrX 12:45, 2 September 2016 (UTC)
- If an article is not in the NPP list (too old, or, I believe, also if it has been patrolled), then it either is reduced to a redirect or gets vandalized with all content removed, and subsequently is restored to its previous state, it should not return to NPP. One can set some limits here, for example, if the content is restored within a day.--Ymblanter (talk) 18:53, 8 September 2016 (UTC)
- "Make "redirects" included by default in PageTriage" - This was suggested in phab:T42135 - essentially setting the default to "on" for the "Redirects" filter. Is this [still] wanted? Quiddity (WMF) (talk) 23:15, 5 October 2016 (UTC)
- @Quiddity: Well, that depends. There are issues with the way the new pages filter handles redirects. A brand new redirect should probably show up in New Pages to be patrolled (we want to catch people creating a redirect from insert bad word here to BLP). A former redirect that has been changed to an article should still show up, but it should be indexed by the date significant content was added, not the date the redirect was created. Redirects that have had a WP:RFD tag placed on them should not show up. ~ ONUnicorn(Talk|Contribs)problem solving 21:50, 6 October 2016 (UTC)
- @Quiddity: Yes, it's definitely wanted. All new redirects should pass through NPP. But it's note one of the high priority issues requiring urgent engineer attention. (For me personally, most of the suggestions on this page are urgent because we've been waiting 5 years for them, but I'm realistic in knowing only too well what a) lightens the load for both admins and patrollers, b) what more efficiently helps us to prevent and/or destroy serious cases of spam and trolling. Kudpung กุดผึ้ง (talk) 06:22, 9 October 2016 (UTC)
- This is still desirable, and using my old account I confirmed that the 'redirects' button is still unticked by default (It ticks the 'all others' button and the 'Nominated for Deletion' button, and includes both reviewed and unreviewed articles). — Insertcleverphrasehere (or here) 22:03, 16 October 2018 (UTC)
- @Quiddity: Yes, it's definitely wanted. All new redirects should pass through NPP. But it's note one of the high priority issues requiring urgent engineer attention. (For me personally, most of the suggestions on this page are urgent because we've been waiting 5 years for them, but I'm realistic in knowing only too well what a) lightens the load for both admins and patrollers, b) what more efficiently helps us to prevent and/or destroy serious cases of spam and trolling. Kudpung กุดผึ้ง (talk) 06:22, 9 October 2016 (UTC)
4. Notifications: new icon
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)
- Support I second this. It would allow us to have a different message sent to the user. Currently if you green check a page that youve tagged for deletion, and send them a message telling them why it is inappropriate, they get a very passive aggressive "Thanks so much for submitting that article! Which is crap, please don't do so again." It should have a different user page template when sending the message to the user that goes along the lines of "Page so-and-so has been tagged for maintenance..." — Insertcleverphrasehere (or here) 21:30, 20 August 2018 (UTC)
6. Welcome message
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)
- Aside from the advantage that welcoming is known to give, some of our patrollers get into the mindset of wanting to do something with each article they look at. Welcoming a newbie as an alternative might help shift some people from the mentality of trying to work out which deletion tag or article improvement template is most applicable to a new article. ϢereSpielChequers 22:32, 7 September 2016 (UTC)
- Support - yes. I shouldn't have to click over to their talk page for this. Blythwood (talk) 15:34, 1 October 2016 (UTC)
- Support - Copy and pasting the subst on the csd tag itself does this, why shouldn't this be included in the tool already? Meiloorun (talk) 🍁 02:01, 17 February 2017 (UTC)
- Support this is honestly one of the reasons I prefer Twinkle for dealing with CSD. I'm giving page curation another go for CSD tagging, but welcoming simultaneously to notifying would be a huge plus. TonyBallioni (talk) 01:20, 22 February 2017 (UTC)
- Support and that's why I listed WereSpielChequers' suggestion here. For years the WP:Welcoming Committee has been abused and misused by new users themselves for whom, like other meta areas, is magnet. They hover over the new registrations and slap a welcome template on every vandal, troll, and no-edit newbie just to boost their edit counts. The WC is due for a shake up and this page for a severe pruning. Kudpung กุดผึ้ง (talk) 02:39, 22 February 2017 (UTC)
- Support, particularly if accompanied by a feature that flagged users who had never been welcomed and also recognised when a belated welcome would be appropriate. Lineslarge (talk) 07:02, 25 September 2017 (UTC)
- Support this is quite desirable and I'll be putting in a Phab ticket requesting it. — Insertcleverphrasehere (or here) 22:05, 16 October 2018 (UTC)
- Support — This would be extremely useful and would go very nicely with the in-built wikilove message to appreciate accounts who have created prolific first articles. Regards, SshibumXZ (talk · contribs). 07:36, 19 October 2018 (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)
- Kudpung, will check on it in the morning. I believe it should be somewhere in their queue of stuff and they haven't gotten to it. In general comunication explaining how they were going to approach the wishlist development work is less than I hoped or experienced when they put AfC into the queue. Best, Barkeep49 (talk) 03:06, 13 September 2019 (UTC)
10. Articles by previously warned editors
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)
- Thanks Kudpung. We've got the list of potential Autopatrollers now at Wikipedia:Database reports/Editors eligible for Autopatrol privilege so that doesn't need folding into curation, but it would still be good to bring extra skeptical attention to editors who have created G3 and G10 articles. I'm no longer quite so sold on the "Look at x other unpatrolled articles by this author?" button as I can see that being used by sloppy deletion taggers to tag everything else that an editor has created. ϢereSpielChequers 13:36, 13 September 2016 (UTC)
11. Patrolled by Twinkle
See also #28 below.
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)
- Support Twinkle is easier to use in many cases. In particular it has more granular and easier, in my opinion, tagging but I still use the NPP Tool because it keeps the Page Curation Log. As long as people use TW to review new articles we need to be able to capture stats from it. JbhTalk 14:15, 2 October 2016 (UTC)
- Support - Most of my reviews are done with Twinkle.- MrX 14:34, 15 June 2017 (UTC)
- Support - I honestly do a bit of both. I use the NewPagePatrol script which shows a list of the new pages on the left side, and when I am off doing other stuff on the wiki and click to an article it doesn't always turn on the page curation tool and I'll end up using Twinkle to mark it patrolled instead. More often with the page curation tool these days though. — InsertCleverPhraseHere 01:24, 21 July 2017 (UTC)
- Support I also use both. I have noticed I tend to pick up diffent issues depending on how I look. DGG ( talk ) 19:27, 17 March 2018 (UTC)
- Support — per reasoning by Kudpung. Regards, SshibumXZ (talk · contribs). 07:38, 19 October 2018 (UTC)
- Comment This is largely resolved via the 'patrol log' which is now pretty much synonymous with the 'page curation log' when it comes to the page feed. It doesn't matter if a page is 'reviewed' or 'patrolled'; it will display in the new page feed as being reviewed. There is a bug though that in the All public logs for a given page, it doesn't list the Patrol log actions, but does list the page curation log actions. I'll file this in Phab as this needs to be fixed. It is difficult to figure out who reviewed a page sometimes, because if you check the public logs, it won't show up. — Insertcleverphrasehere (or here) 15:01, 19 October 2018 (UTC)
- Barkeep49, another one to follow up or note for the next wishlist. I think this one is quite important. Kudpung กุดผึ้ง (talk) 03:57, 13 September 2019 (UTC)
- @Barkeep49, Insertcleverphrasehere, DGG, and Jbhunley:, No, I'm talking about a feature that shows if a patrolled item in the feed was patrolled using Twinkle. Semi automated edits using Twinkle are shown as such in edit summaries as '(TW)' so IMO if there is something that recognises this already, it should be possible to show it in the feed. The reason for this is to eep track on just what extent Twinkle is still benig used for reviewing new pages, and to encourage users to Curation instead. Kudpung กุดผึ้ง (talk) 01:52, 14 September 2019 (UTC)
25. Tool for moving to draftspace
Mentioned several times around the site but first suggested here 13 December 2015 by czar. Kudpung กุดผึ้ง (talk) 14:16, 8 September 2016 (UTC)
- Support - provided a polite explanation is made, e.g. that the topic is valid but that the article is not finished yet. Blythwood (talk) 15:33, 1 October 2016 (UTC)
- The tool should
- Show as 'Move to Draft' in the Curation tool actions list
- Move the page to Draft:articlename without leaving a redirect
- Send this message to the creator:
- Hi (USERNAME), thank you for creating a new article. Unfortunately it's not quite ready for publication but to allow you to continue to develop it without fear of deletion we have moved it to Draft:articlename. When it is ready, please submit it to AfC for review and if it's good to go, a reviewer will move it back to mainspace for you. You may wish to read WP:My first article, and if you need more help, do post a question at The Tea House
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.
- --Kudpung กุดผึ้ง (talk) 00:46, 13 October 2016 (UTC)
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)- Yes, I just did this yesterday, and have done it at least once or twice on previous occasions. (Note: I am not an active "NPP" (more of an "old pages partroller"!), and only occasionally come across stuff like this when working for the WikiProjects like FILMBIO...) It sounds like maybe there should be a move to encourage Page movers to do NPP? (Or someway to grab the attention of Page movers to move New Pages into Draftspace without leaving a redirect? – Some kind of maintained maintenance list perhaps?... If somebody came up with such a list, I'm probably one of the PM's who might watchlist it.) --IJBall (contribs • talk) 06:07, 27 February 2017 (UTC)
- Oppose. I have some concerns about this. I can see moving to draft becoming a form of unilateral "soft deletion" with no discussion, no admin oversight and no limits on what can be deleted. New editors (i.e. not autoconfirmed) won't have the technical ability to move their draft back to mainspace without going through AfC (which is supposed to be an optional process). Even if they did, they wouldn't necessarily know that's what they're supposed to do, or they might assume their article has been "rejected" and give up on it. There's a huge potential for biteyness and I think a lot of these drafts would end up abandoned and G13ed. I think if this were to become common practice, or if were to be built into Page Curation, there would have to be a wider discussion to establish a community consensus for the process and agree some guidelines on what circumstances it can be used and if any oversight is necessary. – Joe (talk) 11:26, 27 February 2017 (UTC)
- Support - As far as I know, any autoconfirmed user can move any page to draft space, The admin oversight would come into play when the redirect CSD is reviewed by an admin. Those of us who are not admins, but are WP:PAGEMOVERs, should be trusted to move articles to draft without a redirect unless it is shown that we have abused that right.- MrX 14:57, 15 June 2017 (UTC)
- Strong Support - Kudpung กุดผึ้ง (talk) 15:59, 15 June 2017 (UTC)
- Strong Support @Kudpung, Note that such a tool already exists in the form of a script: User:Evad37/MoveToDraft. However, this should also be a feature of the page curation tool. If the user has the Page Mover user right, it should move without leaving a redirect, and if they don't, it should automatically tag the redirect for CSD R2. Many articles that end up PRODed or CSDed would be much better off draftified. In my experience, often up to a fifth or so of all new articles in the new pages feed would be best served by being draftified (varies by time of day). Draftifying encourages new users to continue working on the article, while tagging for deletion discourages them (why bother if it is going to get deleted anyway, especially in the case of CSD). In any case, Draftifying articles is currently difficult and time consuming as a manual process and the automated tool available is obscure and does not automate tagging as CSD R2 for non WP:PAGEMOVERs. Semi-automated Draftification should be made more available to New Page Patrollers through addition to the page curation tool. Note I originally posed a similar note to the page curation talk page before being informed of the discussion here.
- @Joe Most of the feedback I get from new users when draftifying their submissions has been quite positive. They often have had trouble in the past with their new, undersourced, articles getting quickly deleted, and are grateful to have their article retained with the chance to work on it further; so I don't see a big biteyness issue. Those that don't understand the draftification, despite the message posted to them, will often just immediately recreate the article, in which case it becomes a matter of simply using the normal tag/PROD/CSD/XfD process if necessary and this doesn't really pose a problem at all. It isn't a catch all, many articles are better off CSDed, PRODed, sent to AfD, or simply tagged, but it is another tool in the NPP toolbox that should be made more widely available.
- @IJBall I added the above script to the WP:PAGEMOVER page as well as the userspace to draftspace version, This should help Page Movers be aware of other uses of the user right. A better approach however is for admins who notice prolific and competent NPPatrollers to offer them the page mover right and explain its usefulness in NPP, and to make NPPatrollers aware of the usefulness of the user right so that they can request it. — InsertCleverPhraseHere 01:12, 21 July 2017 (UTC)
- I am well aware of the script and gave been using it for some time. It's actually quite good. The problem is that the volunteers, such as Evad37 should not have to be making these tools. Of course, the Foundation will rejoice once more at the volunteers doing the devs work for them. There is absolutely no need for a major RfC to agree on this tool - Wikpedia is already stifled by senseless RfCs, What it does need however, is incorporating into the Page Curation tool so that i can only be used by accredited New Page Reviewers, and avoid being abused by unqualified New Page Patrollers, because in spite of the caveats above, based on empirical experince of tens of thousands of patrolls, they will almost certainly use it as a catch-all. Kudpung กุดผึ้ง (talk) 02:32, 21 July 2017 (UTC)
- @Kudpung This is a good point. The worst part about Evad37's tool is that it does not automatically tag the redirect as CSD R2 if the user is not a Page Mover (I tested this with my old account that doesn't have the user right), rather it just creates a normal redirect to the draft. This is an issue as unqualified New Page Patrollers who find the tool and decide to use it will not get doublechecked by admins unless they go through the extra hoop of manually tagging the redirect for CSD. Paradoxically, adding this to page curation with an automatic CSD R2 for non Page Movers would actually result in more oversight of draftification, not less. — InsertCleverPhraseHere 02:49, 21 July 2017 (UTC)
- I am well aware of the script and gave been using it for some time. It's actually quite good. The problem is that the volunteers, such as Evad37 should not have to be making these tools. Of course, the Foundation will rejoice once more at the volunteers doing the devs work for them. There is absolutely no need for a major RfC to agree on this tool - Wikpedia is already stifled by senseless RfCs, What it does need however, is incorporating into the Page Curation tool so that i can only be used by accredited New Page Reviewers, and avoid being abused by unqualified New Page Patrollers, because in spite of the caveats above, based on empirical experince of tens of thousands of patrolls, they will almost certainly use it as a catch-all. Kudpung กุดผึ้ง (talk) 02:32, 21 July 2017 (UTC)
- Oppose This is contrary to the fundamental Wiki principle of developing articles in mainspace. If you have a notable topic then the draft should be in article space to make it clear that it already being worked upon. Otherwise, you are encouraging forking and generally wasting people's time by pushing stuff around rather than improving it. It is our policy that imperfect articles are welcome and this tool should not violate established policy. Andrew D. (talk) 19:27, 8 August 2017 (UTC)
- Apart from being off topic here, Andrew Davidson, because WP:PERFECTION doesn't mention anything of the kind, and besides which, new users can't create in mainspace anyway, the choice is clear: pages that might have some potential but are suffuciently imperfect that they cannot possibly reside in mainspace are usually deleted; given the opportunity to develop their articles in a safe haven might not only result in a reasonble new article, but also one less new user gets bitten by having their article harshly deleted before it has been hardly begun. Kudpung กุดผึ้ง (talk) 23:48, 23 September 2017 (UTC)
- Support Automates a process that is handled manually at the moment. scope_creepTalk 00:57, 14 September 2019 (UTC)
- If we already have a good script, we should use it. I think it is a good idea that volunteers make tools. I think it's a good idea that we not rely on the paid developers unless they are actually needed. The more of the programming is done by regular WPedians, the better. But I certainly do use move to draft -- the main thing that's needed is that Evad37 or someone work on the current script further to make it easier to give different reasons. DGG ( talk ) 04:39, 14 September 2019 (UTC)
- Comment: I don't see much value in adding this to the toolbar, given that we have User:Evad37/MoveToDraft. It would probably be easier to improve the user script to mark the R2 deletions as reviewed. MarioGom (talk) 11:32, 14 November 2021 (UTC)
26. DYK information
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)
- Nice idea, ONUnicorn, but NPP is supposed to be a system for checking whether or not new pages pass the bar (sorry about the private pun). It we start using it for DYK suggestions it wil add clutter to the interface and people will want to use it for GA and FA suggestions. Generally the vast majority of new articles are from new or very inexperienced users and are practically all of very low standard. What we are generally looking for are articles that will be kept because they would probably survive AfD, and articles that must be deleted for non compliance with important policies, and to a lesser extent, articles that are not fit for publication but have potential and can be moved temporarily to draft space. --Kudpung กุดผึ้ง (talk) 06:14, 15 September 2016 (UTC)
- @Kudpung: I have done a fair amount of NPP. I am aware the main point is to keep unacceptable content out. However, Wikipedia has a problem keeping new editors who are good. There is no effective reward for a new editor who submits a new article that meets our guidelines. Most new editors are unaware that new articles can be featured on the main page, and have no idea how to navigate the complex system that is DYK. All I'm asking for is the ability to click a box that would put a message on a new editor's page that says something to the effect of this. This should only be done if there are no problems with the article; if the patroller marks the page as reviewed without adding any clean up tags and elects to send the message. ~ ONUnicorn(Talk|Contribs)problem solving 14:21, 15 September 2016 (UTC)
- I think this is a reasonable suggestion actually, especially with college editing Wikipedia projects that are meant to widen Wikipedia coverage on marginalised topics (women, ethnic minorities, etc.). It's a reasonable encouragement - a stretch further, but not unreasonable, to tell new contributors "This is really interesting. I think this information could easily be put on the front page of Wikipedia if you did a bit more work. Go here and it will tell you how." I am developing some form messages based on my own NPP experience and may add one for this situation. Blythwood (talk) 15:33, 1 October 2016 (UTC)
- Blythwood, You may wish to take a look at Wikipedia:WikiProject User warnings. Kudpung กุดผึ้ง (talk) 00:29, 3 October 2016 (UTC)
- I think this is a reasonable suggestion actually, especially with college editing Wikipedia projects that are meant to widen Wikipedia coverage on marginalised topics (women, ethnic minorities, etc.). It's a reasonable encouragement - a stretch further, but not unreasonable, to tell new contributors "This is really interesting. I think this information could easily be put on the front page of Wikipedia if you did a bit more work. Go here and it will tell you how." I am developing some form messages based on my own NPP experience and may add one for this situation. Blythwood (talk) 15:33, 1 October 2016 (UTC)
- @Kudpung: I have done a fair amount of NPP. I am aware the main point is to keep unacceptable content out. However, Wikipedia has a problem keeping new editors who are good. There is no effective reward for a new editor who submits a new article that meets our guidelines. Most new editors are unaware that new articles can be featured on the main page, and have no idea how to navigate the complex system that is DYK. All I'm asking for is the ability to click a box that would put a message on a new editor's page that says something to the effect of this. This should only be done if there are no problems with the article; if the patroller marks the page as reviewed without adding any clean up tags and elects to send the message. ~ ONUnicorn(Talk|Contribs)problem solving 14:21, 15 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)
- You could use User:SD0001/DYK-helper to file DYK nominations easily. However, note that the DYK process includes a "QPQ" requirement which is time-consuming and not something IMO new page reviewers would be interested in. SD0001 (talk) 16:38, 15 September 2019 (UTC)
29. Special:NewPagesFeed
Auto refresh. MusicAnimal, Kaldari (can this be implemented fairly quickly? It doesn't sound complicated.) The feed should auto refresh every 5 seconds like the other one does. This is the other main reason why so many patrollers won't move over to Page Curation. Whatever we encourage them to do, they will hover with their mouses over that feed ready to pounce as soon as they can add a deletion tag to a new article. The rest of the stuff, even low hanging fruit, they leave untouched. Suggestion: In the feed's user settings ('Set filters"), provide a choice of manual refreshing using the existing button, or auto refreshing. Then rename 'Set filters' to 'Preferences' (everyone on the Internet knows what preferences means). --Kudpung กุดผึ้ง (talk) 06:04, 9 October 2016 (UTC)
- @Kudpung: We originally decided to not auto-refresh the Special:NewPagesFeed interface for two reasons: First, it doesn't work that well with infinite scrolling. If you've loaded several pages worth of articles via infinite scrolling and then the list refreshes, you have to basically start over. Second, the Special:NewPagesFeed interface is geared more towards actual analysis of pages (via the snippets and metadata) than Special:NewPages, which is more tailored towards fast scanning. When you're actually reading the snippets and metadata to analyze a page, it's more disruptive to do an auto-refresh. However, both of these issues could be mitigated with a user preference as you suggest (for people that only want to patrol from the very top). An abundance of user preferences, however, can lead to decision fatigue. So it's important to only provide preferences that will actually be used.[1] Are there any discussions or other evidence that people actually want such an option at Special:NewPagesFeed? Kaldari (talk) 04:43, 12 October 2016 (UTC)
- @Kaldari:. I understand. I also fully understand decision fatigue (I studied that on my PhD research for KommWiss}. So you're right about not offering too many choices - by contrast however, the Twinkle prefs panel is a minefield - have you seen it?. There are no discussions or other evidence that people actually want such an option, but my own research (unfortunately it's something that metrics can't prove) clearly demonstrates that people really enjoy hanging with their mouses over that real-time live feed gadget from User:Lupin/recent2.js, ready to pounce and tag. That's how I figured that however quickly I refresh the Special:NewPagesFeed, a very significant number of pages come through that are already tagged, and of course with various kinds of deletion tags, while none of them are simply 'patrolled' or tagged for minor issues. These people aren't even using Special:NewPages, which as you say, is more tailored towards fast scanning and is fine in the hands of really expert patrollers - but I'm an expert patroller and I think the Page Curation system with its Special:NewPagesFeed is one of the best things the WMF has come up with - ever. I wouldn't be able to recognise socks and corporae spammers without it.t
- So we have to wean people away from Special:NewPages, and that real-time gadget, and get them all singing from the same page, otherwise our endeavours at WP:NPPAFCwill be wasted even if we set a user right limitation for access to Page Curation. The only solution as I see it therefore, is to offer the Special:NewPagesFeed with the options: Refresh mode with infinite scrolling, and Real-time live feed (display 5 pages), refresh every 10 seconds. We can then deprecate that live feed, User:Lupin/recent2.js, in the side bar altogether, its creator hasn't edited Wikipedia for 9 years and we don't need a consensus to do it. Kudpung กุดผึ้ง (talk) 06:13, 12 October 2016 (UTC)
- An alternative is to do it like Twitter does, where after 5 seconds or so a banner will appear at the top saying "View 5 more tweets", etc. This is effectively the same as a live feed but won't be so obtrusive, and won't require an additional user option to turn it on/off (those who don't want it simply won't click on the banner). To take it a step further, automatically removing pages from the list that have already been patrolled seems like a lot of work and I suspect performance would be an issue. From my own experience I'm happy with manually refreshing, but I also usually work from the bottom of the backlog — MusikAnimal talk 23:36, 15 October 2016 (UTC)
- The effort is to understand that we must wean people away from their favourite gadgets and attract them to using Page Curation. There are many problems associate with technical conflicts that arise from using two systems. Working from the front of the queue is also important for catching certain types of editors while they are still online, espcially the drive-by SPA. Kudpung กุดผึ้ง (talk) 10:02, 16 October 2016 (UTC)
- So we have to wean people away from Special:NewPages, and that real-time gadget, and get them all singing from the same page, otherwise our endeavours at WP:NPPAFCwill be wasted even if we set a user right limitation for access to Page Curation. The only solution as I see it therefore, is to offer the Special:NewPagesFeed with the options: Refresh mode with infinite scrolling, and Real-time live feed (display 5 pages), refresh every 10 seconds. We can then deprecate that live feed, User:Lupin/recent2.js, in the side bar altogether, its creator hasn't edited Wikipedia for 9 years and we don't need a consensus to do it. Kudpung กุดผึ้ง (talk) 06:13, 12 October 2016 (UTC)
- An auto-refresh similar to the new Watchlist 'Live Updates' button would be extremely advantageous (without disrupting scrolling). — Insertcleverphrasehere (or here) 07:16, 19 October 2018 (UTC)
- Barkeep49, MusikAnimal, can you follow up at Phab and decipher what the actual status of this ticket is? If it's been shunted into a holding pen like they often quietly do, maybe it should be considered for the next Wishlist. I think it's extremely important to wean people away from using Twinkle to patroll pages. It's OK for people like DGG who knows what he is doing with the old feed, but he vast majority of reviewers do not have his experience. Kudpung กุดผึ้ง (talk) 03:51, 13 September 2019 (UTC)
- Kudpung, this was marked as medium-priority over our internal discussions and hence were not submitted to WMF. So, you ought not expect any work, at-least in this year. ∯WBGconverse 12:43, 13 September 2019 (UTC)
37. Page Curation messages
The messages handed out by the PC tool should be embodied in templates on the local wiki rather than hard-boiled into the software.
Last month I received a "I have unreviewed a page you curated" message for the first time. Because the page's author had mangled the CSD template the message I received bore no resemblance to the facts as I knew them so I tried to investigate. However, the message is bare text and offers no clue to its origin - whereas most messages are transcluded or substed templates which show where they came from.
The message did not conform to the norms of this wiki:
- it wasn't signed;
- it invited a continuation of the discussion on another page rather than keeping the discussion together in one place; and
- there was no edit summary.
The first two issues would easily be resolved if the message were embodied in a template rather than the software. This change could also resolve the #Removing the 250 character limit issue raised by Mz7. Cabayi (talk) 17:42, 28 November 2016 (UTC)
- I agree. I raised this years ago to a WMF developer liaison only to have it dismissed. It's poor design. Sending a message to the reviewer when a page is unreviewed should also be optional, and should not be the default. It would be better to have any such message in the revision history as an edit summary anyway.- MrX 16:02, 15 June 2017 (UTC)
- Strongly agree Ican think of no reason why this would not be a major improvlement, in letting us make changes without waiting for years. DGG ( talk ) 19:33, 17 March 2018 (UTC)
- @Cabayi: -- Done. The first and last have been already, in place for long. I updated the language of the templates to keep the discussion, entirely on reviewer's talk.Check it out:-)Best, ∯WBGconverse 08:27, 28 October 2018 (UTC)
- Thanks Winged Blades of Godric. Yes, I saw Galobtter closed off the ticket this morning. How did it take two years for the existence of the messages at Category:New Pages Feed templates to come to light?? (*ahem* poor documentation) Now that they are in the daylight, it seems just as bizarre that they're not protected in any way - pinging interested admins TonyBallioni, DGG, Mz7 to ponder that issue. -- Cabayi (talk) 11:13, 28 October 2018 (UTC)
- The most intuitive solution would be to prevent a message from being sent when the note
textarea
is empty. << FR (mobileUndo) 08:06, 22 February 2019 (UTC)
- The most intuitive solution would be to prevent a message from being sent when the note
- Thanks Winged Blades of Godric. Yes, I saw Galobtter closed off the ticket this morning. How did it take two years for the existence of the messages at Category:New Pages Feed templates to come to light?? (*ahem* poor documentation) Now that they are in the daylight, it seems just as bizarre that they're not protected in any way - pinging interested admins TonyBallioni, DGG, Mz7 to ponder that issue. -- Cabayi (talk) 11:13, 28 October 2018 (UTC)
- All have been done. But, MrX, I see that WMF has fulfilled your request by eliminating the need to send any customized message in case of un-reviewing, altogether. Now, whenever we un-review any reviewed page, a standard boilerplate is delivered to the t/p of orig. reviewer. LOL; this ought be a bug and shall be fixed. ∯WBGconverse 13:25, 14 September 2019 (UTC)
39. Keyboard shortcuts?
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)
- perhaps a script could take care of this? L3X1 (distænt write) )evidence( 12:10, 14 July 2017 (UTC)
- L3X1, what shortcuts do you want and for what stuff? Make a list ... ∯WBGconverse 11:14, 13 September 2019 (UTC)
- Winged Blades of Godric, I was thinking:
- C, minimizes or expands curation toolbar
- I, brings up or closes Page Info popout
- L, opens WikiLove popout
- R, opens review popout
- A marks as reviewed or unreviewed, depending on case (IDK if this one is possible)
- D, opens or closes deletion menu
- N, advances queue. Thanks,L3X1 ◊distænt write◊ 16:44, 13 September 2019 (UTC)
- IMO, a button to advance queue, and a button to review the page are the most important, if adding all of them is a burden. Thanks,L3X1 ◊distænt write◊ 22:42, 15 November 2021 (UTC)
- Winged Blades of Godric, I was thinking:
- L3X1, what shortcuts do you want and for what stuff? Make a list ... ∯WBGconverse 11:14, 13 September 2019 (UTC)
42. Filters by a score of estimated public interest
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)
- Support This has also proven very useful in working on WikiProject African diaspora--updating the popular pages report surfaced some unexpectedly highly visible pages that needed attention, and I agree that info really helps motivate work on them. Innisfree987 (talk) 18:11, 5 June 2017 (UTC)
- Support - This is a perfect example of triage and automation that could vastly improve NPP productivity. - MrX 15:50, 15 June 2017 (UTC)
- Support adding this functionality to the New Page Feed. — Insertcleverphrasehere (or here) 23:10, 16 October 2018 (UTC)
- Support — Not a bad idea in the least. However, I don't regard this as something that would have a high priority for me, personally. Regards, SshibumXZ (talk · contribs). 07:40, 19 October 2018 (UTC)
- Note:- This is not happening due to resource-constraints and I avidly dislike, what they are doing currently; this data feels like sheer bloat to me, absent a sort. Page Barkeep49. ∯WBGconverse 12:56, 14 September 2019 (UTC)
- Winged Blades of Godric, sorry I'm not clear on what you dislike. Best, Barkeep49 (talk) 14:37, 14 September 2019 (UTC)
44. Review 'on hold'
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)
- Not a bad idea, but technically possibly complicated to design. I too sometimes have situations when I am researching a new page, another patroller has tagged it for deletion and an admin has already deleted it. Kudpung กุดผึ้ง (talk) 00:44, 9 June 2017 (UTC)
- If we could have a live updating NewPageFeed (phab task T207437), this could be added and the page could be marked with a colour code to indicate that another patroller is reviewing it (set to expire after 5 min). — Insertcleverphrasehere (or here) 07:33, 19 October 2018 (UTC)
- @Insertcleverphrasehere, Kudpung, and Nick Moyes:, I cannot alter the color code (and frankly don't think the feature to be extremely beneficial in light of the amount of work, needed to be invested) but it would be easily possible to design a button in the curation toolbar that would slap a banner mentioning that a page is under review.
- Would it suffice?∯WBGconverse 15:43, 22 October 2018 (UTC)
- @Winged Blades of Godric: Yeah that would probably work. — Insertcleverphrasehere (or here) 16:21, 22 October 2018 (UTC)
- Barkeep49, another one unilaterally shunted out of site probably by Aklapper. How important is this request? It's a 'nice-to-have' but is it worth making a fuss about? Kudpung กุดผึ้ง (talk) 04:15, 13 September 2019 (UTC)
- Kudpung, I did create a way-out (months back) but, the downside is that one needs to manually un-review the page after slapping the template, as described at T221514.
- DannyS712 had proposed a generic workaround over T148353 which seeks that tagging a page (with any template) shall not automatically lead to a review, as default behavior.
- We (supposedly) need to check, as to whether the NPP community agrees with this generic fix, since it will incur an extra click on the tick-icon as a regular part of the workflow ..... ∯WBGconverse 11:24, 13 September 2019 (UTC)
- The work described by Winged Blades of Godric has been programmed but has not yet gone live. Best, Barkeep49 (talk) 13:08, 13 September 2019 (UTC)
47. Decline CSD/PROD
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)
- Also Requested above at Wikipedia:Page_Curation/Suggested_improvements#16._Decline_CSD.
- This is badly needed. Barkeep49, could you check out its status at Phab, and otherwise note it for the next Wishlist. Kudpung กุดผึ้ง (talk) 04:27, 13 September 2019 (UTC)
- Barkeep49, can this request be merged with No.16, and followed up at Phab? I'm sure it was on the wishlist. Kudpung กุดผึ้ง (talk) 02:24, 14 September 2019 (UTC)
- Kudpung, I think 16 was merged here (they show the same phab ticket regardless). The scope of work that came out of the wishlist is on meta. In checking the original wishlist asks I don't see this ticket on there. While I was aware of what you and Insertcleverphrasehere did I was not really following along closely enough to know where this fell off. Best, Barkeep49 (talk) 02:41, 14 September 2019 (UTC)
- Barkeep49, we only dispatched the high-priority tickets, after a discussion at Wikipedia_talk:New_pages_patrol/Reviewers/Archive_30#Task_List/Prioritising_tasks .... ∯WBGconverse 13:02, 14 September 2019 (UTC)
- Kudpung, I think 16 was merged here (they show the same phab ticket regardless). The scope of work that came out of the wishlist is on meta. In checking the original wishlist asks I don't see this ticket on there. While I was aware of what you and Insertcleverphrasehere did I was not really following along closely enough to know where this fell off. Best, Barkeep49 (talk) 02:41, 14 September 2019 (UTC)
- Barkeep49, can this request be merged with No.16, and followed up at Phab? I'm sure it was on the wishlist. Kudpung กุดผึ้ง (talk) 02:24, 14 September 2019 (UTC)
- Given that twinkle doesn't feature actually declining the CSD, just sending a warning, I think we can keep using twinkle for that and not prioritize this request --DannyS712 (talk) 05:59, 18 October 2019 (UTC)
55. Ability to log CSD taggings to their CSD logs
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)
- I always use twinkle for this reason. Is there not a way of logging CSD with page curation? If so that is a major flaw.— InsertCleverPhraseHere 22:28, 24 July 2017 (UTC)
- @KGirlTrucker81 and Insertcleverphrasehere: already exists. Go to your logs and then click "deletion tag log". You can view mine here. Its all deletion tags (so for me PROD and CSD except G12, because I much prefer Twinkle for AfD and G12). TonyBallioni (talk) 22:36, 24 July 2017 (UTC)
- @TonyBallioni: We're discussing about CSD tag logs being stored to user subpages, not this one. And also Insertcleverphrasehere, page curation and huggle don't actually log CSD tagging in a user subpage. KGirl (Wanna chat?) 00:12, 25 July 2017 (UTC)
- I know, but we already have an easily accessible deletion only log for it that also has the advantage of not being deletable via U1. I'd oppose spending developer time on this feature when there is a log already and there are other features above that are already in Phabracator that seem like they'd make the functionality of reviewing new pages easier. TonyBallioni (talk) 00:16, 25 July 2017 (UTC)
- For those of us that like to edit or organise our CSD log, it forces us to use Twinkle. — InsertCleverPhraseHere (or here) 20:46, 25 September 2017 (UTC)
- I know, but we already have an easily accessible deletion only log for it that also has the advantage of not being deletable via U1. I'd oppose spending developer time on this feature when there is a log already and there are other features above that are already in Phabracator that seem like they'd make the functionality of reviewing new pages easier. TonyBallioni (talk) 00:16, 25 July 2017 (UTC)
- @TonyBallioni: We're discussing about CSD tag logs being stored to user subpages, not this one. And also Insertcleverphrasehere, page curation and huggle don't actually log CSD tagging in a user subpage. KGirl (Wanna chat?) 00:12, 25 July 2017 (UTC)
- Note This same request is duplicated as #40, #55, and #64. — Insertcleverphrasehere (or here) 23:09, 16 October 2018 (UTC)
- The deficiencies of the page curation's logs are (as I see it, from a Twinkle user's perspective):
- They are in fixed locations. With Twinkle I can (and do) opt to log CSDs & PRODs in the same file. When I see a recurrent title I only need to check one place.
- The PC logs record the fact that the reviewer requested deletion. Twinkle records that the article being deleted was created by its author. When using the logs it's far more useful to know the identity of the previous author than the previous reviewer. A repeat author may be a sockpuppet, a repeat reviewer may be, um, a reviewer??
- Just my 2¢. Cabayi (talk) 09:36, 30 October 2018 (UTC)
- I strongly agree with implementing support for the Twinkle logging system in addition to the page curation log. Userspace CSD and PROD logs are widely looked at to determine suitability for advanced permissions and while it can be doctored or even deleted, doing so is still logged and can quickly throw up a red flag that can be checked into. Additionally, other tools like the AfC helper script have implemented support for the Twinkle log format while the page curation log is by definition limited just to the page curation toolbar, which is not universally used by all reviewers. Nathan2055talk - contribs 06:11, 13 January 2019 (UTC)
- I also support integrating this into user pages, so that it can be easier to look at all of your CSD/PROD tags at once, rather than having them split into 2 locations. --DannyS712 (talk) 06:19, 13 January 2019 (UTC)
- Now that T230455, this change can be implemened in Twinkle? See discussion on T207237. MarioGom (talk) 12:42, 14 November 2021 (UTC)
56. Assisted reporting at AIV of authors of blatantly blockably created pages
Serious BLP violations, swrious spam, serious vandalism. Kudpung กุดผึ้ง (talk) 13:34, 31 August 2017 (UTC)
- It would be good to have this flagged as an option when tagging with relevant CSD criteria. — Insertcleverphrasehere (or here) 08:35, 19 October 2018 (UTC)
- What prevents you from using Twinkle? In any case, you shouldn't be reporting someone to AIV without looking at their contribs first. And if you are at the contribs page, Twinkle's ARV is readily accessible from there. So, I'd say that this would be a pretty redundant feature. SD0001 (talk) 18:36, 1 January 2019 (UTC)
- This Phab ticket hasn't been addressed since it was filed. I don't think it's a priority. Comments , anyone? Barkeep49, SD0001? Kudpung กุดผึ้ง (talk) 06:28, 13 September 2019 (UTC)
80. Page Curation tools optionally available on any page, not just those in NewPagesFeed
DONE | |
"Resolved" by allowing users to add articles back to the queue, which re-enabled using the toolbar. --DannyS712 (talk) 02:39, 6 January 2020 (UTC) |
- The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
It should be possible to make ?showcurationtoolbar=1 and the 'curate this article' link work on any article, not just those in the feed (but currently can only be used on articles that have not expired out of the NewPagesFeed).
It is quite annoying that the Page Curation tools are only available for new pages that haven't expired, it means that I have to use Twinkle whenever a page has been reviewed and expires out of the feed.
It silly that the Page Curation tools are only available on new pages and not, for example, on Broadwater Green. IMO the 'curate this article' link in the toolbar should always be available to New Page Reviewers regardless of the page they are reviewing (It would even be useful for drafts).
Note that the page curation tools should ONLY show up on 'other pages' (pages that aren't in the NewPagesFeed) if that string is added to the URL or if you click the 'curate this article' link. Otherwise I think people would get quite annoyed with it showing up on all sorts of other pages constantly. — Insertcleverphrasehere (or here) 16:07, 19 October 2018 (UTC)
- This can be likely implemented easily, via a patch.Let's see. ∯WBGconverse 20:09, 27 October 2018 (UTC)
81. Adding a "Potential COI" alert to the feed
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)
- @AmericanAir88: good suggestion. This could be done potentially very easily by incorporating data from Filter 148 as well as potentially data from Filter 149. I'll File a Phab Ticket. — Insertcleverphrasehere (or here) 15:33, 23 October 2018 (UTC)
82. Skip viewed articles
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)
- While I am more of a generalist, and prefer to review every article I come across one by one, I realise that this is very difficult to do, and most reviewers 'specialise' in one or more areas or aren't comfortable reviewing some articles. Being able to flick through to problem articles or past articles that you don't feel comfortable with and not have to see them again would be very useful. Logged in Phab. — Insertcleverphrasehere (or here) 15:45, 23 October 2018 (UTC)
83. nppbrowser equivalent / keyword search?
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
- Show: (_) articles; (_)redirects; (_) both
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)
- Information I found with Google suggests that Rentier is the person responsible for the NPP Browser software. I don't know how to submit a feature request, a message to Rentier may suffice. — Frayæ (Talk/Spjall) 20:49, 13 October 2018 (UTC)
- I've copied this from the AfC noticeboard as it seems to be a New Page Feed request that would also be of interest to NPR. Adding it to the feed seems smarter than trying to add all drafts to the new page patrol browser. — Insertcleverphrasehere (or here) 15:29, 23 October 2018 (UTC)
85. Special:NewPages to not highlight pages if tagged for deletion, even if unreviewed.
Per this discussion, we are going to stop marking CSDs and PRODs as 'reviewed' in the new pages feed, to stop things falling through the cracks if the CSD tags are inappropriately removed or the PROD removal is missed. However, this presents a problem at Special:NewPages, which currently will highlight all 'unreviewed' or 'unpatrolled' pages in yellow, with no filtering feature like Special:NewPagesFeed. The simple fix is to un-highlight pages tagged for deletion, even if unreviewed. Ideally this should be added as a filtering option similar to the existing:
Show patrolled edits | Hide bots | Show redirects
buttons. An additional button that toggles "un-highlight tagged for deletion" (toggled on by default) would be ideal. — Insertcleverphrasehere (or here) 16:52, 4 November 2018 (UTC)
87. Fix large screen New Pages Feed display to save space
There is a lot of wasted space on the new pages feed. When viewed very zoomed in, it is fine (I guess), and makes use of each line on the left due to test that wraps around. When zoomed out however, it fails to remove this extra line of space, and simply makes each box bigger than it needs to be. The three images at right indicate the problem best. the final one indicates how the feed could be modified to show more items per page. This would be helpful because it would make it easier to see repeated submissions from the same users, and allow scanning a larger number of pages at the same time. — Insertcleverphrasehere (or here) 21:39, 8 November 2018 (UTC)
- Support anything that makes scanning easier. Some people go through one at a time systematically,andthe tool seems to have them principally in mind, but I know I'm not the only frequent patroller who works by scanning ay one time as large a set at I can. DGG ( talk ) 04:47, 14 September 2019 (UTC)
- Support this is a small incremental fix that should be uncontroversial, and probably not so hard to implement? MarioGom (talk) 12:45, 14 November 2021 (UTC)
90. Community Control over criteria for possible issues
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)
- Barkeep49, if you're talking about all the options for comments and tags, etc the Curation flyout, what we need are: CSD delined, PROD declined, user warning for UPE, etc. Can you list in detail here the additions you would like to see?
- On another note entirely, I'm not sure that ORES things are displaying in the AfC feed and that was the main reason for creating the AfC feed. Could you check that - it might be just my browser. Kudpung กุดผึ้ง (talk) 01:58, 26 July 2019 (UTC)
- Well we're soon going to get a potential COI tag added to the list of potential issues. They're going to use edit filters 148 and 149 which are fairly rudimentary but nice enough. At some point in the future we might have some better COI detection tools available. At that point we'll need to go back to the WMF to get them to change. I would like the community to be able to "own" development of the toolbar as much as is feasible so we don't need to go back to the wishlist in a year, two years, 5 years, whatever in order to have the next round of updates done. It seems clear that the WMF isn't interested in supporting page curation except so far as we drum up support from the wishlist. So be it. In that case I would like the community to be able to own it in the same way we do so many other processes.As for AfC it's working for me but it appears in a different place than for NPP. Are you looking right under the review button? Best, Barkeep49 (talk) 02:19, 26 July 2019 (UTC)
- Barkeep49, there's an ORES model currently under development for detecting COI/(U)PE. The end result is expected to highly exceed the currently rudimentary methods of automated COI/(U)PE detection but I have no knowledge about the precise timeline and it does not help that the department is currently understaffed. Now, that I don't expect EFs to grow any more efficient than they are currently are, the next
better COI detection tool
will be near-certainly this ORES-COI-model, for the integration of which, we (obviously) need to go back to WMF. - So, I am inclined to think that the premises of your demand is a bit ill-founded. Also, while I have not followed their work on integrating abuse filters to the system, I can confidently assume that integrating EFs will be a tougher deal than just doing the elementary checks through it's own code-base. I agree 'bout the necessity of moving away from the hard-code style but that was a question which has been already answered wrongly, years ago. ∯WBGconverse 09:37, 13 September 2019 (UTC)
- Winged Blades of Godric, I had not heard about the ores development. That's good news. Best, Barkeep49 (talk) 12:32, 13 September 2019 (UTC)
- Winged Blades of Godric, being understaffed is not an argument. The WMF is greatly over funded. All they need to do is augment their capacity and reduce some of the deadwood. Do you know which department is developing this, and more importantly, who is in charge of it?Kudpung กุดผึ้ง (talk) 02:50, 14 September 2019 (UTC)
- Kudpung, it's the Scoring Platform Team.
- I have known this via off-wiki sources for quite some time but now see T217232 which states :-
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. - On the broader locus, I have had highly interesting discussions between Danny, IFried, James and me, as to funding CommTech and other departments. Will note them, somewhere .... ∯WBGconverse 03:31, 14 September 2019 (UTC)
- Winged Blades of Godric, will you ping me when you do? I'd love to read about it. Best, Barkeep49 (talk) 03:40, 14 September 2019 (UTC)
- The way the funds our unpaid work generates are used is a bubble about to burst. The WMF is under fire on several fronts right now. Stay tuned. Kudpung กุดผึ้ง (talk) 03:42, 14 September 2019 (UTC)
- Barkeep49, I will try to pen them down, when I get some time. Will ping you:-) ∯WBGconverse 04:04, 14 September 2019 (UTC)
- Winged Blades of Godric, will you ping me when you do? I'd love to read about it. Best, Barkeep49 (talk) 03:40, 14 September 2019 (UTC)
- Barkeep49, there's an ORES model currently under development for detecting COI/(U)PE. The end result is expected to highly exceed the currently rudimentary methods of automated COI/(U)PE detection but I have no knowledge about the precise timeline and it does not help that the department is currently understaffed. Now, that I don't expect EFs to grow any more efficient than they are currently are, the next
- Well we're soon going to get a potential COI tag added to the list of potential issues. They're going to use edit filters 148 and 149 which are fairly rudimentary but nice enough. At some point in the future we might have some better COI detection tools available. At that point we'll need to go back to the WMF to get them to change. I would like the community to be able to "own" development of the toolbar as much as is feasible so we don't need to go back to the wishlist in a year, two years, 5 years, whatever in order to have the next round of updates done. It seems clear that the WMF isn't interested in supporting page curation except so far as we drum up support from the wishlist. So be it. In that case I would like the community to be able to own it in the same way we do so many other processes.As for AfC it's working for me but it appears in a different place than for NPP. Are you looking right under the review button? Best, Barkeep49 (talk) 02:19, 26 July 2019 (UTC)
91. Send message to all article creators thanking them - differing based on article state
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.
92. Have redirects be indexed after same length of time as articles
Quoting Rosguill The backlog length for the New Pages Queue for articles is 90 days, but several weeks ago editors realized that redirects were dropping off of the queue after only 30 days. In practice, this means that many if not most redirects will not be reviewed. This problem would be solved if the backlogs were both 90 days long. Note that currently there should be no redirects older than 20-something days in the queue, as once we noticed the problem a few editors made sure to keep the back of the queue patrolled.
. Best, Barkeep49 (talk) 23:10, 11 August 2019 (UTC)
- Implementing this is trivial. But, it can't proceed unless MusikAnimal is done with his calculations on the impact of this on database-storage or some DBA gives clearance. ∯WBGconverse 10:32, 13 September 2019 (UTC)
- @Winged Blades of Godric: That task was removed from Community Tech's board because it wasn't on the wishlist. It is super trivial to fix (which is why we were going to do it), but as we discovered, some years ago redirects were intentionally changed to be removed from the queue after only 30 days. We're not sure why! I can only suspect it's because the massive number of rows that would be added as a result. I think the decision is going to be with the DBAs, who may not take kindly to that much extra storage. Not that it's your responsibility, but anyone can do the math if you know how to run some SQL queries. Basically there are a bunch of "tags" for each entry in the queue, and we'd need to multiply that times however many redirects would be added from the extra 60 days worth of data, then evaluate the costs/benefits. This of course would be a rough estimate. Frankly I think phab:T228952 should happen first, which is very non-trivial. Most of this is because of decisions that were made in the design of PageTriage from well before we worked on it. We've improved it quite a bit, but it's still a painful battle trying to make any architectural changes. — MusikAnimal talk 19:50, 13 September 2019 (UTC)
- @Rosguill, Winged Blades of Godric, MusikAnimal, Barkeep49, and Insertcleverphrasehere:, I remember discussing the drop off time with the devs some time ago - I think it was during the run uo to ACTRIAL - and we agreed to fix it at 90 days. However, in view of the lack of enthusiasm to patroll pages, even that may not be long enough. At the time, I naturally assumed that all pages that come under review at NPP would be subject to 90 days, so it was not queried. I think this is important because redirects are the one way that spammers game the system to recreate deleted pages. More important than phab:T228952, - which I don't understand - and which has already been shelved anyway. Kudpung กุดผึ้ง (talk) 02:43, 14 September 2019 (UTC)
- Kudpung, we're missing the 90 days mark some of the time now but I think that roughly a quarter of a year is a fair compromise between not letting bad stuff appear in Google and giving us a reasonable amount of time to get to articles. Plus to some degree deadlines help. The fact that redirects just disappear from the queue rather than sitting there makes sense to me - redirects are cheap and the cost of not patrolling them is less. However combining this with the 30 day drop-off is not a great combo. MusikAnimal's point about the painful battle of PageTriage (one I'd love for him to repeat at our current conversatoin but understand if he can't) is why addressing that for me is the biggest priority. Best, Barkeep49 (talk) 02:58, 14 September 2019 (UTC)
- @Rosguill, Winged Blades of Godric, MusikAnimal, Barkeep49, and Insertcleverphrasehere:, I remember discussing the drop off time with the devs some time ago - I think it was during the run uo to ACTRIAL - and we agreed to fix it at 90 days. However, in view of the lack of enthusiasm to patroll pages, even that may not be long enough. At the time, I naturally assumed that all pages that come under review at NPP would be subject to 90 days, so it was not queried. I think this is important because redirects are the one way that spammers game the system to recreate deleted pages. More important than phab:T228952, - which I don't understand - and which has already been shelved anyway. Kudpung กุดผึ้ง (talk) 02:43, 14 September 2019 (UTC)
- @Winged Blades of Godric: That task was removed from Community Tech's board because it wasn't on the wishlist. It is super trivial to fix (which is why we were going to do it), but as we discovered, some years ago redirects were intentionally changed to be removed from the queue after only 30 days. We're not sure why! I can only suspect it's because the massive number of rows that would be added as a result. I think the decision is going to be with the DBAs, who may not take kindly to that much extra storage. Not that it's your responsibility, but anyone can do the math if you know how to run some SQL queries. Basically there are a bunch of "tags" for each entry in the queue, and we'd need to multiply that times however many redirects would be added from the extra 60 days worth of data, then evaluate the costs/benefits. This of course would be a rough estimate. Frankly I think phab:T228952 should happen first, which is very non-trivial. Most of this is because of decisions that were made in the design of PageTriage from well before we worked on it. We've improved it quite a bit, but it's still a painful battle trying to make any architectural changes. — MusikAnimal talk 19:50, 13 September 2019 (UTC)
- Support much longer drop-off time. What we don't get to now, we should still get to if we can. We won't get to all the old ones any more than now, but they will be there for people who, like myself, try to look for ones whose title or some other indication suggests that there might be a problem. I really do not see the point of having the drop off at all. DGG ( talk ) 04:44, 14 September 2019 (UTC)
- Until a page has been viewed and reviewed, nobody knows what's on it. The face of the waterfall at NPP has changed. There is no denying that while an encyclopedia can never be complete, most of the traditional encyclopedic topics are catered for and being updated and maintained. What we are left with are the incessant non notable bios and autobios, footballers whose footy SNG has an even lower bar than BASIC or GNG, reality shows, Bollywood, and more bios. The new enhancements to the entries in the feed provided by ORES provide an excellent overview already, although some things might be missed by newer reviewers through banner blindness, or those who patrol too fast. It's therefore essential that nothing gets indexed before it has been checked. I think here is now a very strong argument to extend the 90 day drop off, or even have it open ended per DGG. The disadvantage with the latter however, is that reviewers will continue to go for the low hanging fruit knowing that there would no longer be a sense of urgency. Kudpung กุดผึ้ง (talk) 05:31, 14 September 2019 (UTC)
93. Orphan in possible issues
Hi greetings, I'd like to suggest an improvement in page curation toolbar. We know, while using the page info in the tool, we can see the possible issues such as No citation, Orphan, etc. The article is seem to be orphan when there is no links from other pages in the main article namespace. But the tool considers the links from pages in all namespaces, not only from mainspace. Sometimes new articles may not have links from other articles, but from pages in other namespaces such as talks, user talks, etc. The tool does not determine it as orphan, but actually the article is orphan. It will be a great help, if the tool consider the links only from mainspace while determining whether the article is orphan or not. Hope that this issue will fixed. Regards.--PATH SLOPU 11:45, 28 September 2019 (UTC)
- Agreed, although it isn't much of a problem to be honest as users will rarely link non-existant articles in talk pages, unless they are linked in the small window between the page being created and the page being reviewed. Nonetheless, if this is the case, I would support a change. Willbb234Talk (please {{ping}} me in replies) 21:07, 24 November 2019 (UTC)
94. Article Creator From 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)
- phab:T157048 DannyS712 (talk) 23:12, 24 January 2020 (UTC)
Automated messages while reviewing a page or unreviewing it must be optional
Please add a check box at the window to mark the page as reviewed, where it says send a message to the page creator or the reviewer. The sending of message should be optional. --DBigXrayᗙ 17:43, 20 February 2020 (UTC)
Following up from the discussion at Wikipedia talk:New pages patrol/Reviewers#Catching forks, I suggest that the related pages extension be used to display roughly three articles in the "Page Info" panel of the curation tool to help catch content forks and allow reviewers to better familiarize themselves with the context of an article's topic. {{u|Sdkb}} talk 06:08, 22 December 2020 (UTC)
Page info and dab pages
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)
Refine filtering of AfC drafts
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)
Curation tool marks pages with harv refs as uncited
Just a general comment, but the tool currently marks articles that use harv refs such as the {{Sfn}}
template as being uncited. Iazyges Consermonor Opus meum 15:46, 8 October 2021 (UTC)
Please move the “mark as reviewed” checkbox
I do all my reviewing on iPad and the checkbox for “mark as reviewed” is about one fifteenth of a fingertip away from the green bar for “add selected tags”. This means I frequently make fat finger errors and have to go back and unreview an article. Instead of appearing just above the green bar could the checkbox move over to the right to allow clear space between them? Thanks Mccapra (talk) 11:48, 14 November 2021 (UTC)
Expand language
(Brought here from reviewers talk page) As suggested by Bada Kaji - Could we include an option on the Page Curation toolbar to add the tag Expand (language), give us a list of the most common languages translated from and a space to add the foreign language title(s)? I am noticing more pages needing this template lately. Thank you JW 1961 Talk 22:47, 14 November 2021 (UTC)
Expanded info on previous deletions
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:
- 1. Showing Previously deleted (previous AfD) for article XY if one or more Wikipedia:Articles_for_deletion/XY pages exist, helping identify potential reposts.
- 2. Showing Previously deleted (draft exists) for article XY if a Draft: XY page exists, often indicative of a copy-paste to mainspace.
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)
- Agreed. The recreation of redirects, recycled Drafts, and refunded/recreated articles have always been contentious. They should systematically pass through the New Pages Feed feed again. Kudpung กุดผึ้ง (talk) 15:06, 18 November 2021 (UTC)
Mark unpatrolled
This feature, if it doesn't already exist, was suggested by this unanswered question I found while looking at the Help Desk archives.— Vchimpanzee • talk • contributions • 18:00, 23 November 2021 (UTC)
- A patroller can add any page back to the NPP queue by clicking "Add to the New Pages Feed" in the "Tools" left hand menu Polyamorph (talk) 19:58, 23 November 2021 (UTC)
- I'll let the person know. Thanks.— Vchimpanzee • talk • contributions • 20:25, 23 November 2021 (UTC)
Vandalism by Category and Importance?
Is Vandalism on stubs or low rank articles common? And do unwatched articles get more vandalism? I know there can be multiple projects, but the project importance quality table might be good to have in long run, https://en.wikipedia.org/wiki/Wikipedia:Version_1.0_Editorial_Team/Star_Wars_articles_by_quality_statistics Wakelamp d[@-@]b (talk) 08:52, 24 November 2021 (UTC)
Update stub spacing in Page Curation tool
I noticed that the when Page Curation tool tags stubs, it only enters a single line before the tag (Special:Diff/1069309679 for example). WP:STUBSPACING says to leave two blank lines before the first stub tag (I'm guessing the curation tool only inserts the basic tag for others to sort). It looks like at least the User:SD0001/StubSorter script automatically insert the second blank line, but if someone sorts manually, it might leave only the single line. Can the tool be updated to add one more blank line before the {{stub}} tag? A bit of a nit, but seems like a low-hanging fruit update. -2pou (talk) 17:29, 1 February 2022 (UTC)