Some of these are not relevant for new page patrollers: G6 move, G6 XfD, G6 history merge, G8 (both) and G13. As someone who hasn't used PageTriage much, I don't know whether PageTriage aims to be all-encompassing or just to include speedy deletion criteria that apply to new pages.

Some of these are not relevant for new page patrollers: G6 move, G6 XfD, G6 history merge, G8 (both) and G13. As someone who hasn't used PageTriage much, I don't know whether PageTriage aims to be all-encompassing or just to include speedy deletion criteria that apply to new pages.

Just speedy deletion criteria that apply to new pages. I've updated the list.

FYI, this could either be implemented in the extension itself or on-wiki at https://en.wikipedia.org/wiki/MediaWiki:PageTriageExternalDeletionTagsOptions.js.

G6 move, G6 XfD, G6 history merge, G8 (both) and G13: These are all relevant because the admins who still need to patrol the work of the patrollers will effect these jobs when they come across the need (there should be a 'Curate this page' link showing in the side bar for cases where the Curation tool no longer automatically loads, as in the case of previously patrolled pages)..

The whole object of having created Page Curation was to offer the community something better than Twinkle in order to get all patrollers applying the same criteria and levels of judgement, and without having to keep swapping back and forth between Page Curation and Twinkle.

If we are to make best use of the newly created New Page Reviewer user group, we should set a higher priority for these tweaks - and a few more to come.

@Kudpung, @TTO: I've restored the entire list on this ticket per Kudpung. Feel free to discuss further.

We'll probably want to make some of these conditional based on namespace (and more closely match how Twinkle works).

I've attempted to write some documentation for the structure of the on-wiki configuration pages: https://www.mediawiki.org/wiki/Extension:PageTriage#On-wiki_configuration

For the missing A7 criteria in particular I've put some code up on the talk page referenced above that adds these criteria (with the words copied from Twinkle). @Kudpung are you able to add this to https://en.wikipedia.org/wiki/MediaWiki:PageTriageExternalDeletionTagsOptions.js ?

