Wikipedia:WikiProject Articles for creation/Reviewing instructions

Not everyone can review potentially new articles like they can edit Wikipedia. For criteria to become a reviewer, see ../Participants/.

How to use the "articles for creation helper script"
The "Articles for creation helper script" is a script that assists in reviewing article submissions. The script can accept and decline article submissions, mark submissions as under review, tag submissions for deletion, and add comments to submissions without changing their status. The script will also automatically notify the author of the outcome and can be used to create the respective talk page of an accepted submission.

It is very highly recommended that reviewers use the script when reviewing, as it ensures that editors are notified and templates are removed from articles once they have been created. Though it is technically possible to do the process manually, it needs to be done exactly in every detail to avoid confusion to the contributors and other reviewers.

Editors must read the script documentation and the reviewing instructions below before starting to review submissions. The documentation and the discussion pages for the script are located at WikiProject Articles for creation/Helper script.

To install the script go to your user preferences and check the checkbox at:

How to find submissions for review
All drafts are displayed in the dynamic list at Special:NewPagesFeed. Select 'Articles for Creation' and then from 'Set filters' choose from the multiple options which kind of drafts you would like to review. Submissions sorted by their predicted category can be found at AfC sorting. This page is updated every day by a bot.

You can also find a list at Category:Pending AfC submissions. Or you can click on the button at AFC button, which will take you to a random article waiting for your keen eye.

How to place a submission "under review"
If you are in the process of reviewing a submission, please mark the submission "under review". This changes the visible submission template, alerting other reviewers that someone is reviewing the submission, which reduces occurrence of edit conflicts. When using the script, simply select Mark as reviewing from the Review tab.

Core purpose
The purpose of reviewing is to identify which submissions will be deleted and which won't. Articles that will probably survive a listing at Articles for deletion should be accepted. Articles that will probably not survive should be declined. Issues that do not affect the likelihood of success at AFD (e.g., halo effects like formatting) should not be considered.

General standards and invalid reasons for declining a submission

 * Avoid the following errors:
 * 1) Avoid declining an article because it correctly uses general references to support some or all of the material. The content and sourcing policies require inline citations for only four specific types of material, most commonly direct quotations and contentious material about living persons.
 * 2) Avoid declining an article that meets the criteria for requiring inline citations because you wrongly assumed that the absence of little blue numbers meant that no inline citations existed. The use of tags, although popular, is not required. Editors may choose any form of inline citation, not just the most popular one. Many new editors choose a different style, and their choice is protected by Wikipedia's citation guidelines.
 * 3) Avoid declining an article because the references contain bare URLs or other reference formatting problems. Instead, run reFill (and check its output!) or tag the article with  or.
 * 4) Avoid declining an article because it contains formatting issues, such as the absence of wikilinks, or because it has no sections. Instead, fix it yourself, or accept the article and tag it with maintenance templates to alert other editors to issue(s).
 * 5) Avoid declining an article because you personally don't like the citation style or formatting.
 * 6) Avoid declining an article because the reliable sources are not free, online or in English. Books, magazines, and other print-only sources are perfectly acceptable, and may as well be in another language.

Step 1: Quick-fail criteria
Before reading a submission in detail, check whether it meets any of the quick-fail criteria. If so, it should be declined immediately and in some cases it may be necessary to nominate the submission for speedy deletion.

Step 2: Notability and verifiability
The principle of notability applies to the subject of the article. The principle of verifiability applies to the content of the article. The most basic standard for inclusion in Wikipedia is notability. It is important for reviewers to determine a subject's likely notability right away, to avoid new editors having submissions declined for other reasons, only to find out later that the subject of their submission cannot be accepted because it does not meet the notability guidelines. Many problems found in submissions can be fixed through good editing, but no amount of editing can make an inherently non-notable subject notable!

If what is written in the submission meets the notability guidelines, such as a claim to a major award, but the submission lacks references to evidence this, then the underlying issue is inadequate verification and the submission should be declined for that reason. Notability is a higher standard than lacking an indication of importance or significance, which are grounds for speedy deletion in the article mainspace.

Articles require  in  that are  of the subject.

