User:Lingzhi/reviewsourcecheck

This script simplifies source reviews by flagging 16 types of errors in the references and/or notes. It is a fork of Ucucha's HarvErrors2 script; it produces no output if harv templates are not being used.

To check as many errors as possible, I recommend using this in conjunction with two others

1. First, copy/paste importScript('User:Ucucha/HarvErrors.js'); to Special:MyPage/common.js .
2. On the same page and below that script, add one of these two variants, depending on where on the page you wish to add a link that toggles between "Hide ref check" and "Show ref check". Both versions should store the page state (whether reference errors/warnings are "hidden" or "shown"). The state persists between page loads and between the browser closing and reopening (unless cleared by the user, for example by deleting data in your browser's cache etc.). Huge thanks to User:Evad37 for much coding help:
   1. If you want to add a tab to the drop-down tab at the top, located between the 'watchlist star' and the search box (using the vector.js skin), add importScript('User:Lingzhi2/reviewsourcecheck.js');

      

   2. If you want a link to be added to the Toolbar section on the left side of the page, add importScript('User:Lingzhi2/reviewsourcecheck-sb.js');.
3. Finally go to to Special:MyPage/common.css and add .citation-comment {display: inline !important;} /* show all Citation Style 1 error messages */.

• (Other unrelated but quite useful tools include IABot's Analyze a page, reFill, User:Citation bot/use, and User talk:GregU/dashes.js)

When you've added those, go to an article to check for various messages in its notes and references. (You may need to clear your browser's cache first).

After the explanatory #Common sense and #Cascading errors sections, the #Descriptive table section below gives a short summary of the messages generated by this script (other messages that you may see are output from the other scripts, of course). Below that is a dummy article with some examples of errors in notes and references for you to examine.

OCLC, Archive links and odd, incongruous errors

1. If you need to find an OCLC number, go to WorldCat.org and use the "Find items in libraries near you" search. From the results, click the link for the item you're interested in. The output of that search also includes the OCLC Number, a little bit down the page.
2. Missing archive link: Archiving is not required, but is considered good practice. This is flagged even if an access date is present. To archive: Go to an articles History and click the "Fix dead links". On the "IABot Management Interface", find the small drop-down menu that says "Run Bot" and select "Fix a single page"). Type a Wikipedia article's title on the line that says "Page title to analyze" Be sure to check the checkbox labeled "Add archives to all non-dead references (Optional)". Run time for the bot can be from a few seconds to several minutes.
3. If the script displays some sort of an odd, incongruous error, such as "Missing pagenums for book chapter?" for a news article, check to see if you're using {{citation}} or {{cite book}} or whatever instead of {{cite news}}. Since this sort of template mismatch often may not change or disturb the output that the readers see, it may not be an urgent problem.

Common sense

Use these warnings and error messages with a spoonful of caution and common sense. For one thing, editors have some discretion in whether they wish to use some template parameters. A good example is |location= for books: many editors considered these mandatory for books, because different publisher locations may produce different formats with different pagination. However, the only unbreakable rule is that usage must be consistent. This script generates a running count of books with and without publisher location. If one or more Inconsistent Location warnings are displayed, go to the last instance and look at its totals. If most (but not all) of the books cited include a location, suggest that the editor(s) fill in the missing location(s) as often as possible. If there are many without a location and a few with, you could suggest removing those few. [Or just go ahead and suggest they fill them all in. Consider it a public service].

Another example is the messages regarding adding access date and archive urls/dates. Editors have even more discretion with these than they do with |location=. Per WP:CITE, |access-date= is only required for web sources without a known publication date. In practice, moreover, some relatively stable urls (e.g., those from Google Books) may not need access dates either. In general, however, try to encourage consistency, because access dates are often very useful. Access dates aid automated tools (and humans) in locating the correct version of an archived web page, or in adding archive links in the future. Even with relatively stable resources like Google Books, there's no future guarantee that the source will remain accessible, so the access date is an indication that at least at one time that it was.

Note that P/PP error? is the check that seems to display the greatest number of false positives. There's simply no way to cover all the possible variations that could be displayed. Treat this as marking "something to check; it could well be wrong" rather than a definitive error.

Also note that sometimes you also need to apply a little knowledge of the outside world. A relatively amicable historian would be amused/bemused to see Missing first name for: Suetonius:

• Suetonius (2008), Edwards, Catherine (ed.), Lives of the Caesars, Oxford University Press, ISBN 9780191609107

Bede (860). "St. Gallen Stiftsbibliothek Cod. Sang. 254. Jerome, Commentary on the Old Testament book of Isaiah. Includes the most authentic version of the Old English "Death Song" by the Venerable Bede". Europeana Regia. Retrieved 5 June 2013.

Cascading errors

