Extension:PageTriage
PageTriage リリースの状態: 安定 |
|
---|---|
実装 | 特別ページ , ユーザー インターフェイス |
説明 | 新規ページのレビューと承認を容易にする |
作者 | Ryan Kaldari, Benny Situ |
互換性の方針 | MediaWiki とともにリリースされるスナップショット。 master には後方互換性がありません。 |
MediaWiki | >= 1.43.0 |
データベースの変更 | はい |
テーブル | pagetriage_log pagetriage_page pagetriage_page_tags pagetriage_tags |
ライセンス | MIT ライセンス |
ダウンロード | |
例 | Special:NewPagesFeed on the English Wikipedia |
|
|
|
|
|
|
四半期ごとのダウンロード数 | 15 (Ranked 124th) |
translatewiki.net で翻訳を利用できる場合は、PageTriage 拡張機能の翻訳にご協力ください | |
問題点 | 未解決のタスク · バグを報告 |
PageTriage(ページトリアージ)拡張機能は、新しく作成された記事の予備的な評価(トリアージ)に使えるよう、機能豊富なインターフェイスを提供します。 その目的は既存のコア機能「新しいページの巡回」を置き換え、新規の記事にタグ付けし評価や改善の機能を追加することです。 新規立項のページに適用すると「巡回者」権限のある人向けに、「Special:NewPagesFeed」とページ査読ツールバーを追加します。 開発担当は、ウィキメディア財団のFeatures 拡張機能技術チームです。 もっと詳しい情報はPage Curation(ページの査読)をご参照ください。
ここで要点として特筆しておくと、設定とコードの一部はウィキペディア英語版のワークフローに固有であり、現在の構成では拡張機能の国際化はほぼ不可能です。 (Phabricator:T50552 を参照してください。)
インストール
- ダウンロードして、ファイルを
extensions/
フォルダー内のPageTriage
という名前のディレクトリ内に配置します。
開発者とコード寄稿者は、上記の代わりに以下を使用してGitからインストールします:cd extensions/
git clone https://gerrit.wikimedia.org/r/mediawiki/extensions/PageTriage - 以下のコードを LocalSettings.php ファイルの末尾に追加します:
wfLoadExtension( 'PageTriage' );
- 更新スクリプトを実行します。このスクリプトは、この拡張機能が必要とするデータベーステーブルを自動的に作成します。
- 完了 – ウィキの「Special:Version」に移動して、拡張機能が正しくインストールされたことを確認します。
Checking for successful install
この拡張機能の働きを実際に見るには:
- ログインしていない利用者として新しいページを作成し、内容は適当に文を2、3書き込み保存。
- Special:NewPagesFeedを開く
すると新規ページが一覧になるので、フラグの「カテゴリなし」「孤立」などを確認。 ページキュレーションツールバーを表示するには :
- 「システム管理者」権限のあるアカウントでログイン、もしくは「巡回」権限のあるグループを追加してそのグループにあらかじめ特定の利用者名を加えておき、その利用者としてログイン。
- Special:NewPagesFeed を開く
- ここで新規ページの隣に「査読」ボタンが表示されたはずです。
- これをクリックすると新規のページに査読ツールバーが表示されます。
高度なインストール
追加の拡張機能
PageTriage は拡張機能がなくても動作し、機能を全て利用するには追加の拡張機能も必要でインストールします。
- 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 becausedraftquality
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.
Enabling draft namespace
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.
Cron jobs
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
Manual testing
Special:NewPagesFeed -> Articles for Creation
- 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.
ORES
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' );
inLocalSettings.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
Determining if a page is reviewed
Status codes
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)
Via the API
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;
}
Via SQL
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
SQL
SQL tables
Name | Prefix | Description | Old entry deletion strategy | Service classes (when refactoring, SQL queries should be moved to here) | Data classes |
---|---|---|---|---|---|
pagetriage_page | ptrp_ | The main table. Log of all pages created after PageTriage was installed. One entry per page. Stores the "mark as reviewed" statuses mentioned above. Also stores the last time a tag was placed on the page by PageTriage. Query ptrp_reviewed > 0 in this table to figure out if a page is marked as reviewed. No entry also means the page is reviewed.
|
All articles deleted once ptrp_reviewed > 0 (marked as reviewed) and older than 30 days. All redirects deleted after 180 days regardless of patrol status.
|
QueueManager, QueueLookup | QueueRecord |
pagetriage_page_tags | ptrpt_ | Stores metadata about pages, to make the filters in the Page Curation toolbar work. For example, if you pick the filter "Were previously deleted", then PageTriage will query this table looking for the recreated tag ID. The tag ID is discovered by checking the pagetriage_tags table. See #pagetriage_page_tags for list of tags.
|
All article metadata deleted once ptrp_reviewed > 0 (marked as reviewed) and older than 30 days. All redirect metadata deleted after 180 days regardless of patrol status.
|
||
pagetriage_tags | ptrt_ | A dictionary of page_tags, and their corresponding ID number. See #pagetriage_page_tags for list of tags. |
pagetriage_page_tags
pagetriage_page_tags
data is updated by calling ArticleCompileProcessor::newFromPageId( [ $pageId ] )->compileMetadata()
. This is called in the following hooks:
onPageMoveComplete()
- runs when moving a pageonLinksUpdateComplete()
- runs when saving an editonMarkPatrolledComplete()
- 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.
List of tags
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
PHP
拡張機能の設定
拡張機能は「巡回」権限に基づいています。 巡回の設定については、Manual:巡回 を参照してください。
利用者の LocalSettings.php file ファイルから以下の設定変数を書き込みます。
Variable | Default | Description |
---|---|---|
$wgPageTriageEnableCurationToolbar
|
true
|
false を選ぶと査読ツールバーを無効にする。 |
$wgPageTriageInfiniteScrolling
|
true
|
新しいページフィードで無限スクロールを使用するか否か |
$wgPageTriageMaxAge
|
90 | The age (in days) at which PageTriage allows unreviewed articles to become indexed by search engines (if $wgPageTriageNoIndexUnreviewedNewArticles is true). |
$wgPageTriageNamespaces
|
NS_MAIN | The namespaces that PageTriage is active in. |
$wgPageTriageNoIndexUnreviewedNewArticles
|
false
|
レビューが未処理の新しい記事を索引対象外の noindex に設定する場合は、true に設定します。 言い換えるなら、査読が終わるまでは、検索エンジンに拾われないようにすることです。 |
設定変数の総覧は extension.json を参照してください。
API
PageTriage が追加する以下の API エンドポイントでは次のことができます。
API | Description | Type | Triggering action |
---|---|---|---|
pagetriageaction | 当該のページに査読の有無をマークし、操作の履歴をSpecial:Logに記録。 | Write |
|
pagetriagelist | 検索結果からページの一覧を取得し、査読の状態を含めてそれぞれのメタデータを添えます。 To retrieve one page, you must provide the page_id . To provide multiple pages, you must select one of showreviewed /showunreviewed , and one of showredirs /showdeleted /showothers , or no pages will be returned.
|
Read |
|
pagetriagestats | Special:NewPagesFeed のヘッダで使うため、クエリで検知したページの一覧を取得 | Read |
|
pagetriagetagcopyvio | Mark an article as a potential copyright violation, and logs the action in Special:Log. | Write |
|
pagetriagetagging | 当該のページにクリーンナップ用タグもしくは削除テンプレートを付け、処理のログを Special:Log に書き込むこと。 | Write |
|
Special:Log
The following logs are created by the extension:
Special:Log | log_type
|
log_action
|
Description | Notes |
---|---|---|---|---|
Page curation log | pagetriage-curation | delete, enqueue, reviewed, tag, unreviewed | Logs deletion tagging, maintenance tagging, marking page as reviewed, marking page as unreviewed | |
Potential copyright violation log | pagetriage-copyvio | insert | Allows a bot to log potential copyright violations | Doesn't display unless you set $wgPageTriageEnableCopyvio to true
|
エントリー ポイント
以下のさまざまな操作から、この拡張機能が起動します。
Entry point type | File location | Notes |
---|---|---|
5 APIs | includes/Api/* | |
1 special page | includes/SpecialNewPagesFeed.php | |
20 hooks |
|
|
1 cron job | cron/updatePageTriageQueue.php | runs every 48 hours |
7 maintenance scripts | maintenance/* | need to be run manually |
Here is a list of some actions and the corresponding entry points they trigger:
Action | Entry points used |
---|---|
View Main page |
|
Save an edit to the Main page |
|
Type in search box, triggering search suggestions |
|
View Special:NewPagesFeed |
|
View an unreviewed article while logged in
and having the |
|
Hooks
File | Group | Hook | Actions it performs |
---|---|---|---|
Hooks.php | Move page | onPageMoveComplete | Changes patrolled status, updates cache, updates metadata in pagetriage_page_tags table.
|
Edit page | onRevisionFromEditComplete | Handles marking redirects that flip to articles as unreviewed. DeferredUpdate. | |
onPageSaveComplete | Add new articles to the New Pages Feed and pagetriage_page table.
| ||
onLinksUpdateComplete | DeferredUpdate of metadata / pagetriage_page_tags table.
| ||
Every page load | onArticleViewFooter |
| |
Help:Patrolled edits | onMarkPatrolledComplete | Marking as patrolled (the patrol link shows up in template namespace, for example) will also mark as reviewed in PageTriage. | |
Blocking and unblocking | onBlockIpComplete | Update article metadata / pagetriage_page_tags when a user gets blocked or unblocked. This is so Special:NewPagesFeed can display "Blocked" by articles created by blocked users.
| |
onUnblockUserComplete | |||
onResourceLoaderGetConfigVars | Adjusts some config vars related to draft namespace ID. | ||
Extension:Echo | onBeforeCreateEchoEvent | Code that makes PageTriage Echo notifications work. For example, the notification to article creators that their article was marked as reviewed. | |
onEchoGetDefaultNotifiedUsers | |||
onLocalUserCreated | |||
Extension:ORES | onORESCheckModels | Code that makes PageTriage ORES filters in Special:NewPagesFeed work. For example, filtering by article size or by predicted vandalism/spam/copyvio. | |
Help:Tags | onListDefinedTags | Code that makes PageTriage tags work. Tags can be attached to individual revisions to show that a tool helped make the edit. For PageTriage, it tags edits "PageTriage". | |
onChangeTagsAllowedAdd | |||
onChangeTagsListActive | |||
API | onApiMain__moduleManager | Disables the pagetriagetagging API, if that feature is turned off in PageTriage's settings. | |
Delete or undelete page | onPageDeleteComplete | If a page is deleted, also delete its data from the PageTriage queue, and remove it from the cache. | |
HookHandlers/
UndeleteHookHandler.php |
onArticleUndelete | If a page is undeleted, add it back to the PageTriage queue, regardless of autopatrol status. Fixes a bug where undeleted pages were automatically marked as reviewed. | |
HookHandlers/ Schema.php | SQL | onLoadExtensionSchemaUpdates |
|
Cron jobs and maintenance scripts
File | What it does | Why run it? When is it useful? | Safe to delete maintenance script? |
---|---|---|---|
cron/updatePageTriageQueue.php | Every 48 hours, remove some items from the new pages feed after certain time limits. Removed items can be re-added by clicking "Add to the New Pages Feed". | Keeps the SQL tables from getting too big. | |
maintenance/cleanupPageTriage.php | Remove page with namespace other than NS_MAIN/NS_USER from pagetriage queue. | Fix a bug? T321982 | |
maintenance/cleanupPageTriageLog.php | Maintenance script that updates parameter name from '4::tags' to 'tags' in pagetriage-curation log and (now defunct) pagetriage-deletion log | One time conversion of old log entries to modern format? Logs are now always written in the new format. [1]. | Probably |
maintenance/cleanupPageTriagePageTags.php | Remove page from pagetriage_page_tags if they are not in pagetriage_page
|
Fix a bug that made it into production. All solved now. [2]. | Probably |
maintenance/DeleteAfcStates.php | Delete the afc_state tag value for every page in the queue (drafts and non-drafts). Normally all pages have this tag even if they're not drafts. | Fix a bug that made it into production. All solved now. [3]. T203184#4592953. | Probably |
maintenance/FixNominatedForDeletion.php | Set pagetriage_page.ptrp_deleted if the page is has any pagetriage_page_tags related to deletion (e.g. prod_status, blp_prod_status, etc.)
|
Fix a bug that made it into production. All solved now. [4]. T202582. | Probably |
maintenance/populateDraftQueue.php | Add missing Draft namespace pages to the AfC triage queue. | Related to deploying PageTriage's draftspace feature into an environment that already has a draftspace. [5]. | |
maintenance/updateUserMetadata.php | Former cron job. Update expired user metadata in the pagetriage_page_tags table
|
[6]. T341432. |
NOINDEX
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
- 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
- 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 inpagetriage_page
table[2]
- Page age is less than
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.
Is the page in the pagetriage_page
table?
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
- One cron job deletes redirects older than
- In a namespace that PageTriage is configured to patrol
- Isn't an article that is so old it predates the installation of PageTriage
JavaScript
Directory structure
- /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.
External libraries
- 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
- old (moving away from)
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.
クライアント側のフック
mw.hook
ext.pageTriage.toolbar.ready
mw.pageTriage.actionQueue
PageTriage が提供する専門的なアクションキュー・システムでは、他のスクリプトやガジェットを統合できるようにします。
This is similar to mw.hook
except that it uses promises.
これには mw.pageTriage.actionQueue
モジュールを使って実行。
システムの作動に関する解説文書は、ソースコードのコメントを参照。
It is not currently used by any scripts or gadgets on enwiki, but it is used internally by PageTriage.
モジュールのactionQueue は、mw.hook ext.pageTriage.toolbar.ready
が発動すると利用可能になります。
後述のその他のデータに加えて、アクションキュー処理者にわたす固有のオブジェクトに含まれるデータは以下のとおり:
pageid
— レビューするページのID。title
— 名前空間を含むページ名。reviewer
— PageTriageを使用している利用者の利用者名。creator
— ページ作成者の利用者名。reviewed
— 当該のページは査読が必要だと現在、印が付けてあるか、もしくは今後、付く可能性があるかどうか。
利用できる操作
delete
— 査読者が当該のページに削除タグを付けると発動。処理者にわたされるデータに含まれるものは以下のとおり:tags
— 当該のページに追加されたすべてのテンプレートの特定の対象。検索キーはテンプレートの題名、検索値は即時削除コードなどメタデータの対象です。
mark
— 当該のページの査読状態が変化すると発動。他に含まれるものは以下のとおり:note
— 査読者が記事の初稿投稿者にあてたメッセージ文。白紙の場合もあります。
tags
— 当該のページにメンテナンス・タグがつくと発動。他に含まれるものは以下のとおり:tags
— 当該のページに追加した一連のテンプレートの題名一覧。note
— 査読者が記事の初稿投稿者にあてたメッセージ文。白紙の場合もあります。
例
操作のクエリを使うには、上記の操作により発動する関数を登録します。PageTriage は非同期のコードの入力を待って操作を終わらせてから、その他の操作すなわちページの再読み込みなどを実行します。たとえば査読済みとマークされたサンドボックスを編集する場合は次の構文を使います。
$( 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 );
} );
} );
} );
} );
Where are preferences stored?
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.
Installation on WMF wikis
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 tofalse
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.
関連項目
Notes
- ↑ Checked by
isPageUnreviewed()
- ↑ Checked by
isNewEnoughToNoIndex()
, if it doesn't exit early due to$wgPageTriageMaxNoIndexAge
beingnull
. - ↑ https://meta.wikimedia.org/w/index.php?title=Limits_to_configuration_changes&diff=prev&oldid=26121135
この拡張機能は 1 つ以上のウィキメディアのプロジェクトで使用されています。 これはおそらく、この拡張機能が安定していて高いトラフィックのウェブサイトでも十分に動作することを意味します。 この拡張機能がインストールされている場所を確認するには、ウィキメディアの設定ファイル CommonSettings.php および InitialiseSettings.php 内で、この拡張機能の名前を探してください。 特定のウィキにインストールされている拡張機能の完全な一覧は、そのウィキの Special:Version ページにあります。 |
この拡張機能は以下のウィキ ファーム/ウィキ ホスト/パッケージに含まれています: これは正式な一覧ではありません。 一部のウィキ ファーム/ウィキ ホスト/パッケージは、ここに記載されていなくてもこの拡張機能を含んでいる場合があります。 必ずご利用のウィキ ファーム、ウィキ ホスト、バンドルで確認してください。 |