{{divbox|greenv||

Significant coverage
References about the subject — at least one lengthy paragraph, preferably more. Not passing mentions, not directory listings, not just any old thing that happens to have the name in it. Several of them. The subject of the article must be notable. }}

{{divbox|greenv||

Reliable sources
Published sources that have a reputation for fact-checking and accuracy. A major newspaper, a factual, widely-published book, high-quality generally trusted mainstream publications. Not blogs, MySpace, Facebook, LinkedIn, YouTube, fansites, Twitter, wikis, or other sites with user-generated content. The content of the article must be verifiable. }}

{{divbox|greenv||

Independent
Nothing written by the subject, paid for by the subject, or affiliated with the subject. Not their website, and not a press release. The sources must be independent. }}

Subject-specific notability guidelines
Wikipedia has some subject-specific notability guidelines. Read through the submission and consider if one or more of the guidelines below applies. If it does, and the submission does not meet the relevant guideline or the General Notability Guideline you can decline the submission for that reason. The following table shows the notability guidelines for specific subjects. If the subject of the submission you are reviewing is not listed in the table below, only apply the general notability guideline.

Verifiability
If what is written in the submission meets the notability guidelines, but the submission lacks references to evidence this, then the underlying issue is inadequate verification and the submission should be declined for that reason.

Step 3: Suitability
Now you should read the submission in detail and decide whether it is suitable for Wikipedia. To be suitable, the article must be about a notable subject and be written in an encyclopedic style from a neutral point of view. The most common reasons that a submission is not suitable are provided here.

Step 4: Accepting a submission
At this point, if you have not found any reason to decline the creation of the article, it should be accepted. Follow the steps here:


 * 1) Click the Accept button.
 * 2) * Select an appropriate name
 * 3) * Give the article an assessment on the quality scale
 * 4) * Consider adding categories, and/or appropriate cleanup templates or stub-tags by entering the code in the relevant boxes.
 * 5) * Add any WikiProject banners that would apply to the article by inserting the template code into the relevant box.
 * 6) * If accepting an article about a person, please ensure you tick the biography checkbox, and select the relevant option from the living person drop-down menu. This ensures such articles are placed in Category:Biography articles of living people.
 * 7) Click Accept and publish to mainspace. The script will move the article for you, clean it up, create its talk page, grade it, and notify the submission creator.
 * 8) If you have AWB authorization, you can use AWB to tidy up the new article and carry out typo and general fixes. If you don't have AWB, you can use Auto-Ed to clean up the formatting of pages or do it manually.
 * 9) If the submission is reasonably well-sourced, has a minimum of 1,500 characters of prose, and is generally interesting, consider nominating the article to appear on the main page as part of Did you know? (see instructions).

If you cannot publish the draft
If a submission, which should be accepted, cannot be moved, you may get one of the following errors:
 * If a proposed article title is triggering the page title blacklist, you will see an error message that reads: Error info:hookaborted : The modification you tried to make was aborted by an extension hook. If you try and move the page manually you will see: MediaWiki:Titleblacklist-forbidden-move. Please request help with the move from a pagemover at Requested moves/Technical requests.
 * If the destination page has been creation protected because of repeated recreation, it will be necessary to make a request for unprotection at Requests for unprotection.
 * If the page title you have selected already exists as a redirect in mainspace, tag the redirect with and – if desired – mark the draft under review. After it has been deleted by an administrator, you can then accept the submission. If deletion is declined because the draft is not ready for main space, please notify reviewers on the Articles for Creation talk page.
 * A title with a slash would work in the article namespace, but in the draft namespace it generates a subpage. For example, Draft:AC/DC would be understood by the system as the DC subpage of Draft:AC . To properly promote such pages, move the draft to a name without slash, promote the draft, and then move it back to the name with a slash.

Step 5: Other tasks and checks
Please read Wikipedia's username policy and if you recognize that a user has a prohibited username, tag the user's talk page with. This tag is also used by Twinkle under: warn → Single issue warnings →. If the username is a blatant violation of the username policy, consider reporting the username to usernames for administrator attention.

Draft submissions
Draft submissions are designed to replace the userspace draft option from the article wizard. Submissions are reviewed only after a review is requested by the submitter. After a review is requested, it is reviewed like any other pending submission. If the submission meets the guidelines, it is accepted normally. If it needs improvement, it is declined. All draft submissions not pending review are located in Category:Draft AfC submissions.

