Most of the the press and commentary we’ve seen about Google’s new Ngram Viewer has been extremely positive (here’s our post from last week with links to several articles). However, today we came across a very interesting and very well written/documented blog post by Natalie Binder, a librarian and information science student at Florida St. University.
“Google’s word engine isn’t ready for prime time” (by Natalie Binder, The Binder Blog)
Here are two brief paragraphs from the blog post:
The whole idea of Ngrams is built on a shaky foundation: the accuracy of Google’s optical character recognition (OCR) software. OCR is how a computer “reads.” When a paper document is scanned, it’s essentially a “dumb document.” The text is not searchable because a computer doesn’t know the difference between a printed word and an image.
Accurately digitizing a book requires hundreds of hours of hard work, because a human being has to go through and hand-correct these errors (see my previous article on OCR, “A breadful book“).
She also points to the challenge of getting quality metadata when scanning documents. She also includes a link to the widely read 2009 blog post by Geoffrey Nunberg, “Google Books: A Metadata Train Wreck.”
This [metadata] is not a small problem. These types of issues are rampant in Google Books. Moreover, Google may not be able to count on crowd wisdom to fix these problems. Codicology (the study of the physical properties of books) and cataloging are highly specialized professional fields, both of which require Master’s degrees. These types of errors undermine trust in Google’s entire cataloging system. Until these issues are resolved, serious scholars of the humanities cannot approach Google Books as a trustworthy scholarly source. _Unless it can somehow prove its accuracy, ngrams sinks in the same boat.
We think it’s also important to mention that in the comments section of the blog post, Binder is very clear that the issues she’s writing about are not really an nGrams problem but with the scanned material it utilizes.
Don’t get me wrong; I think this is a great first step. These technical problems have to do with Google Books, not ngrams itself. If Google fixes Books, ngrams will be much better.
In a second blog post, “The problem with Google’s thin description” one point that Binder makes is that even if the data is correct, the multiple meanings of words can cause challenges.
See Also: “When OCR Goes Bad: Google’s Ngram Viewer & The F-Word” (by Danny Sullivan, Search Engine Land)
Via Resource Shelf
TeleRead: News and views on e-books, libraries, publishing and related topics