Расширение:PageTriage

The new page should appear, flagged as "Нет категорий", "Возможно, страница-сирота", etc. To see the page curation toolbar:

• Echo - Allows users to receive notifications for things like when an article they created has been marked as reviewed.
• ORES - In Special:NewPagesFeed, allows filtering by "predicted class" (articlequality: stub, start, c-class, b-class, good, featured) and "potential issues" (draftquality: vandalism, spam, attack, copyvio). The predictions are done with machine learning (except for copyvio, which is done via a third party bot using an API, but is included here because draftquality needs to be turned on). ORES AI is typically trained by editors via https://labels.wmflabs.org/ui/, or by analyzing reverts. The ORES database provides probabilities which are accessed via the ORES extension. A threshold (tolerable false positive rate) is applied to this data, and some of the thresholds are set in the ORES extension's extension.json file.
• WikiLove - Adds a button to the Page Curation toolbar that allows you to leave a person a barnstar more easily.

By default, the draft namespace is disabled, but can be enabled with the following update to LocalSettings.php

// These three settings are optional, and will enable the Articles-for-Creation mode.
$wgPageTriageDraftNamespaceId = 118;
$wgExtraNamespaces[ $wgPageTriageDraftNamespaceId ] = 'Draft';
$wgExtraNamespaces[ $wgPageTriageDraftNamespaceId + 1 ] = 'Draft_talk';

When enabled, a new "articles for creation" tab will show up on Special:NewPagesFeed.

By default pages edited in the draft namespace will be "unsubmitted".

Articles in the draft namespace can be submitted for review by adding [[Category:Pending_AfC_submissions]] to the draft page. At which point they will show up under "awaiting review".

Note the toolbar controlled by the configuration variable $wgPageTriageEnableCurationToolbar does not show up in the draft namespace.

To make sure old articles are eventually taken out of the new pages feed, you should set up a cron job to run the following file every 48 hours: cron/updatePageTriageQueue.php

• Enable draftspace by following the directions above in the section #Enabling draft namespace.
• In Special:NewPagesFeed, to place a draft in one of the AFC states, you need to create a page in the "Draft" namespace, and add it to the following categories:
  • Unsubmitted: (no category)
  • Awaiting review: Category:Pending AfC submissions
  • Under review: Category:Pending AfC submissions being reviewed now
  • Declined: Category:Declined AfC submissions

Note: The Page Curation toolbar does not display for drafts.

Enwiki has the ORES extension installed, which provides machine learning predictions of an article's quality and of some common issues. ORES works fine in production, but requires some setup if you want to test in a localhost environment. It can be desirable to test with ORES turned on, for example, if you are changing the layout of Special:NewPagesFeed. Here is a localhost testing procedure:

• Clone Extension:ORES and add wfLoadExtension( 'ORES' ); in LocalSettings.php
• Add this to LocalSettings.php

$wgPageTriageEnableOresFilters = true;
$wgOresWikiId = 'enwiki';
$wgOresModels = [
	'articlequality' => [ 'enabled' => true, 'namespaces' => [ 0 ], 'cleanParent' => true ],
	'draftquality' => [ 'enabled' => true, 'namespaces' => [ 0 ], 'types' => [ 1 ] ]
];

• Run php extensions/ORES/maintenance/BackfillPageTriageQueue.php

There are status codes used to track whether a page is reviewed or not. These are the values given when you query patrol_status, ptrp_reviewed, and ptrl_reviewed:

• Unreviewed
  • 0 - unreviewed
• Reviewed
  • 1 - reviewed (someone clicked the green check mark in the Page Curation toolbar)
  • 2 - patrolled (someone clicked the "Mark as patrolled" link at the bottom right corner of a page)
  • 3 - autopatrolled (someone with the autopatrol user right created the page, or moved the page from a non-tracked namespace to a tracked namespace)
  • no result - will occur if the page is not in a tracked namespace (mainspace, userspace, and draftspace), if the article was created before PageTriage was installed, or if the article was reviewed for longer than 30 days (these records are deleted by a cron job)

To check the review status of pages using an API query, you can use api.php?action=query&prop=isreviewed.

Sample JavaScript code:

/**
 * @param {number} pageID The page ID number. A positive number with no commas.
 */
async isReviewed(pageID) {
	let api = new mw.Api();
	let response = await api.get( {
		action: 'query',
		format: 'json',
		formatversion: '2',
		prop: 'isreviewed',
		pageids: pageID,
	} );
	return response.query.pages[0].isreviewed;
}

/**
 * @param {string} title One title. Can include namespace. Example: User:Test
 */