Correct use of the |location= requires consistency, while references such as {{cite book}} and {{cite web}} need to be sorted systematically if they are grouped together in their own dedicated section. Correct use of |location= parameters depends on whether or not other sources on the page include that parameter, and correct placement of a reference within sort order depends on the sort order of the references above it. For this reason, the programming logic for both "Inconsistent use of Location" and "Sort error, expected: <identifier>" displays error messages that are cascading .

For the sort errors, the first reference listed out of sort order causes that reference and perhaps many or all subsequent ones to display the error message. The first reference listed out of sort order will often throw others below it out of sort order too. If there are several, start from the top and work down when correcting. Fixing one or two might clear many errors. This is a cascading error; when fixing, start at the first instance & go down.

It is very strongly suggested that the |location= field be populated, but one could argue that it is not, strictly speaking, absolutely required. However, there is a requirement that it be employed (or not employed) consistently. As a case in point, this version of our article on "Slavery" has (looking at last instance in the running total) "Inconsistent Location (16 with; 141 without)". If that article were in FAC it might be possible (but notvery advisable) to delete the 16 locations.

Descriptive table

Error and description

Error message	Comments
P/PP error? very short snip;	Page ranges for footnotes. In the footnote, if the page range given includes a dash or hyphen or comma, it should say "pp." and not "p.", and vice versa. As discussed earlier, this check is a time saver that is not foolproof. Produces some false positives.
Caution: No ref= anchor;	If a source that is sitting within a large References section has no |ref=, it may be difficult to spot the fact that it isn't pointing to anything at all in the article's body text. This locates such instances. A slight drawback is that sometimes you don't want source to link to anything (e.g., "Further reading"). If the resulting warning messages annoy you, use |ref=0 in the cite template.
Hyphen in pg. range;
Missing identifier (ISSN, JSTOR, etc.);	Only for periodicals
Warning: duplicate author/date;	For example, if there were three instances of "Bhattacharya, Sanjoy (2002)", the second and third would be flagged (but not the first). Editors should modify all three to appear as "Bhattacharya, Sanjoy (2002a)", "Bhattacharya, Sanjoy (2002b)" and "Bhattacharya, Sanjoy (2002c)".
Missing first name for: Asimov;	No check performed if the citation includes et al.
Inconsistent first name fmt.([some number] full, [some number] abbrev);	Full or abbreviated first names, as for example "Wang, N." versus "Wang, Nancy". The respective numbers in "[some number] full" and "[some number] abbrev" indicate the running total of each; the underlined one indicates whether the current reference is full or without a abbreviated.
Inconsistent Location ([some number] with, [some number] without);	Only for books. The respective numbers in "[some number] with" and "[some number] without" indicate the running total of each; the underlined one indicates whether the current reference is with or without a location. There's no requirement that the |location= field be populated, but there is a requirement that it be employed (or not employed) consistently... see this parameter as discussed in both #Common sense and #Cascading errors.
Caution: Missing pagenums for book chapter?
Missing Publisher;	Only for books. I was unable to see anything in the page source which would facilitate flagging websites with no publisher.
Missing ISBN;	Books, if publication year >= 1970
Pub. too early for ISBN;	You do the math. This could be caused by a typo, but more likely indicates the source is a reprint (which therefore should include an |orig-year= parameter).
Missing OCLC;	Books, if publication year < 1970
Missing Year/Date;
Missing archive link;
Missing access date;	NOT flagged if a publication date or an archive date is present.
Sort error, expected: Wiznewsky;	See #Cascading errors. Only checks within sections that have one of the following headings: "Biographies", "Bibliography", "References", "Citations_and_notes", "Literature_cited", "Works_cited", "Book_sources", "Primary_sources", "Secondary_sources", "Sources", or "Specialized_studies". Should be able to handle pages with more than one section of references (e.g., Primary and secondary) and sort each separately. Should not sort sections where references are listed in order of occurrence (and are not intended to be sorted). The sort uses javascript's sort(Intl.Collator()) function so it is relatively language-sensitive for Romanized scripts, but it is not foolproof. In fact it is probably adrift with non-Romanized text such as "สองศิษย์เอกธัมมชโยโต้ขอกล่าวหาวัดพระธรรมกาย". You'll just have to discuss those with other editors.

Dummy article (example)

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

References

