วิกิพีเดีย:โครงการวิกิว่าที่บทความ/ขั้นตอนการตรวจทาน

"WP:AFCR" เปลี่ยนทางมาที่นี่ คุณอาจต้องการไปที่วิกิพีเดีย:ว่าที่บทความ/หน้าเปลี่ยนทางและหมวดหมู่

โครงการวิกิว่าที่บทความ

หน้าโครงการ พูดคุย ฉบับร่างที่ถูกส่ง ผู้ตรวจทาน ขั้นตอนการตรวจทาน สคริปต์

---

ดูว่าใครสามารถตรวจทานฉบับร่างได้

ไม่ใช่ทุกคนที่จะสามารถตรวจทานฉบับร่างได้อย่างแก้ไขวิกิพีเดีย สำหรับเงื่อนไขในการเป็นผู้ตรวจทาน ดูที่ผู้มีส่วนร่วม

วิธีการใช้ "สคริปต์ช่วยเหลือการตรวจทานฉบับร่างว่าที่บทความ"

"สคริปต์ช่วยเหลือการตรวจทานฉบับร่างว่าที่บทความ" คือสคริปต์ที่ช่วยให้ตรวจฉบับร่างได้ง่ายขึ้น คุณสามารถใช้สคริปต์ในการยอมรับหรือปัดตกฉบับร่าง ทำเครื่องหมายว่ากำลังตรวจ แจ้งลบ หรือเพิ่มความเห็นโดยไม่ต้องแก้ไขสถานะของมัน สคริปต์จะแจ้งเจ้าของฉบับร่างและสร้างหน้าพูดคุยที่เกี่ยวข้องได้เมื่อฉบับร่างถูกยอมรับเป็นบทความแล้ว

แนะนำเป็นอย่างยิ่งว่าผู้ตรวจทานควรใช้สคริปต์เมื่อทำการตรวจทานฉบับร่าง เพื่อให้มั่นใจว่าผู้สร้างหน้าจะได้รับแจ้งเตือนและแม่แบบถูกลบออกแล้วอย่างแน่นอนเมื่อสร้างเป็นบทความจริง แต่อย่างไรก็ตาม ทางเทคนิคแล้วยังเป็นไปได้ที่จะทำกระบวนการนี้ด้วยมือ แต่ก็ต้องทำโดยตรงตามทุก ๆ รายละเอียดเพื่อมิให้สับสนแก่ผู้มีส่วนร่วมหรือผู้ตรวจทานอื่น

ผู้แก้ไขควรอ่านคู่มือการใช้งานสคริปต์ด้านล่างก่อนเริ่มต้นการตรวจทานฉบับร่าง คู่มือการใช้งานและหน้าพูดคุยของสคริปต์อยู่ที่วิกิพีเดีย:โครงการวิกิว่าที่บทความ/สคริปต์ช่วยเหลือ

ในการติดตั้งสคริปต์ โปรดเพิ่มโค้ดดังต่อไปนี้ไปที่หน้า /common.js หรือ /vector.js ของคุณ:

mw.loader.load('//th.wikipedia.org/w/index.php?title=User:Patsagorn_Y./afch.js&ctype=text/javascript&action=raw', 'text/javascript');

วิธีการหาฉบับร่างเพื่อตรวจ

คุณสามารถดูรายการได้ที่หมวดหมู่:ฉบับร่างรอตรวจ

วิธีการทำเครื่องหมายฉบับร่างว่า "กำลังตรวจ"

หากคุณอยู่ในกระบวนการตรวจฉบับร่าง กรุณาทำเครื่องหมายฉบับร่างว่า "กำลังตรวจ" โดยจะแสดงให้ผู้ตรวจทานอื่นทราบว่ากำลังตรวจฉบับร่าง ซึ่งจะช่วยลดการแก้ไขชนกัน เมื่อใช้สคริปต์ช่วยเหลือ เลือก ทำเครื่องหมายว่ากำลังตรวจจากแท็บ ตรวจ

วัตถุประสงค์

The purpose of reviewing is to identify which submissions will be deleted and which won't. Articles that will probably survive a listing at Wikipedia: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.