Draft submissions are not meant to replace the current Articles for Creation system. Rather, it is meant to make it more effective by offering new editors a better way to create draft articles, without struggling with requested moves once they feel it is ready to be moved to mainspace.

A pending template can be turned into a draft template by replacing the second parameter with the letter "t". NOTE: Please only do this with the creator's permission.

Declining draft submissions
When a draft is submitted for review, there are two AFC submission templates. There is a draft submission template, and a normal pending review template. The draft submission template is merely used to keep track of unsubmitted drafts. Once it has been submitted for review, this template should be removed. ArticlesForCreationBot is tasked with removing the draft submission template, so only the pending review template should remain. If a draft submission meets the quick fail criteria, then it is declined like any other submission.

Other types of submissions
Articles for creation can also be used to submit templates, disambiguation pages and articles for deletion discussions. In these cases, there are no notability issues. You just need to decide whether the page is useful and appropriate to Wikipedia. For these submissions it will most likely be necessary to include a custom decline reason, using the AfC Helper Script. Refer to official guidelines for guidance on when to disambiguation pages or templates. This can be found at Disambiguation or Template namespace. Articles for deletion discussions may be created on behalf of anonymous users, who cannot start them. Aside from general reasons for declining a submission (empty, gibberish, spam, copyright violations, etc.), AFD submissions should generally be accepted. (See Deletion policy and instructions for opening an AFD for more information.)

AFC also processes redirect, category and file submissions. Reviewing instructions can be found at Articles for creation/Redirects/Reviewing instructions, Articles for creation/Categories/Reviewing instructions and Files for upload/Reviewer instructions.

Cleaning submissions
The AFC Helper Script is able to clean up the formatting of submissions, including removing userspace/sandbox templates and unnecessary draft templates. From the Review menu, select Other options and then Clean submission. Once the script has finished, reload the page to see a much cleaner submission.

Adding questions or comments
If you want to ask the submitter a question, or just make a comment on a submission, click the Comment option from the Review tab. Some premade templates of common responses can be found in Category:AfC comment templates.

Rejecting submissions
Drafts on topics entirely unsuitable for Wikipedia should be rejected. Rejection is appropriate when you genuinely believe the page would be uncontroversially deleted if it were an article (i.e., the page would be an overwhelming "delete" at AFD, or clearly meet a CSD article criterion). If a draft meets one of the  general CSD criteria, an appropriate CSD tag should also be added.

Submissions in other namespace
Pending submissions that have been created in userspace (including sandboxes) should be moved to the preferred AfC namespace. You will find a pre-loaded link at the bottom of the pending review template to complete this. You may need to select an alternative appropriate name for the submission, based on its content. Note that the AfC Helper Script will not work in non-AfC namespaces. Submissions in other namespaces that contain the template can be moved to AfC space regardless of their status, if it is beneficial to do so.

Duplicate submissions
Sometimes you will notice two or more different submissions on the same subject created by the same editor. You may notice while trying to move a pending submission from userspace, that the preferred AfC title already exists. This is usually the result of new editors who are unfamiliar with the MediaWiki interface and create new pages rather than editing existing ones. In such cases, you should consider requesting a technical page move or a history merge. Do not create yet another duplicate page, even with a numerical distinguisher. This risks splitting page histories or creating parallel histories and confusing new editors. If you find two pending submissions on the same subject, by the same author, you can decline one of them as a duplicate. If you are unsure about how to deal with duplicates, ask an experienced member of the project or an administrator for assistance.

Reviewing manually
In the event of an AfC Helper Script failure, you can review submissions manually by reading this archived version of the instructions and following the steps for modifying. If you do this, be careful to follow every step exactly.

Log
If you want to check a reviewer's list of AFC accepts, declines, comments, and edits, you can use the AFC History Tool.

Marking your own AFC accepts as reviewed
If you have the new page patrol right or the autopatrolled right, and you accept a draft, you are permitted to mark it as reviewed, even though you also did the AFC accept. However if the draft is borderline in some way such as notability, it is a good practice to leave it unreviewed, or mark it as unreviewed, to get an additional set of eyes on it.