async function isReviewed(title) {
	let api = new mw.Api();
	let response = await api.get( {
		action: 'query',
		format: 'json',
		formatversion: '2',
		prop: 'isreviewed',
		titles: title,
	} );
	return response.query.pages[0].isreviewed;
}

To check the review status of pages using an SQL query, you need to query the pagetriage_page table and the ptrp_reviewed field. Follow the directions in #Status codes to interpret the values of this field.

/* By page_id */
SELECT ptrp_reviewed
FROM pagetriage_page
WHERE ptrp_page_id = 71318376

/* By page_title and page_namespace */
SELECT ptrp_reviewed
FROM pagetriage_page
JOIN page ON page_id = ptrp_page_id
WHERE page_title = 'Živko_Kostadinović' -- underscores, not spaces
	AND page_namespace = 0

pagetriage_page_tags data is updated by calling ArticleCompileProcessor::newFromPageId( [ $pageId ] )->compileMetadata(). This is called in the following hooks:

• onPageMoveComplete() - runs when moving a page
• onLinksUpdateComplete() - runs when saving an edit
• onMarkPatrolledComplete() - runs when clicking the "Mark this page as patrolled" link in bottom right corner of certain pages

It is called asynchronously. The user will see that their edit succeeded and can continue browsing the website, and the page tags update will occur in the background, invisibly to the user.

The pagetriage_page_tags are as follows:

• Author information
  • user_id
  • user_name - there's a filter where you can type in their username
  • user_editcount
  • user_creation_date
  • user_autoconfirmed
  • user_experience - Experience level: newcomer (non-autoconfirmed), learner (newly autoconfirmed), experienced, or anonymous. These experience levels are baked into core and can be accessed with MediaWikiServices::getInstance()->getUserFactory()->newFromUserIdentity( $performer )->getExperienceLevel()
  • user_bot
  • user_block_status
• Deletion tags - will display a black trash can icon if marked for deletion
  • afd_status
  • blp_prod_status
  • csd_status
  • prod_status
• Special:NewPagesFeed red warning text
  • category_count - No categories
  • linkcount - Orphan
  • reference - No citations
  • recreated - Previously deleted
  • user_block_status - Blocked
• Page information
  • page_len - size of article, in bytes
  • rev_count - number of edits to the article
  • snippet - text from beginning of article, used in Special:NewPagesFeed to preview the article
• afc_state - 1 unsubmitted, 2 pending, 3 under review, 4 declined
• copyvio - latest revision ID that has been tagged as a likely copyright violation, if any

The extension is based on the 'patrol' right. For more information about configuring patrolling, see Manual:Patrolling .

The following logs are created by the extension:

Here is a list of some actions and the corresponding entry points they trigger:

NOINDEX refers to the HTML code <meta name="robots" content="noindex">, which can be inserted into a page to stop the page from appearing in search engine results. In default installations of MediaWiki, all pages are indexed unless they contain the wikicode __NOINDEX__. When $wgPageTriageNoIndexUnreviewedNewArticles is set to true, PageTriage will take over deciding what pages are indexed. The logic that determines this is located in includes/Hooks.php, in the onArticleViewFooter() method.

• First check: Noindex the page if ALL of the following are true:
  • $wgPageTriageNoIndexUnreviewedNewArticles is turned on
  • Page age is less than $wgPageTriageMaxAge (set to 90 days on enwiki)
  • Page is in pagetriage_page table^[1]
  • Page is marked as unpatrolled (ptrp_status = 0)

• Second check: If the wikitext has the __NOINDEX__ magic word, noindex the page if ALL of the following are true:
  • Page age is less than $wgPageTriageMaxNoIndexAge (set to 90 days on enwiki)
  • If $wgPageTriageMaxNoIndexAge is not null, page is in pagetriage_page table^[2]

The main use case for the __NOINDEX__ magic word is in deletion templates and maintenance tag templates that are transcluded into mainspace or draftspace. See this search.

In regards to the requirement "Page is in pagetriage_page table", there are several ways a for a page to get into this table:

• Not been deleted by a PageTriage cron job
  • One cron job deletes redirects older than $wgPageTriageRedirectAutoreviewAge days old (default 180 days as of Sep 2022), regardless of patrol status. In other words, this cron job autopatrols them.
  • Another cron job deletes reviewed pages after 30 days of being reviewed
• In a namespace that PageTriage is configured to patrol
• Isn't an article that is so old it predates the installation of PageTriage

