Text Correcting with Virginia Chronicle

Hello Virginia Chroniclers:

Here’s a reminder that as a registered user of Virginia Chronicle, the Library of Virginia’s digital newspaper collection, you can assist in improving search results by correcting inaccurately translated newspaper text.

Optical Character Recognition (OCR), the software which reads a scanned newspaper page to create a searchable text file, is not 100 percent accurate. Many things can affect OCR accuracy, including broken or blurry type, text that is too dark or too light, mixed fonts, etc. Therefore, we need users to correct words the human eye can read that OCR cannot.

To become a registered user, go to the Virginia Chronicle page and click “Register” in the upper right corner of the home screen and enter the necessary information. Once you are registered, you will need to log in with your email and password whenever you would like to correct text in Virginia Chronicle.

Home page


LoginNext, go to the newspaper page you would like to correct, right click on the page and choose “Correct page text” from the three options. There is also a “correct this text” option on the left side of the screen under “Why may this text contain mistakes?”

CorrectA “Correct Text” column appears on the left with text that has been read by Optical Character Recognition software while the newspaper image displays on the right. You can place your cursor anywhere under the “Correct text” column on the left and begin text corrections–a corresponding red box will appear over the newspaper image to show you where you are on the page. Before leaving each section–usually pages are sectioned by column indicated by a blue block–click the “save” button to save any changes you’ve made.

And that’s all there is to it! You’ll see that the it’s a fairly easy process once you actually begin correcting text.

You can also click on the “How to correct text” link or to the “Help” feature for detailed instructions as well.

Correct2The Virginia Newspaper Project would like to extend a big thank you to the registered users of Virginia Chronicle who have already corrected over 300,000 lines of text!

Thanks to engaged users like them, this great research tool is made even better. Thank you!text correctors


Posted by in Uncategorized.
Tags: , , , , , , .

2 Responses to Text Correcting with Virginia Chronicle

  1. Bruce in Blacksburg says:

    I have been using this resource extensively to find historical information about Virginia Tech, the Farmers Specials that operated on rails and water just after the turn of the last century, and aspects of the Norfolk & Western Railway. I have found a great deal of info about the traveling agriculture shows and some detailed reports on the travels of the VT Corps of Cadets.

    A question, though — when correcting text, should it be submitted “as is” with obvious typos, or should those be corrected? Typically the problem is with a missing letter or an obviously misspelled word.

    Also, would consideration be given to finding another way to enter corrected text? I have taken to grabbing a block of text and copying it into BBEdit (I’m a Macintosh user), then making the corrections in that text editor. Once done, I delete all the existing text, then drag and drop (or cut and paste) the corrected text line by line. While this works, it is a tad tedious. Being able to take care of an entire block of text would speed up things.

    • Kelley says:

      Great question! The general consensus is that you can correct the obvious typos in the original newspaper. Veridian, the software that hosts Virginia Chronicle, is set up to keep a copy of the original text and the corrected text, so all bases should be covered. We will definitely look into an alternative way to enter corrected text that might save time.

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>