วัตถุประสงค์หลักของกระบวนการตรวจทานฉบับร่างคือการลดจำนวนอัตราการลบฉบับร่าง โดยการติชมเนื้อหาก่อนเพื่อให้ปรับปรุงบทความในทางที่สร้างสรรค์ได้จนเป็นบทความ เกณฑ์ในการตัดสินใจว่าจะปัดตกบทความใดหรือไม่นั้นคือให้สมมติว่าแจ้งลบบทความ บทความจะถูกพิจารณาลบหรือไม่ หากใช่ ควรปฏิเสธฉบับร่าง แต่ถ้าไม่ ผู้ตรวจทานอาจให้ผ่านเพื่อเป็นบทความ

หากฉบับร่างถูกแจ้งลบ จะได้รับการตัดสินว่าไม่ควรลบหรือไม่?

ใช่ จะไม่ถูกลบ	ให้ผ่านฉบับร่างได้ (คุณอาจจะใส่ป้ายปัญหาอื่น ๆ ที่ไม่เกี่ยวกับการลบได้)
ไม่ จะถูกลบอย่างแน่นอน	ปฏิเสธหรือปัดตกฉบับร่างนั้น และอย่าลืมอธิบายเหตุผลว่าทำไมจึงควรถูกลบ
ไม่แน่ใจ	ถามคำถามที่หน้าพูดคุย

มาตรฐานโดยทั่วไปและเหตุผลที่ไม่เหมาะสมในการปัดตกฉบับร่าง

พยายามงดข้อผิดพลาดเหล่านี้

1. งดปัดตกฉบับร่างเพราะมีการใช้การอ้างอิงทั่วไปในการสนับสนุนแหล่งที่มาบางส่วนหรือทั้งหมด นโยบายเนื้อหาและแหล่งอ้างอิงจำเป็นต้องใช้การอ้างอิงในบรรทัดเฉพาะสำหรับเนื้อหาสี่ประเภทเท่านั้น ซื้อมักเป็นอัญพจน์และเนื้อหาใด ๆ (ไม่ว่าในเชิงลบ เชิงบวก หรือเป็นกลาง) เกี่ยวกับบุคคลที่ยังมีชีวิต
2. หลีกเลี่ยงการปฏิเสธบทความที่ตรงตามเกณฑ์ที่กำหนดสำหรับการอ้างอิงในบรรทัดเนื่องจากคุณเข้าใจผิดว่าการไม่มีตัวเลขสีน้ำเงินเล็ก ๆ น้อย ๆ หมายความว่าไม่มีการอ้างอิงในบรรทัดอยู่ การใช้แท็ก <ref> แม้ว่าจะเป็นที่นิยม แต่ก็ไม่จำเป็นต้องใช้ ผู้แก้ไขอาจเลือกรูปแบบใดก็ได้ของการอ้างอิงในบรรทัด, ไม่ใช่แค่อันที่ได้รับความนิยมมากที่สุดเท่านั้น ผู้แก้ไขใหม่จำนวนมากเลือกรูปแบบที่แตกต่างออกไป และตัวเลือกของพวกเขาได้รับการคุ้มครองอย่างเป็นทางการด้วยการยินยอมให้อ้างอิงของวิกิพีเดีย
3. Avoid declining an article because the references contain bare URLs or other reference formatting problems. Instead, run reFill or tag the article with {{cleanup-link rot|date=ธันวาคม 2024}} or {{citation style|date=ธันวาคม 2024}}.
4. Avoid declining an article because it contains formatting issues, such as no wikilinks to other articles, 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 the one or two issues that you believe need to be resolved first.
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, on-line or in English. Books, magazines, and other print-only sources are perfectly acceptable, and may be in another language.

ขั้นตอนการตรวจทาน

ขั้นตอนที่ 1: ตรวจหาความผิดพลาดเบื้องต้น

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.

Expand this box to learn about the quick fail criteria

