User talk:The Earwig/afc-helper.js

The AFC Helper Script is a JavaScript designed to help when reviewing Articles for creation redirect submissions. Currently, it supports automatic page saving, automatic information detection, and other useful features that make reviewing redirects, especially when a large volume are submitted at once, a lot easier.

Instructions

Installation

• To install the script, simply add the following line to your skin's javascript file. The tool currently supports both Monobook (the default skin) and Vector (the beta skin). So, if you were using Monobook, you would add the following to Special:MyPage/monobook.js:

importScript('User:The_Earwig/afc-helper.js'); // AfC Redirect Helper script.

• After this, you must clear your browser's cache.

Usage

Screenshot of an older version of the script, written by Henrik.

If the installation was done properly, you should see a collection of colored links next to the section headers at WP:AFC/R (see right). Note that these colored links will only appear next to the requests that were not already created. The following is an list of the various links and their meanings:

Accept links

[accept] [change] [reason]

• The accept option is rather straightforward. It will automatically create the redirect based on the information specified by the requester.
• The change option can be used if you want to accept the redirect, but at a different title, or to a different target. This option will call up two prompts asking for you to enter the other information.
• The reason option can be used to accept a request normally (as if you were clicking on accept), but will prompt you for a comment. This will appear at the end of {{afc redirect}}, and can be useful to end discussions about the redirect.

Decline links

[exists] [blank] [notarget] [unlikely] [reason]

• The exists option can be used to decline a request if the page already exists.
• The blank option can be used to decline a request that does not provide enough information. You will usually use this if it does not specify a page name, because if no target is specified, the notarget option is preferred.
• The notarget option can be used if the request does not specify a target for the redirect.
• The unlikely option can be used if the redirect is too vague to be useful, or needs a source. For example, you could close a request for The Great One and Only to redirect to Amy Winehouse with this, because you would need a source.
• The reason option is a last resort, to be used if none of the other decline options fit. An example of this is if the submission is a test; it will prompt you for a reason to decline, and then it will automatically save the page.

Comment

[comment]

• The comment option does just that – leave a comment. It will bring up a prompt asking you to enter a comment about the request, then it will save it automatically.

Redirect template

If you choose to accept the request using any of the three accept links, the script will ask you for a redirect template to use. You can either select one of the provided templates, enter your own (you must include the brackets), or not use one at all.

Caveats

The following are some important caveats that you should know:

• The script supports redirects that use non-English, albeit Latin characters, such as é, á, or ó. However it does not support redirects that use foreign characters, such as Indic scripts. Please, do not even try, or you'll create something like this.
• Category submissions cannot be completed with this script, period. I'm not even sure if the script will display next to category submissions...
• Sometimes, people submit requests with multiple redirects that point to the same target. If you use the script on one of these, it will create the first redirect properly, but will not create the others. The other redirects will need to be processed manually.

Discussion

Very nice tool! Well done for creating it. We've been waiting for this for a long time. — Martin (MSGJ · talk) 16:43, 2 September 2009 (UTC)