Indic Wikisource Proofreadathon May 2020/Rules

Indic Wikisource Proofreadathon May 2020

• Home
• Help & Discussion
• Participants
• Rules
• Book list
• Award
• Progress
• Result

Rules

1. The contest will run from 01 May 2020 to 10 May 2020 (inclusive).
2. Indian Standard Time (UTC+05:30) as recorded by the Wikimedia servers applies.
3. Only edits made during the set contest time will count for scoring.
4. Only the texts listed in this book list count for scoring.
5. A user who proofreads a page earns three (3) points. A user who validates (checks) a page earns one (1) point.
6. We encourage you to not edit the same page at same time. Try to maintain a gap of at least 20 pages between proofreaders.
7. Just saving computer-generated, unproofread text does not count as contributing to the page.
8. For problematic pages:
   1. No points are awarded if they are still problematic at the end of the contest.
   2. If the problem is solved before the end of the contest (allowing the page to be marked proofread), then the three (3) points earned will be split between contributors to the page.
9. Pages without text earn no points.
10. Use of bots or other automatic editing is not allowed. (Aside from the cheating aspect, bots cannot correctly identify OCR errors in a text.)
11. If it becomes necessary, cheating or other misbehaviour will be assessed by the Wikisource community. Users judged to be cheating in either the letter or the spirit of this contest may have their score annulled.
12. If a user engages in any misconduct or other vandalism in the proofreadthon, the user will be warned the first two (2) times this occurs and given the opportunity to correct themselves. If the same misconduct occurs three (3) more times after that, the user may be disqualified from the proofreadthon. Some examples of misconduct include, but are not limited to, the following:
    • saving a page as proofread without modifying the page;
    • saving a page as validated without properly reviewing the page;
    • (if you are a reviewer and a participant) reviewing a page that you proofread/validated yourself;
    • saving pages with bots or automatic editing (see point 10 above);
    • making edits in order to inflate your edit count.
13. If a page is saved (assigned as proofread/validated) with a few minor mistakes, the following apply:
    • The save can be accepted if the user corrects these mistakes later. Administrators/reviewers are requested to please notify the user to correct the page within at least one day time (24 hours).
    • If corrections are not made 24 hours after being notified, administrators/reviewers may revert the contribution, assign the proofread/validated page as demoted, and reduce the user's score by three (3) points/one (1) point.
14. The decision of the administrator/reviewer will be final. No arguments will be entertained during this proofreadthon.

Scoring system

During the contest people can help proofread and validate book pages on Wikisources. For each page, either proofread or validated, a participant gains points. At the end of the contest, a prize is awarded to the Wikisourceror with the most points. Second and third-place prizes are awarded with a random drawing from all the remaining contestants: each point that gained during the contest is like a lottery ticket, so that the more points one has gained during the contest (that is, the more pages one have proofread or validated), the more chances one has to win.

There are three components to the score:

1) the total number of points;

2) the total number of validations performed; and

3) the total number of constructive contributions of all sorts.

Scoring system

Legend	Action taken	Points	Validations	Contributions
	From any status to Proofread:	3 points	0	1
	From Proofread to Validated:	1 point	1	1
	If a Validated page is demoted:	-1 point	-1	-1
	If a Proofread page is demoted:	-3 point	0	-1
	Problematic page	0 point	—	—
	Page without text	0 point	—	—
	Unproofread page	—	—	—

How

General

The proofreading texts section lists the texts that are being used for this contest. Each bold title links to an "index page" which is the central page for proofreading of any work on this project. On that index page will be a list of pages: a list of page numbers under the heading "Pages". Each page number will link to a page that needs to be proofread. They are colour-coded to show how far along they are. In the end, every page needs to be fully proofread and validated (green) or have no text on it (grey).

Users will be scored on each page they proofread during the competition.

Proofreading

Proofreading on Wikisource involves two people per page. The first proofreads the page; the second checks it. There is a traffic light system to show how complete a page is at the moment.

Proofreading means making the text in the editable text box match the text in the page scan as much as possible. The most important part is making sure that the text is the same but formatting should be matched wherever possible too. When the first person has finished a page, they should save it with the Proofread status (yellow). If they want to save the page at any point before finishing it, they should save it with the Not Proofread status (red).

When a page is proofread, someone else (and it needs to be someone else) should check the page to make sure that it does match the original page scan. If it does, this second person should save it with the Validated status (green). They are allowed to make changes to fix any problems they find while they are doing so.

As with any traffic light, there are also the blue and grey statuses. If the first person finds something they cannot do (eg. an illustration they can't include, some unusual characters they can't type, etc), they should save it with the Problematic status (blue). If the page is blank, it doesn't need to be proofread and can just be saved with the Without Text status (grey).

Other points

• If you are new to Wikisource, it might help to check out the Help pages, especially Beginner's guide to proofreading and subsequent pages.
• Handling the split between pages can be tricky. The computer assumes that the first word on the next page follows the last word on the current page. When this isn't true, the user needs to show the computer what to do:
  • If a word is split between pages, uses the {{hyphenated word start}} and {{hyphenated word end}} templates (or their shortcuts: {{hws}} and {{hwe}}). For example, at the end of the first page write {{hyphenated word start|bad|badger}} and at the start of the second page write {{hyphenated word end|ger|badger}}.
  • If the end of a page is also the end of a paragraph, add {{nop}} to the end of the page to tell the computer to start a new paragraph.
• The index talk page might have specific information about proofreading or other issues affecting a specific work.

Guidelines admin/reviewers

• The Administrator/Reviewer should check the proofreaded pages as many as possible. They should behave with wiki-Etiquette, and Assume good faith to new wikisource user.

• If any user haven't proofread any page with community proofread standard as per respective community, the Administrator/Reviewer should send the messages about his/her mistakes to the user who will do the proofread.The user has time to rectify 24hr his/her mistake.

• After 24hr Administrator/Reviewer may revert that page, if the user not rectify his/her mistakes. Here is the decision of Administrator/Reviewer where he/she revert the pages OR validate the pages, if there was minor spelling mistake or layout issues. Try to ignor the users minor mistakes and send the messages the same to users talkpage. If the user deliberately doing the same minor mistakes repetitively, you may revert this as per rule.

• Administrator/Reviewer has right to revert the pages. The native marking happened as Rule 13 & 14 when the Administrator/Reviewer revert the pages. Before revert, the Administrator/Reviewer should send the messages about his/her mistakes to the user who will do the proofread/validate. The user has time to rectify 24hr his/her mistake.

• The any user repeated the same mistakes ,the user may be out of this proofreadthon.

• If it becomes necessary, cheating or other misbehavior will be assessed by the Wikisource community. Users judged to be cheating either the letter or the spirit of this contest may have their score annulled.

• Follow the rules as describe above.

• The Administrator/Reviewer should check the copyright status of the book before proofreading. The book should be PD-India Tag

FAQ

• How the proofreading edithon dates are selected?

• CIS-A2K team was discussed about this edithon first week of April. We announced it 15th of April. For preparation for this edithon we give the minimum 15 days time. So 1st May is the best time for the community.

• How the admin/reviewer has been selected?

• Preferably self-nomination accepted. According to experience, any Wikisource active user may add their names at the Administrator/reviewer section.

• Could admin/reviewers are participate this edithon?

• Yes.Administrator/reviewer may joint as a participants.

• Who can participate this Proofreadthon?

• Any one may joint as participants.

Please feel free to ask the question(s) on the talk page.