Quick-fail criteria Quick-fail reason Action Copyright violation Please check all submissions for copying from existing sources – copyright infringement is a pervasive problem and it is not only important that we don't host such material, but it often leads to significant additional work when not caught early. One way to search for them is to copy and paste into a search engine such as Google (between quotation marks) a limited but unique portion of text of the draft, and try a few such snippets from each paragraph. See also this tool. Also check the sources provided, and, if relevant, and even if not given as a reference or link, check the person's or organization's web site (it is often useful once located to look for an "about", "history" or other narrative section). If the submission contains material that has been copied from elsewhere and the source is not released under a suitable free license or into the public domain, immediately decline the submission as a copyright violation. In no event should you simply decline and leave the copyright violation sitting in the page history. There are three routes to take from here: 1) If substantially the entire page is an unambiguous copyright violation (and there's no non-infringing revision to revert to), please tag the page for speedy deletion with {{db-g12}}. This can be done using Twinkle, if you have this gadget installed, or using AFCH when you decline the draft. Don't forget to warn the user with the warning notice template that will be provided to you in the text of the speedy deletion tag. Where you have not marked the page for speedy deletion for whatever reason (e.g., removing the infringement found would still leave substantial content), you can either: 2) Send the page for investigation to Wikipedia:Copyright problems, by marking it with {{copyvio | url=insert URL}}, and then follow the instructions in the copyright investigation notice to list the page at "today's" copyright violations page and to warn the user; or 3) If you are willing to take the time to clean up the copyright problem yourself, please click "show" below for detailed instructions. Copyright cleanup instructions      (i) remove all of the copyrighted material from the draft, noting in your edit summary where it is from ("Remove copyright violation of http://www...."). Where the copying is from more than one source, it's often easiest to remove each infringement in a separate edit;      (ii) post to the draft's talk page {{subst:cclean|url=URL(s) copied from}}; just place a space between the URLs if there's more than one (note: this template automatically signs for you so place no tildes);      (iii) mark the revisions in the page history (typically the first edit and second to last edit) for redaction by an administrator by placing and saving at the top of the draft page this template: {{copyvio-revdel|start = earliest revision ID (that is, the number at end of the revision's URL after "oldid=") | end= end revision ID}};      (iv) change the decline parameter in your AfC copyvio decline template from cv to cv-cleaned – or remove that decline entirely, since you've just cleaned it, and re-assess the draft on its other merits; and      (v) warn the user, such as with {{subst:uw-copyright-new|DraftName}}. Vandalism, negative unsourced BLP, or attack page If a submission is clearly an attack page, an entirely negative unsourced BLP, or vandalism, immediately decline the submission as such and ensure you select the check box to blank the submission using {{afc cleared}}. Also, you should immediately tag the page for speedy deletion with {{db-g10}} for attack pages and negative unsourced BLP, or {{db-g3}} for vandalism and blatant hoaxes. This can be done using Twinkle, if you have this gadget installed. Consider also warning the user on their talkpage. Nonsense or test If a submission consists of only patent nonsense or is an unambiguous test edit, decline it as a test. Test submissions with no other useful page history are also eligible for speedy deletion under criteria {{db-g2}}. Advertising Quickly read over the submission. If the submission is a blatant advertisement decline the submission as such. In some cases it may be necessary to select the checkbox to blank the submission using {{afc cleared}}; although Draft: pages are not normally indexed by search engines, they can show up on mirror sites. In extreme cases, where a submission is a blatant advertisement and the subject is clearly non-notable or otherwise unsuitable for Wikipedia, it may be appropriate to tag the submission for speedy deletion using {{db-g11}}. Blank submission Click on edit to ensure that the article is truly blank and not simply missing a closing tag. If truly blank, decline as a blank submission. However, if you look at the page history and see that it previously had content but it was 1) blanked by the same user/IP address that posted that content; and 2) there were no substantive edits by other users – you may tag it for speedy deletion using any of {{db-g7}} / {{db-blanked}} / {{db-author}}. Submission not in English If a submission is not written in English, it can be declined. Category:AfC submissions declined as not in English is linked from Wikipedia:Pages needing translation into English. Another editor might translate the submission at a later date. Already exists Sometimes new editors create a submission without checking to see if the subject already has a Wikipedia article. Do a quick search for the title of the suggested article, as well as any alternative names that come to mind. If you find an article on the same subject, decline the article. Consider making a redirect if the contributed name is useful. However, articles that have been moved manually without using the AFCH script often leave behind the original draft, instead of properly redirecting this to the article talk page. When you encounter such drafts, don't mark them as duplicates; redirect them properly. But be careful–sometimes users not entitled to accept drafts use the manual method either inadvertently or to avoid scrutiny–check the actual article carefully, because a high percentage of these are spam or otherwise unsuitable.