• "Fighting for Respect: African-American Soldiers in WWI" (PDF). Archived from the original (PDF) on 2005-09-07.
• Asquith, Novalyne; True; Grit (1980), Day of the Stranger, Necronomicon Press
• Green, Novalyne (1969). G'bye, Have a Nice Trip. Necronomicon Press. ISBN 978-0-19-155371-4.
• Xanadu, Novalyne; Burke (July 1963). Day of the Stranger. Chicago: Necronomicon Press. OCLC 978-0-19-155371-4. {{cite book}}: Check |oclc= value (help)
• Champion, Novalyne (2009), Day of the Stranger, Necronomicon Press, OCLC 23940321
• Aasenthal, Amy (March 2, 2004). "King's books". Chicago Sun-Times.(subscription required)
• Absenthal, Ben (March 2, 2004). "King's books". Chicago Sun-Times. Sun-Times Media Group. Retrieved September 30, 2017.(subscription required)
• Rosenthal, Phil (March 2, 2004). "Atmosphere as thick as one of King's books". Chicago Sun-Times. Sun-Times Media Group. Retrieved September 30, 2017.(subscription required)
• de Camp, L. Sprague (1975), The Miscast Barbarian, Gerry de la Ree. Chapbook. Later expanded into Dark Valley Destiny.
• Weigold, Auriol (1999). "Famine management: The Bengal famine (1942–1944) revisited". South Asia: Journal of South Asian Studies. 22 (1): 63–77. doi:10.1080/00856409908723360.
• "36 U.S. Code § 210303 - Purposes". Legal Information Institute. 2014. Retrieved 10 December 2014.
• "369th Infantry Regiment "Harlem Hellfighters"". BlackPast.org. Retrieved 12 March 2015.
• "369th Regiment Armory, The Harlem Armory, Central Harlem". Harlem One Stop. 2014. Retrieved 10 December 2014.
• American Battle Monuments Commission (1944). "93d Division: Summary of Operations in the World War". The U.S. Army Center of Military History. Retrieved 10 December 2014.
• "American National Biography Online: Johnson, Henry".
• "Battlefield 1 Early Enlister Deluxe Edition".
• Kalikimake, John D. (2011). "Kahuku Army Air Base: One of Oahu's World War II Satellite Fields" (PDF). American Aviation Historical Society Journal (Spring): 52–61.
• "Editorial: For Henry Johnson, honor in sight".
• Ford, Rebecca (7 March 2014). "Sony Nabs Max Brooks' WWI Graphic Novel 'The Harlem Hellfighters'". The Hollywood Reporter. Retrieved 12 April 2014.
• Gates, Jr., Henry Louis (2014). "Who Were the Harlem Hellfighters?". PBS. Retrieved 10 December 2014.
• Gero, Anthony; Smith, Nancy; Jones; Anderson. Black Soldiers of New York State, A Proud Legacy. MyFirst Publisher.
• Gilbert King. "Remembering Henry Johnson, the Soldier Called "Black Death"". Smithsonian.
• "Greenstreet: NYC Parks". New York City Department of Parks & Recreation. 2014. Retrieved 10 December 2014.
• "Harlem Hellfighters, Harlem, NY 1913". Harlem World. Retrieved 12 March 2015.
• "Harlem Hellfighters". MAAP: Mapping the African American Past. 2014. Retrieved 10 December 2014.
• "Harlem River Drive: Historical Overview". NYC Roads. 2014. Retrieved 10 December 2014.
• Lanum, Mackenzie (2014). "Paige, Myles Anderson (1898-1983)". The Black Past: Remembered and Reclaimed. Retrieved 10 December 2014.
• Lewis, William Dukes (2003). "A Brief History of African American Marching Bands". FolkStreams. Retrieved 10 December 2014.
• Livas, Nicole (7 November 2008). "The 369th Veterans Association". WAVY Blogs. Retrieved 10 December 2014.
• Mikkelsen, Jr., Edward (2014). "369th Infantry Regiment "Harlem Hellfighters"". The Black Past: Remembered and Reclaimed. Retrieved 10 December 2014.
• National Park Service. "National Register Information System". National Register of Historic Places. National Park Service.
• Nelson, Peter (2009). A More Unbending Battle: The Harlem Hellfighter's Struggle for Freedom in WWI and Equality at Home. Basic Books. ISBN 978-0-7867-4467-1.
• Robertson, Stephen (1 February 2011). "Parades in 1920s Harlem". Digital Harlem Blog. Retrieved 10 December 2014.
• "U.S. 10th Army (Okinawa) Order of Battle, April 1945" (PDF). US Army Combined Arms Center. 2014. Retrieved 10 December 2014.
• "U.S. Renames 369th: Now 'Colored Infantry'". Chicago Defender. 1940. Retrieved 20 February 2015.
• Wang, Hansi Lo (1 April 2014). "The Harlem Hellfighters: Fighting Racism In The Trenches of WWI". Code Switch. NPR. Retrieved 10 December 2014.
• Wintz, Cary D.; Finkelman, Paul (6 December 2012). Encyclopedia of the Harlem Renaissance. Routledge. ISBN 978-1-135-45536-1.
•  This article incorporates public domain material from 369th Sustainment brigade. United States Army Institute of Heraldry.
•  This article incorporates public domain material from websites or documents of the United States Army Center of Military History.