Extension:PageTriage/ja

PageTriage is an extension that aims to provide a feature-rich interface for triaging newly-created articles. It is intended to replace the new page patrol core function while adding additional functionality for reviewing, tagging, and improving new articles. It adds a Special:NewPagesFeed page, and a page curation toolbar to new pages for those with the 'patrol' permission. It was developed by the Wikimedia Foundation's Features Engineering team. For additional details see Page Curation.

An important note is that some of the configuration and code is specific to the English-language Wikipedia's workflows and as it's constructed now the extension is pretty much impossible to internationalize. (T50552 を参照してください. )

インストール
To actually see the extension working:


 * 被ログインユーザーとして新しいスタブページを追加.
 * Special:NewPagesFeedをご覧ください

The new page should appear, flagged as "", "", etc. ページキュレーションツールバーを見るには :


 * Login as a user with the 'sysop' permission, or add a group with the "patrol" permission, and add some user to that group, and login as that user.
 * Special:NewPagesFeedをご覧ください
 * Now you should see a "" button next to the new page.
 * Click this and you should see the page curation toolbar on the new page.

拡張機能の設定
拡張機能は「巡回」権限に基づいています. 巡回の設定については、を参照してください.

The following configuration variables can be set from your LocalSettings.php file:


 * $wgPageTriageEnableCurationToolbar: Set to false to disable the curation toolbar (default is true)
 * $wgPageTriageInfiniteScrolling: Whether or not to use infinite scrolling in the new pages feed (default is true)
 * $wgPageTriageNoIndexUnreviewedNewArticles: Set this to true if new, unreviewed articles should be set to noindex. In other words, if they should not be indexed by search engines until they are reviewed. (default is false)
 * $wgPageTriageMaxAge: The age (in days) at which PageTriage allows unreviewed articles to become indexed by search engines (if $wgPageTriageNoIndexUnreviewedNewArticles is true) (default is 90).
 * $wgPageTriageNamespaces: The namespaces that PageTriage is active in. (default is NS_MAIN and NS_USER).

See extension.json for the full list of config variables.

wiki上の設定
It is possible to configure much of PageTriage on-wiki via the pages  and , although the structure of the configuration may change in the future (to better accommodate wikis besides English Wikipedia).

You can get a general idea of how the configuration works by looking at the following:

Both of these files operate in much the same way.

There are two top-level jQuery variables that define the curation templates that are listed in the curation toolbar under the (add tags) and  (nominate for deletion) buttons. これら :

The 'Main' and 'User' refer to the namespace of the page being curated. Each sub-item in the three sets above defines the tabs shown at the left side of the toolbar, and has the following form:

Then the actual templates that are listed are defined under the above  variable. Each deletion template has the following form:

At the moment, some tags must be present:



例
So, if you don't want to use any of the built-in deletion templates (which can be imported from NewPagesFeed_Templates.xml, by the way) then you can replace them all with a single one by adding the following at the bottom of your  page:

クライアント側のフック
PageTriage provides a specialized action queue system to allow other scripts and gadgets to integrate with it. This is similar to  except that it uses promises. This is done using the  module. See the comments in the for documentation on how the system works.

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


 * — レビューするページのID.
 * — 名前空間を含むページ名.
 * — PageTriageを使用している利用者の利用者名.
 * — ページ作成者の利用者名.
 * — Whether or not the page is currently or will be marked as reviewed.

利用できる操作

 * — Fired when the reviewer tags a page for deletion. The data given to the handler also includes:
 * — 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.
 * — Fired when the review status of a page is changed. Also includes:
 * — The personal message the reviewer added for the creator of the page. This may be blank.
 * — Fired when maintenance tags are added to the page. Also includes:
 * — An array of the titles of all templates that were added to the page.
 * — The personal message the reviewer added for the creator of the page. This may be blank.

例
To use the action queue, register a function to be ran when an aforementioned action is fired. PageTriage will wait for any asynchronous code to complete before doing anything else, such as refreshing the page. For example, to edit Sandbox after a page has been marked as reviewed, you could use:

API
PageTriageはAPI5件のエンドポイントを追加し、次の機能に利用します.


 * - クエリで検知したページの一覧と最も活発な査読者の統計を取得
 * - クエリで検知したページの一覧と対応するまたデータを取得
 * - 当該のページに査読の有無をマーク
 * - Add clean-up tags or deletion templates to a page
 * - Internal API for fetching Backbone templates for use in the JS application

To check if a page has recently been marked as reviewed using an API query, you can use. The  field indicates whether the page is unreviewed (0), reviewed (1), patrolled (2), or autopatrolled (3). Log entries are kept, but pagetriagelist data is removed from the database after one year.

関連項目

 * commons:Category:PageTriage extension