Help:Extension:FlaggedRevs/zh

是MediaWiki軟體的擴展，它能讓維基監視對頁面做出的更改，並更謹慎地控制向維基讀者顯示的內容. 頁面可以由某些編輯者和審核員標記，以表示這些頁面已經被審核並確認符合維基所要求的標準. 該頁面的每個後續版本都可以被這些用戶標記以用來審核新的更改. 維基可以使用不同的標記，並只允許某些用戶能夠設定這些標記.

能夠標記修訂將使得維護維基的協調過程變得更加容易，因為能夠更清楚地知道哪些編輯是新的（而且可能是不合適的）或已被確認有建設性而接受. 同時也可以設定頁面讓讀者在查看頁面時只能看到被標記為某個等級的修訂版本；因此，無法將修訂標記為足夠高級別的用戶所做出的更改將保留為「草稿」的形式，直到修訂由另一個可以設定更高標記等級的用戶標記為止.

標記修訂非常靈活，有許多種的配置方式. 它可以足以讓人不易察覺，也可以用來緊密地控制維基上的活動.

术语
標記修訂引入了一些有關於用戶和編輯的新術語. 雖然每個術語都可以完全地自訂，以符合語言差異或基於維基定製，但某些術語通常是通用的.
 * 標誌和标记

標記修訂讓維基可以定義應用於頁面修訂的「標誌」，以表示該版本的品質或其他屬性. 標誌被分為分級式的「標準」，雖然有些維基只使用一個標準，但其他維基可能會使用多個標準來表示頁面的不同屬性. 例如，標記修訂的預設配置定義了三個標準，「準確度」、「深度」和「可讀性」，每個標準包含四個標誌.


 * Marker

Marker是抽象的標誌分組，用於辨識具有特定品質的條目. 有三種marker「已檢查」、「良好」和「優良」. 預設情況下，任何修訂版本在任何維基標準被標記為任何等級皆會符合「已檢查」marker. 「良好」marker的預設設定為準確性和深度1級，可讀性2級. 對於「優良」marker，修訂版本（預設情況下）在所有三個標準下都必須為最高級別. 大多數維基將定義他們自訂的標誌準則，因此這些設定將有所不同.


 * 稳定版和当前版

已啟用標記修訂的頁面有兩個「別名」：「當前版本」和「穩定版本」.

當前版本
 * 如你所想的，當前版本就是包括最新編輯在內的最新版本，無論這些編輯是否具有建設性.
 * 當前版本也稱為頁面草稿.

穩定版本
 * 穩定版本是已審核的頁面版本中最新的版本

你可以直接連結到頁面的當前版本或者是穩定版本，方法是分別在網址中附加 或.

查阅


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  to the URL in the address bar, setting   for the current version, and   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:


 *  - pages which have a stable version
 * ' (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.
 *  - pages that have no reviewed stable version.

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
 * 用户编辑的单独内容“页面”的数量
 * 用户使用的编辑次数
 * 用户是否有，以及它的大小（字节）
 * 用户是否曾被封禁
 * 用户被回退的编辑数（不包括自我回退）
 * 用户使用编辑摘要的次数（包括自动编辑摘要）

管理员可以无视自动授权机制，以授权不符合标准的用户，或者对滥用权限的用户除权.

管理员权限


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.