Help:Extension:FlaggedRevs/ja

は、MediaWikiを使用したウィキにおいて、ページに施された変更を監視し、ウィキの閲覧者に表示する内容をより注意深く管理するための拡張機能です. 特定の「編集者」(editor)および「査読者」(reviewer)によって各ページは格付けされ、査読してそのウィキが求めている基準をどれほど満たしているかを示すことができます. ページのすべての各版は、それらの利用者によって新しい編集が査読され「格付け」されます. ウィキではそのような格付け段階の幅を設定したり、特定の利用者にのみ各段階の格付けを許可することもできます.

版を格付けできるようになると、ウィキの管理手順の調整をより簡単にできます. なぜなら、これによってどの編集が新しく（そして受け入れがたい編集かもしれない）、どの版を建設的なものとして承認するかを明確にできるからです. また、特定のレベル以上に格付けされた版のみを読者に表示できるように各ページを設定することもできます. ゆえに、編集した版を充分に高いレベルに格付けできない利用者による変更は、更に高いレベルに格付け可能な利用者に確認されるまで、「下書き」版として残ります.

FlaggedRevsはとても柔軟性があり、広範囲の設定が可能です. つまり、設定によっては、ほとんど目立たないぐらい慎重な設定をすることもできますし、ウィキの活動をとても厳しく管理するのに用いることもできます.

用語解説
FlaggedRevs introduces some new terminology relating to users and editing. While each term is fully customizable to allow for language differences or per-wiki customization, some terminology is generally universal.
 * フラグとフラグ付け

FlaggedRevs allows wikis to define "flags" that can be applied to revisions of a page to indicate the quality or other attributes of that version. Flags are grouped into hierarchical "scales"; while some wikis use only one scale, others may use multiple scales to indicate different attributes of a page. For instance, the default configuration of FlaggedRevs defines three scales, "Accuracy", "Depth" and "Readability", with each scale containing four flags.


 * マーカー

Markers are more abstract groupings of flags that identify articles as generally of a particular quality. There are three markers available, "checked", "quality" and "pristine". By default, any revision that has been flagged to any level on all of the flag scales that the wiki uses, qualifies for the "reviewed" marker. The default settings for the "quality" marker are level-1 for accuracy and depth, and level-2 for readability. For the "pristine" marker, a revision must (by default) be reviewed at the highest level on all three scales. Most wikis will define their own custom flag scales and so these settings will differ.


 * 安定バージョンと現在のバージョン

FlaggedRevs が有効になっているページでは 2 つの「別名」を使用できます: 「現在のバージョン」と「安定バージョン」です.

現在のバージョン
 * The current version is, as expected, the most recent version including the most recent edits, whether or not those edits were constructive.
 * The current version is also referred to as the draft of a page.

安定バージョン
 * 安定バージョンとは、あるページの査読済みの版のうち最新の版のことです.

現在のバージョンと安定バージョンにはいつでも直接リンクできます. URL の末尾に &stable=0 や &stable=1 をそれぞれ追加してください.

閲覧


FlaggedRevs allows a wiki to mark each revision of a page with a flag to indicate its quality or validity, and to control which revisions are shown by default on a page. Each page where FlaggedRevs is enabled is effectively given two alternative aliases; these are the "stable" version, which is the latest version that has been flagged to a sufficiently high level, and the "current" version, which is the most recent revision, flagged or not. Readers can access either version of the page by adding &stable= to the URL in the address bar, setting &stable=0 for the current version, and &stable=1 for the stable version. On each alias, there is an explanation and a link to the other version.

Wiki developers can control which alias is displayed to users and readers by default, and which flags allow a version to be considered 'stable'. Registered users can customize which alias they see by default in their User Preferences. Editors are also made aware of which alias they are viewing by the "" tab, which instead displays.

編集


FlaggedRevs does not affect a user's ability to edit a page; only the way the resulting version is handled by the wiki. Whenever a user edits a page, the contents of the edit window are always the wikimarkup for the current version, to prevent revision forks from accumulating. When there are unreviewed changes made since the last stable version, a diff is provided above the edit window to highlight any changes. This is important as the text being edited may not be the same as the page the user viewed before clicking the "" link (if the user was viewing the stable version); and it allows any changes to be immediately reviewed and modified or reverted if necessary.



If the user will not be able to see their changes in the default alias, an additional warning message is displayed,. Other than this the editing process is unchanged by FlaggedRevs; edits are made, previewed and saved in the normal manner.