@kaldari: the current configuration makes it easy to add configuration for adding deletion templates to only Main or only User pages, but other namespaces would require the conditional code to be in the configuration JS itself. (I might be wrong in that, I'm still getting my head around the code.) It seems to me that it'd be better to modify the extension to support an extra configuration parameter that lists the namespaces a template does (or doesn't?) apply to.

I'm assuming that there's a longer-term plan in place to make PageTriage wiki-agnostic? If so, then generalising the namespaces thing would make sense as part of that work. (As well as things like not requiring any particular tags to be present in the configuration.)

@Samwilson: Unlike Twinkle, PageTriage is only designed to facilitate new page patrolling, which primarily focuses on Main namespace, and to a lesser degree User namespace. It doesn't support other namespaces at all. If there are deletion templates that don't apply to Main or User namespace, we should not add them to PageTriage.

The idea is to eventually make PageTriage wiki-agnostic, although for the deletion templates, it currently isn't. This isn't an immediate priority though or something we (the Community Tech team) are likely to work on.

If I knew how to add the js I would use my admin access a nd do it immediately. However, I am not a programmer, so I wouldn't have a clue about adding js or any other scripts to any part of Wikipedia or MediaWiki. My role is one of facilitator who from a hands-on aspect recognises the needs for quality control of our encyclopedic content, how it is best done using what we already have (and which can be improved upon), and helping the community to do it best. In that respect, Twinkle is of little actual use for the specific purpose of New Page Reviewing and provides no support for new users or even the reviewers. It doesn't even have a log system which makes it possible to monitor the performance of accredited patrollers. Twinkle's main job is for page protection, user welcomes, warnings and blocks, etc.

We don't strictly need the following because they are tags that are generally applied to older articles for other reasons than simply being new (one of the complaints about Twinkle is that its lists are cluttered).:

• A5: Transwikied articles
• G6: History merge
• G6: Move
• G6: XfD
• G6: Unnecessary disambiguation page
• G6: Copy-and-paste page move
• G6: Housekeeping
• G8: Pages dependent on a non-existent or deleted page
• G8: Subpages with no parent page
• G13: Old, abandoned Articles for Creation submissions

What we do need is the 'CSD declined' feature, and the new 'Move to draft' feature

In T150628#2810252, @Kudpung wrote:

G6 move, G6 XfD, G6 history merge, G8 (both) and G13: These are all relevant because the admins who still need to patrol the work of the patrollers will effect these jobs when they come across the need (there should be a 'Curate this page' link showing in the side bar for cases where the Curation tool no longer automatically loads, as in the case of previously patrolled pages)..

In T150628#2879450, @Kudpung wrote:

We don't strictly need the following because they are tags that are generally applied to older articles for other reasons than simply being new (one of the complaints about Twinkle is that its lists are cluttered).:

I'm confused now...

Thanks @Kudpung, that's great info. So the specific deletion reasons that are still missing from PageTriage are the following?

• A7: Unremarkable person
• A7: Unremarkable musician(s) or band
• A7: Unremarkable club
• A7: Unremarkable company or organization
• A7: Unremarkable website or web content
• A7: Unremarkable individual animal
• A7: Unremarkable organized event
• A11: Obviously made up by creator, and no claim of significance General criteria Custom rationale (custom deletion reason)
• G6: Unnecessary disambiguation page
• G10: Wholly negative, unsourced BLP

I'm not an admin on English Wikipedia, so can't edit the page myself. The code below needs to be added to MediaWiki:PageTriageExternalDeletionTagsOptions.js; would you be able to do that? It's just a matter of copying and pasting. Sorry I can't jump in and do it myself. :-) I'm on IRC if you want to chat.

What we do need is the 'CSD declined' feature, and the new 'Move to draft' feature

See T124396: Allow moving to draftspace and tagging accordingly (keywords: draft, draftify, draftification) for the latter, and I can't find an existing ticket for the CSD declined — do you know if there is one? I think it's a separate feature to this current ticket?

That'a lot of js. I'd be scared I'd break the Wiki. How do I get on to IRC?

In T150628#2879740, @Kudpung wrote:

That'a lot of js. I'd be scared I'd break the Wiki. How do I get on to IRC?

https://en.wikipedia.org/wiki/Wikipedia:IRC/Tutorial

Join #wikimedia-commtech once on IRC.

I'm on IRC now, but Samwilson is not there.

I’m on IRC now but Samwilson is nit there.

Kudpung

@Kudpung what channel are you in? Come and join #wikimedia-commtech (by typing /join #wikimedia-commtech).

@kaldari: would you mind looking over the above code and if you're happy with it, paste it into the en.wp page?

Ok I've synced https://en.wikipedia.org/w/index.php?title=MediaWiki:PageTriageExternalDeletionTagsOptions.js&diff=755211551&oldid=506788360

I did a quick test and it worked as expected, but I did not go through all the criterion. I'm sure we'll hear about it if something is off.

Thanks @MusikAnimal!

@Kudpung does it look okay to you?

Sunday morning now. I'll check it out immediately after breakfast.

They seem to be working as expected but the order of the items on the list needs to be rearranged, and perhaps the generic A&entry shuld be removed.
Also (I don't know if these need to be filed as new Phab requests):

• users have requested that the font size of the 'This article is only X minutes old' alert should be larger, and/or bold, or even in bold red.
• The entire window of the Page Curation fly-out could do with being bigger - like the Twinkle pane. This would also reveal the box to enter the additional criteria to be entered for some of the features.
• The window should be free floating once opened - currently it can only be moved up and down to reveal page parts behind it.

Iwill shortly post the list of criteria in the order in which they should apear in the Creation tool. Also, some of heir descriptions wil have been edited for brevity and less clutter - it is assumed that editors using the tool have read and understood the tutorial, so repeating everything should not be necessary.

This is the list in the order it appears in Twinkle (less the ones that were deliberately left out). I realise this makes a bit more work for someone - my bad, I have been doing NPP for 10 years and I forgot that this is not all evident to everyone. The tooltips are for mouseover as in Twinkle.

Mark this page for speedy deletion only if it fits exactly one of the criteria below. There is no catch-all - if it doesn’t fit, use PROD or AfD.

A1: No context
Tooltip: Articles lacking sufficient context to identify the subject of the article.

A2: Foreign language article that exists on another Wikimedia project
Tooltip: Articles having essentially the same content as an article on another Wikimedia project.

A3: No content
Tooltip: Any article (other than disambiguation pages, redirects, or soft redirects) consisting only of external links, category tags and "see also" sections, a rephrasing of the title, chat-like comments, template tags, and/or images.

A7: Unremarkable person
Tooltip: An article about a real person that does not assert the importance or significance of its subject.

A7: Unremarkable musician(s) or band
Tooltip: Article about a band, singer, musician, or musical ensemble that does not assert the importance or significance of the subject.

A7: Unremarkable club
Tooltip: Article about a club that does not assert the importance or significance of the subject.

A7: Unremarkable company or organization. Does NOT apply to schools or educational establishments.
Tooltip: Article about a company or organization that does not assert the importance or significance of the subject.

A7: Unremarkable website or web content
Tooltip: Blog, online forum, webcomic, podcast, or similar web content that does not assert the importance or significance of its subject.

A7: Unremarkable individual animal
Tooltip: Article about an individual animal (e.g. pet) that does not assert the importance or significance of its subject.

A7: Unremarkable organized event
Tooltip: Article about an organized event (tour, function, meeting, party, etc.) that does not assert the importance or significance of its subject.

A9: Unremarkable musical recording
Tooltip: A musical recording without indication of importance or significance AND where the artist's article does not exist.

A10: Recently created article that duplicates an existing topic
Tooltip: Exists already in English Wikipedia , and does not expand upon any existing article(s) on the subject, and where the title is not a plausible redirect.

A11: Obviously made up
Tooltip: Clearly invented/coined/discovered by the article's creator or someone they know personally, and does not credibly indicate why its subject is important or significant.

G1: Patent nonsense - NOT for non-English pages.
Tooltip: Completely Incoherent text, gibberish, or random typed characters.

G2: Test page
Tooltip: A page created to test editing or other Wikipedia functions.

G3: Vandalism
Tooltip: Plain pure vandalism including redirects left behind by page move vandalism

G3: Blatant hoax
Tooltip: Blatant and obvious misinformation to the point of vandalism.

G4: Recreation of a page that was deleted at AfD
Tooltip: Sufficiently similar and unimproved copy, having any title, of a page deleted via its most recent deletion discussion.

G5: Creations by banned or blocked users
Tooltip: Pages created by banned or blocked users in violation of their ban or block, and which have no substantial edits by others.

G6: Unnecessary disambiguation page
Tooltip: Page disambiguates only two Wikipedia pages or no existing pages, regardless of its title.

G7: Author requests deletion
Tooltip: Pages where the author has requested deletion, either explicitly or by blanking the page.

G10: Attack pages
Tooltip: Pages that disparage, threaten, intimidate or harass their subject or some other entity, and serve no other purpose.

G10: Wholly negative, unsourced BLP
Tooltip: Entirely negative in tone and unsourced; no neutral version in the history to revert to.

G11: Unambiguous advertising or promotion
Tooltip: Exclusively promotional, needing to be fundamentally rewritten to become encyclopedic.

G12: Unambiguous copyright infringement
Tooltip: Copyrighted text or material with no credible assertion of public domain, fair use, or a compatible free license, where there is no non-infringing content on the page worth saving. Text lifted from web sites, books, PDFs, etc.

Thanks @Kudpung! I've updated P4632 to define all tags (not just the new ones); this means they can go in the correct order.

The Unnecessary disambiguation page (G6) item (to insert db-disambig) doesn't have a talk-page notification template; is this correct?

In T150628#2884547, @Kudpung wrote:

Also (I don't know if these need to be filed as new Phab requests):

• users have requested that the font size of the 'This article is only X minutes old' alert should be larger, and/or bold, or even in bold red.
• The entire window of the Page Curation fly-out could do with being bigger - like the Twinkle pane. This would also reveal the box to enter the additional criteria to be entered for some of the features.
• The window should be free floating once opened - currently it can only be moved up and down to reveal page parts behind it.

Oh and yes, I think these should be separate tasks.

• The window should be free floating once opened - currently it can only be moved up and down to reveal page parts behind it.

@Kudpung: You should be able to drag the window anywhere you want. Can you double check this? If it isn't working for you, please file a new ticket for that and be sure to put what browser you are using.

I don't think CommTech is going to be able to work on the new requests, but it will be good to have them in Phabricator.

@Samwilson: I created a new template for the disambiguation warning and added it to the code: https://en.wikipedia.org/wiki/Template:Db-disambig-notice-NPF.

In T150628#2888175, @kaldari wrote:

I don't think CommTech is going to be able to work on the new requests, but it will be good to have them in Phabricator.

This is only the beginning of a few necessary tweaks to Page Curation . So if 'CommTech' can't, where is the other venue to request them to be done by another department?

In T150628#2885613, @Samwilson wrote:

Thanks @Kudpung! I've updated P4632 to define all tags (not just the new ones); this means they can go in the correct order.

The Unnecessary disambiguation page (G6) item (to insert db-disambig) doesn't have a talk-page notification template; is this correct?

Not that I know of. Is it possible, in order to reduce clutter , to provide those descriptions as mouseover tooltips?

In T150628#2885613, @Samwilson wrote:

Thanks @Kudpung! I've updated P4632 to define all tags (not just the new ones); this means they can go in the correct order.

The Unnecessary disambiguation page (G6) item (to insert db-disambig) doesn't have a talk-page notification template; is this correct?

Not that I know of. Is it possible, in order to reduce clutter , to provide those descriptions as mouseover tooltips?

FYI, I've nominated the Db-inc and Db-club CSD templates to be merged (since they are both about non-notable organizations): https://en.wikipedia.org/wiki/Wikipedia:Templates_for_discussion/Log/2016_December_19#Template:Db-inc.

This is only the beginning of a few necessary tweaks to Page Curation . So if 'CommTech' can't, where is the other venue to request them to be done by another department?

@Kudpung: This is the correct venue (regardless of which team will work on it). Do you want to create the tickets for the additional requests or would you prefer that one of us create them for you (since I know Phabricator isn't the most intuitive software to use)?

Not that I know of. Is it possible, in order to reduce clutter , to provide those descriptions as mouseover tooltips?

This will also need to be filed as a separate ticket.

This doesn't look like HTML, but if someone will give me a line of code of whatever code it is, as this is an admin-accessible script I'll add it myself to all the portions of the script for each CSD criteria. If no body wants to do it here, please put it on my en.Wiki talk page. I have a newsletter waiting to go out to reviewers.

@Kudpung: It's not HTML, it's just a set of configuration values that are processed by the code for PageTriage. Adding support for tooltips will require significant software changes within the PageTriage extension. Also, I don't think it's a good idea personally. I think it would be much better to shorten the descriptions rather than hiding them behind tooltips.

OK. So I can edit the texts in the js for less clutter? Is is posible to put Wikilinks in those texts, like for example back to the policy pages? Or doesn't that work either outside the Pagetriage extension?

@Kudpung: Currently, it is not possible to add links in the descriptions. The descriptions are just treated as raw text and are not parsed for HTML or WikiText.

OK. So I can edit the texts in the js for less clutter?

Yes, as an administrator, you are able to edit the texts. Just make sure you retain the quotation marks around them or it will cause a syntax error.