Jump to content

Wikipedia:Requests for checkuser/Procedures

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Daniel (talk | contribs) at 09:09, 11 December 2006 (cr). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

Tasks

Listing stage

This is the stage when caseshave been just created.

  • Ensure that the case is located correctly. This means that the case should be created at Wikipedia:Requests for checkuser/Case/(sockpuppeteer). Two common locations for miscreations are:-
  • Wikipedia:Requests for checkuser/(sockpuppeteer)
  • Wikipedia:Requests for checkuser/(sockpuppeteer) 2 etc. (generally occurs when a sockpuppeteer has had a case about them prior)
If either occurs, the options are either:-
  • If the proper target for a case already exists (ie. for a previous request), the best option is to copy-and-paste the request on the "bad" pagename to the "good" pagename, indicating that you are doing a copy-and-paste move in the edit summary. Once you have copied it across, tag the page for speedy deletion using {{db-reason}}.
  • If the "good" pagename doesn't exist, simply use the "Move" function to transfer it to the proper location, then tag the redirect left in the "bad" pagename with as above.
    Make sure you notify the applicant of the move, giving a link to the new pagename.
    • Ensure that the {{checkuser}} and {{checkip}} templates are used correctly in the top area of the request, and that the list of usernames is bulleted.
    • Ensure a code letter is provided, or that "none applicable, see below" is clearly stated by the applicant. If it isn't, post {{codeletter}} on the talk page of the applicant (see template page for usage details). Annoate the request for checkuser with {{moreinfo}}, stating that you have requested a code letter, to avoid confusion/doubling up between clerks.
    • Some code letters specifically ask for diffs and/or links to other material (eg. ArbCom decisions). See Wikipedia:Request for checkuser header for the list (which is transcluded onto the main RFCU page). If diffs are explicitly requested, and they are not given, add {{diffneeded}} on the talk page of the applicant (see template page for usage details). Annotate as per above.
    • Fix other general formatting problems, including how diffs are added (RFCU prefers [1] rather than http://www.example.com). Also used {{unsigned}} for requests which aren't signed, and remove any unneeded bolding etc.

    Intermission stage

    This is the stage when cases have been successfully listed (see above), but are waiting a checkuser to act on. Cases in this stage are located in Wikipedia/Requests for checkuser/Pending, which is transcluded to be the "Oustanding requests" section on the main RFCU page.

    • Watch for checkusers requesting more information. If they do, follow the procedures in the above section regarding {{codeletter}} and {{diffneeded}}. If, somehow, both a code letter and diffs are requested, user {{codeletterdiff}} (see details on template page).
    • Ensure that the requests don't become discussion/arguments between the accused and the applicant. Generally, let the accused respond with one comment. If then the applicant responds, remove both the initial response by the accused and the response by the applicant to the talk page, marking this by using "{{clerknote}} discussion moved to talk page" etc. under an appropriate header. Also, link to the talk page in the clerk note, to make naviagtion easier.
    • Watch if checkusers request any other clerk assistance, which is generally marked by the {{Clerk Request}} template. Follow their requests and instructions to the best of your ability, and if applicable discuss at the noticeboard for assistance.

    --TBC--