Users who are capable of reviewing edits are encouraged to do so both during and after they edit. There is an option next to the "" and "" checkboxes to immediately review the version resulting from that edit, although this option is unchecked by default. Once a reviewer has made an edit, they are returned to the article as normal, but are presented with a diff of all changes, including theirs, since the last stable version, with the option to immediately review the changes.

査読


Reviewing versions is the primary new activity introduced by FlaggedRevs. With the exception of the "review this edit" checkbox on the edit screen, all methods of reviewing versions use the same interface. At the bottom of a draft page, a series of radio buttons or checkboxes allows the reviewer to select which flags to apply to the revision, and there is the option to provide a comment that will appear in the review log.

Users can review any version, including versions that have already been reviewed by others. In this instance the newest review overrides previous reviews: if the new reviewer flags the version at a higher level than the previous reviewer, it is considered a normal "approve" review, while 'confirming' another reviewer's assessment by flagging the version to the same level is recorded as a "re-review". By flagging a previously-reviewed version as 'unassessed', reviewers can effectively 'unflag' a revision; these "deprecations" can be seen in a separate stream in.

未査読版の検索
FlaggedRevs is designed to encourage eligible editors to review versions quickly and efficiently, and so links are provided in most common locations to review changes by editors who cannot flag the versions themselves. Edits that have resulted in an unreviewed version are marked with an exclamation mark ! in the watchlist and the RecentChanges feed, with a link to review the changes. When viewing a page that has unreviewed edits, a banner is also added to indicate the number of edits since the last stable version, the age of the stable version, and a link to review the changes.



The FlaggedRevs extension also creates a number of new special pages that can be used to find and manage reviewed and unreviewed pages:


 *  - 安定バージョンがあるページ


 * ' (called ' on some wikis) - pages that have pending changes from the stable version.


 *  - pages that have pending changes from the stable version that also have recent changes tags.


 *  - 査読済みの安定バージョンがないページ

The latter two pages also include the number of users who have each page on their watchlist, so that 'backwater' articles can be identified and monitored; because of this slightly sensitive information, access to pages is usually restricted to users who have the ability to review versions. is sorted by the time since the last revision was flagged, oldest first.

総合的監視
In addition to these pages, several other reports give general oversight over the reviewing process. is a list of pages where the default display settings have been overridden by administrators to either always show readers the "stable" alias by default or always show readers the "current" alias by default, depending on the wiki's FlaggedRevs settings.

 provides an aggregated log of all reviews made on the wiki. These events are also added in a new 'stream' to the main log at Special:Log, at Special:Log/review. However, the report at can be filtered by marker type, namespace, whether the action was to review, unreview or re-review the revision, and whether the review was automatic or manual.

Finally,  provides a summary of how thoroughly each content namespace has been reviewed, and other useful data about the reviewing process.

自動昇格
Wikis can configure FlaggedRevs to automatically grant editors the ability to review versions when they meet certain thresholds of activity. Wikis need to judge carefully how best to configure the autopromotion feature (if at all) to be as confident as possible that the user is a constructive editor, without making them wait too long to be promoted. Thresholds can be set on a number of attributes, including:


 * 利用者のアカウント登録からの経過日数


 * Their total editcount
 * It can be required that these edits have been made consistently over a time period, eg 20 edits spread over a period of 20 days would qualify, but 20 edits all at once would not
 * Edits from the last X days can be excluded from the count (giving admins time to look at them)
 * A certain number of these edits can also be required to be in "content" namespaces


 * 利用者が編集したコンテンツ「ページ」数


 * The number of edits the user has made that include an edit summary
 * Whether the user has a user page, and how substantial it is (bytecount)


 * 利用者がブロックされたことがあるかどうか


 * 利用者による編集が取り消された回数 (自身による取り消しは除外)


 * 利用者が編集の要約を記入した回数 (自動的に記入された要約を含む)

The autopromotion mechanism can be overridden by administrators, either to promote a user who does not meet the criteria, or to demote a user who has abused the reviewing ability.

管理者の能力


While a wiki's developers can define default settings for which alias is presented to each user group by default, these settings can be customized by individual users and for individual pages. Each registered user can set in their preferences whether they wish to see the "current" or "stable" alias by default when viewing an article.

Some group on the wiki, usually administrators, have the ability to use the special page  to override the default display for unregistered users. Administrators can set a page to display the stable version by default, and can also control how the stable version is selected, choosing which marker is preferred.

Administrators also have the ability to grant users the ability to review edits, and to revoke that permission in case of abuse, by using the Special:UserRights interface. This explicit assignment overrides any permissions automatically given to the user by the autopromote feature – if an administrator has explicitly revoked a user's reviewing permissions, the autopromote feature will not grant them back, and vice versa.