 |
 | This page in a nutshell: RevisionDelete is aMediaWiki function used toredact grossly improper posts and log entries. It is available toadministrators in accordance with thecriteria for use. It can also be used in "Suppression" mode byoversighters to remove certain defamatory content and privacy breaches from public and administrator view. |
| Deletion policies |
|---|
RevisionDelete (also known asRevDel orRevDelete) is a feature that allowsadministrators toremove individual entries in apage history orlog from public view. It is used for "selective deletion", largely replacing the prior method (delete and partial undelete) which should no longer be used except for history merges and occasional other technical cases where it is needed. Revision deletion should only be used in accordance with thecriteria for redaction.
RevisionDelete can hide the text of a revision, the username that made the edit or action, or the edit summary or log summary. On the English Wikipedia, criteria exist to govern the use of RevisionDelete, which are outlinedbelow. Use of RevisionDelete byoversighters in "Suppression" mode is covered separately by theOversight or Suppression policy.
Any administrator may handle RevisionDelete requests made by users, butCategory:Wikipedia administrators willing to handle RevisionDelete requests lists administrators who have declared a particular willingness to handle such requests. Users who have concerns about any particular use of RevisionDelete may ask any administrator to review the matter, but again administrators listed in that category may be particularly well placed to do so. When contacting editors about sensitive material, email is preferred to talk page messages, to avoid exposing information to more readers.
RevisionDelete allows selectiveredaction of posts and log entries by administrators, as well aspeer review by any administrator of the correct use of the tool. Entries still appear in redacted form on the public wiki, and any user may request that an administrator review a RevisionDelete action, to determine whether its removal was reasonable. RevisionDelete logged actionscan be found here.
As a deletion tool, RevisionDelete is capable of removing material from the wider community's view. Because of this, the tool should only be used within strict guidelines.
In time-sensitive situations where material may be subject tothe oversight policy (such as privacy breaches and defamation), an administrator may redact first, then immediately bring the matter to the attention of oversighters. (Seebelow.)
RevisionDelete was introduced for administrators in 2010. The community's endorsement of the tool included a very strong consensus that there was a potential for its abuse, that such abuse needs to be prevented by the community and appropriate mitigation of the risk of abuse written into policy. Especially, RevisionDelete is not to be used to remove "ordinary" offensive comments and incivility, or unwise choices of wording between users, nor to redact block log entries; material must be grossly offensive, with little likelihood of significant dissent about its removal. Otherwise it should not be removed. Administrators should consult as usual if uncertain that a revision would be appropriate to redact.
A certain low degree of inappropriate or disruptive posting is normal within a large community. In general, only material that meets at least one of the criteria below should be deleted. Users should consider whether simplyreverting or ignoring would be sufficient in the circumstances. If deletion is needed, only redact what is necessary (i.e. leave non-harmful fields visible), and give a clear reason for the removal.
The community's decision[when?] was that RevisionDeleteshould not be used without prior clear consensus for "ordinary" incivility, attacks, or claims of editorial misconduct. The wider community may need to fully review these at the time and in future, even if offensive.
Log redaction (outside of the limited scope ofRD#2 for the creation, move, and delete logs) is intended solely for grossly improper content, and is not permitted for ordinary matters; the community needs to be able to review users' block logs and other logswhether or not proper. Use of the RevisionDelete tool to redact block logs (whether the block log entry is justified or not) or to hide unfavorable actions, posts or criticisms, in a manner not covered by these criteria or without the required consensus or ArbCom agreement,will usually be treated as abuse of the tool.
Personal information includes almost any material that is (or looks like it might be) actual claims, facts, hints, or allusions to non-public, personal, or private information (seeWP:Oversight andWP:OUTING).
It does not matter whether the privacy-breaching material was posted by the user themselves or by a third party, whether in good or bad faith, recently or in the past, whether accurate, whether the target is identifiable to the administrator, nor whether it is a statement, pointed speculation, or implied.
RevisionDelete can be used to hide anyprivacy-breaching or defamatory posts while waiting forOversight. Since Oversight requests are not immediate, an administrator may provisionally delete the information from public view to minimize harm, then promptlycontact an oversighter.
Even if the material is ultimately found not to be suppressible,administrators are allowed to err on the side of caution, even in cases with an apparentconflict of interest, provided it is in good faith and they quickly seek oversighter review. If the oversighter decides suppression was not appropriate, the material will be restored or RevisionDeleted instead.
Administrators should be aware that delete logs are public and scrutinized. Deletion may lead to extra attention at times. Only administrators can see the material when it is RevisionDeleted (and before oversight), but even so it may sometimes be more discreet to contact oversighters directly, and not use RevDelete first. A lot depends on the material itself.If RevisionDelete is used, avoid obvious suggestive terms in the reason (e.g. don't use "RD4", "oversight", "private material", "hiding IP of logged out user", etc.).
When hiding personally identifiable information related to an individual who can be contacted by email, it may be considered good manners to notify them that the information was deleted and hidden from public view. Providing such notice is at the administrator's discretion.
RevisionDelete is mainly intended for simple use and fairly recent material. Text that exists in numerous revisions (e.g. on busy pages) or which has been the subject of many others' comments may not be practical to redact. Redaction of such material should take into account how practical and effective redaction will be, how disruptive it would be (e.g. to others' valid posts), and whether redaction willitself draw attention to the issue. No hard line exists; judgment is required.
Administrators in this situation may wish to initially edit the page to revert or remove the grossly improper material, and then consult.
To request revision-deletion for copyright violations (RD1), useTemplate:Copyvio-revdel.
To avoid theStreisand effect, there is no dedicated on-wiki forum for requesting revision deletion under other circumstances. You can send a message to any administrator inCategory:Wikipedia administrators willing to handle RevisionDelete requests either at their talk page or byemail, especially if privacy is a concern.
You can also request revision deletion onIRC using#wikipedia-en-revdelconnect. Only use this for requests that areurgent and should not be handled publicly (RD2, RD3, and RD4). In this channel, only administrators will be able to see your request.
Keep in mind thatif the revision you're reporting could be subject to oversight, follow the procedures atWP:Requests for oversight or emailoversight-en-wp
wikipedia.org.
To contest or reverse revision-deletions, discuss with the deleting admin. For image revisions deleted underF5, you may instead request undeletion atWikipedia:Requests for undeletion.
Actions performed using this tool remain visible in the public logs. They are subject to review by other administrators (who can see redacted material), and to reversal upon clear, wider consensus. Such a review should take place at theAdministrators' noticeboard. As with other administrative tools, good judgment and appropriate use are expected;improper use can lead to sanctions or desysopping.
 |
On the English Wikipedia, the revision deletion feature is available in administrator mode toadministrators and in administrator and suppression mode toOversighters (all of whom are currently also administrators).
Page histories and logs have a button for administrators and oversighters that allows multiple entries to be redacted by selecting them from the list with checkboxes. On page histories, the button isChange visibility of selected revisions; on logs it isChange visibility of selected log entries.
When a revision or log entry is hidden from view in its entirety, it is displayed as shown to the right, with the elements hidden from view stricken and greyed out. The struck-out elements cannot be viewed by any usergroup which does not have thedeleterevision right. A user who cannot access the relevant revisions and who tries to compare the revision with other revisions or access its&oldid= page will receive an error stating that the revision has been removed from the public archives. Similarly, looking up log entries or contributions by username will not show log entries where the username has been redacted.
The button can usually be clicked by an administrator to view selected redacted entries. It will appear in black if suppression has been applied, in which case both the redacted material and its deletion settings cannot be accessed by administrators or users who lack access to theoversight tool.
Revision deletion actions are retained even when the revision or page is deleted in the traditional manner. If a page is later undeleted, data that was deleted with RevisionDelete will still remain deleted.
When redacting the log entry of a page move, note that it will also have been recorded as an edit summary in that page's history; it will need to be redacted as well.
While a RevisionDelete is generally effective at removing sensitive information from the public eye, it does not impact third parties. Third parties may:
.png)
To hide or unhide a revision or a log entry, select the relevant revision[s] or log entry/entries that you wish to show or hide with the checkbox[es] to its/their left, and clickChange visibility of selected revisions orChange visibility of selected log entries as appropriate. Depending on your permissions, there may be either three or four options to choose from:
In the visibility restrictions option area, tick the checkboxes next to each restriction you wish to apply to the selection, and provide a reason for the setting from theReason dropdown menu. Optionally, enter further information into the text field. Once this information has been filled in, clickApply to selected revision to apply the change. If this has been done correctly, a success message should be displayed.
Unhiding a revision or log entry follows the same procedure. Untick the checkboxes that you wish to unset in the visibility restriction options section, and provide a reason for the change.
Hiding of a username or IP shouldonly be used where that username or IP has a reasonin and of itself to be hidden, such as accidentally editing logged out or an attack username. Hiding a username will remove the contribution completely from the user's contributions list (except from administrators, who will see a warning indicating it is invisible to users), rather than a crossed out entry for deleted edits without hidden username. This will cause issues with users trying to review actions taken on the user, as well as potential copyright violation risks.
Use of RevisionDelete produces an entry in the publicdeletion log, or the privatesuppression log if used by an oversighter and"Suppress data from administrators as well as others" is checked. Log entries created in the public deletion log look like those displayed to the right, for page revision and log entries visibilities respectively. The options (diff |change visibility) provide an easy link to view or redact the underlying page revision to which the log entry refers.
The older method ofselective undeletion (i.e. delete the entire page then selectively restore revisions) as a method of deleting revisions is deprecated in favor of this system. While selective undeletion does still have a few valid uses (such as complexhistory merges), it should not be used to remove revisions from the page history, due to its relative lack of transparency and poor efficiency.