ขั้นตอนที่ 2: ยืนยันความโดดเด่นและตรวจสอบข้อมูล

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, 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.

Expand this box to learn about notability and verifiability

Articles require significant coverage in reliable sources that are independent of the subject. 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. Notability guidelines Subject Guideline shortcut Action Academics (professors, scientists, etc.) WP:PROF Decline the submission as about a non-notable academic Astronomical objects WP:NASTRO Decline the submission as about a generally non-notable subject Books WP:NBOOK Decline the submission as about a generally non-notable subject Events WP:NEVENT Decline the submission as about a generally non-notable subject Films WP:NFILM Decline the submission as about a generally non-notable film Geographical features WP:NGEO Decline the submission as about a generally non-notable subject Musical performers or works WP:NMUSIC Decline the submission as about a non-notable band Organizations or companies WP:NCORP Decline the submission as about a non-notable corporation Sports and athletes WP:NSPORT Decline the submission as about a generally non-notable subject Web content WP:NWEB Decline the submission as about a non-notable web presence Other people WP:BIO Decline the submission as a non-notable biography Any subject not covered above WP:GNG Decline the submission as about a generally non-notable subject 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. Verifiability Reason for denial Action Insufficient reliable sources to verify the content of the submission. Decline the submission as lacking sufficient references to verify the content.

ขั้นตอนที่ 3: พิจารณาความเหมาะสม

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.

Expand this box to learn about unsuitable articles

Types of unsuitable articles Reason for denial Action Nothing more than a dictionary definition Decline the submission as a nothing more than a dictionary definition A non-notable neologism Decline the submission as a nothing more than a non-notable neologism Appears to be a joke or hoax Decline the submission as a joke Does not conform to the BLP policy Decline the submission as not conforming to the BLP policy Is not written from a neutral point of view Decline the submission as not written from a neutral point of view Insufficient context Decline the submission as having insufficient context to make the subject understandable Too short, but could be merged into Article Decline the submission as too short and suggest a suitable title for the content to be merged into (if applicable). Generally, the author should be able to do this themselves. Anything else covered by WP:NOT Decline the submission as not suitable for Wikipedia; consider writing a custom decline reason in these cases, explaining exactly why the submission is not suitable.

ขั้นตอนที่ 4: ให้ผ่านฉบับร่าง

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:

Expand this box to learn about accepting a submission

Click the Accept button. Select an appropriate name Give the article an assessment on the quality scale Consider adding categories, and/or appropriate cleanup templates or stub-tags by entering the code in the relevant boxes. Add any Wikiproject banners that would apply to the article by inserting the template code into the relevant box. 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. 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. 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. 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). Known issues If a submission, which should be accepted, cannot be moved because the page title is blacklisted, or the page is creation protected, you will get one of the following error messages: If a proposed article title is triggering the 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 find an administrator who will be able to assist you. If the destination page has been creation protected because of repeated recreation, it will be necessary to make a request for unprotection at Wikipedia:Requests for unprotection.

ขั้นตอนที่ 5: ดำเนินการในเรื่องอื่น ๆ

Please read Wikipedia's username policy and if you recognize that a user has a prohibited username, tag the user's talk page with {{subst:Uw-username|Reason}}. This tag is also used by Twinkle under: warn → Single issue warnings → {{uw-username}}. If the username is a blatant violation of the username policy, consider reporting the username to usernames for administrator attention.

ดูเพิ่ม

ให้ผ่านฉบับร่าง

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.

ปัดตกฉบับร่าง

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.

กรณีอื่น ๆ

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: (Wikipedia:Disambiguation or Wikipedia: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 Wikipedia:Deletion policy and instructions for opening an AFD for more information.)

เก็บกวาดฉบับร่าง

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.

ถามคำถามหรือแสดงความคิดเห็นต่อฉบับร่าง

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.

ปฏิเสธฉบับร่าง

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.

ส่งฉบับร่างในเนมสเปซอื่น

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 {{Afc submission}} template can be moved to AfC space regardless of their status, if it beneficial to do so.

ส่งฉบับร่างเพื่อตรวจซ้ำ

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.

การตรวจทานด้วยตนเอง

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 {{Afc submission}}. If you do this, be careful to follow every step exactly.

ปูม

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