• /modules/
  • ext.pageTriage.article - related to marking an article as reviewed
  • ext.pageTriage.defaultTagsOptions - lists of deletion tags and maintenance tags used by the Page Curation toolbar
  • ext.pageTriage.init - creates a mw.pageTriage object
  • ext.pageTriage.newPagesFeed - Special:NewPagesFeed
  • ext.pageTriage.sidebarLink - related to the "Add to the New Pages feed" link that shows up in the left menu toolbox, and the ooui alert box it generates
  • ext.pageTriage.toolbar - Page Curation toolbar
  • ext.pageTriage.toolbarStartup - ActionQueue and toolbar startup code
  • ext.pageTriage.util - Backbone.js models (article, revision, stats)
  • external - contains external libraries including backbone, jquery.tipoff, jquery.badge, jquery.waypoint, and underscore

The toolbar has three states: maximized, minimized, and hidden. The maximized toolbar is the full-size toolbar with all buttons. The minimized toolbar still displays and floats, but simply says "Curation" and has an X you can click to close it. The hidden toolbar doesn't display at all, and can be re-opened by clicking the "Open Page Curation" link in the left menu.

• front end
  • old (moving away from)
    • Backbone.js
    • jQuery
    • jQuery Badge
    • jQuery Waypoints
    • jQuery UI
    • Mustache (template system)
    • OOUI - used in modules/ext.PageTriage.enqueue (codesearch)
    • Underscore.js
  • new (moving towards)
    • Codex
    • Moment.js
    • Vue

Backbone and Underscore are unusual libraries to use in MediaWiki extensions, and jQuery UI is deprecated. Long term, we are interested in replacing these front end libraries, to make the extension easier to maintain.

• ext.pageTriage.toolbar.ready

PageTriage provides a specialised action queue system to allow other scripts and gadgets to integrate with it. This is similar to mw.hook except that it uses promises. This is done using the mw.pageTriage.actionQueue module. See the comments in the source code for documentation on how the system works. It is not currently used by any scripts or gadgets on enwiki, but it is used internally by PageTriage.

The actionQueue module is available after the mw.hook ext.pageTriage.toolbar.ready fires. PageTriage will give the action queue handler an Object with the following data, in addition to other data as noted below:

• pageid — ID of the page being reviewed.
• title — Title of the page, including namespace.
• reviewer — Username of who is using PageTriage.
• creator — Username of the creator of the page.
• reviewed — Whether or not the page is currently or will be marked as reviewed.

• delete — Fired when the reviewer tags a page for deletion. The data given to the handler also includes:
  • tags — An object of all the templates added to the page. The keys are the template title, and the values are an object of metadata, including things like the speedy deletion code.
• mark — Fired when the review status of a page is changed. Also includes:
  • note — The personal message the reviewer added for the creator of the page. This may be blank.
• tags — Fired when maintenance tags are added to the page. Also includes:
  • tags — An array of the titles of all templates that were added to the page.
  • note — The personal message the reviewer added for the creator of the page. This may be blank.

$( function () {
	// You must first listen for the ext.pageTriage.toolbar.ready event using mw.hook, to ensure your handler is registered at the right time.
	mw.hook( 'ext.pageTriage.toolbar.ready' ).add( function ( queue ) {
    	// Listen for the 'mark' action.
		queue.add( 'mark', function ( data ) {
			return new mw.Api().edit( 'Sandbox', function ( revision ) {
				// Replace 'foo' with the note the reviewer left.
				return revision.content.replace( 'foo', data.note );
			} );
		} );
	} );
} );

Preferences such as the user's Special:NewPagesFeed selected filters are stored as MediaWiki user preferences. The preference name is userjs-NewPagesFeedFilterOptions. It is set using mw.Api().saveOption() and read using mw.user.options.get(). This data ends up in the SQL user_properties table. Temporary accounts (IP masking) will not be able to store their preferences.

This extension was designed for English Wikipedia. There is interest in changing its code and making it more useful to other wikis (phab:T50552), however this is challenging from a technical perspective and progress is slow. For now, the following are true:

• PageTriage is allowed to be installed on other wikis^[3] (although as of 2024 this hasn't happened yet).
• The setting $wgPageTriageEnableExtendedFeatures can be set to false to turn off English Wikipedia-specific features such as maintenance tags and deletion tags in the Page Curation toolbar.
• There are concerns that the noindex features (controlled by $wgPageTriageNoIndexUnreviewedNewArticles and $wgPageTriageMaxNoIndexAge) create search engine optimization problems, and these noindex features should not be enabled on new wikis without first discussing it with product manager Samwalton9 (WMF).
• Like most other WMF-deployed extensions, PageTriage supports internationalization, and has its interface translated into many other languages.

• commons:Category:PageTriage extension
• Help:New pages feed
• w:Wikipedia:Page Curation/Help