Channels ▼

Jolt Awards: The Best Books

, October 01, 2013 Five notable books every serious programmer should read.
  • E-mail
  • Print

Productivity Award: Taming Text

By Grant S. Ingersoll, Thomas S. Morton, and Andrew L. Farris

Perhaps once a year, I have the experience of picking up a book on a topic I'm unfamiliar with and immediately becoming absorbed by it. I started reading this volume to get a sense of the major issues and solutions in text processing and found myself devouring the book — sneaking it into meetings and any other place where I could spend a few more minutes working my way through it.

Handling unstructured text (that is, text in documents, rather than databases) presents all kinds of complex problems, most of them having to do with the central role of natural language. For example, the problem of stemming (which is the process of reducing variants such as plural of nouns, verb tenses, etc. to their canonical form), searching, fuzzy searches, indexing, parsing, and categorizing.

The authors' explanations of these problems are supremely readable and the solutions are presented with code implementations. Where possible, the authors rely on open-source tools, such as Lucene, Solr, Apache Mahout, OpenNLP, and others to do the heavy lifting. In addition to algorithms, this book shows how to build text-processing clusters, manage document libraries for processing, and handle other pragmatic concerns.

The final third of the book is dedicated to the unique challenges of how to tag and classify documents automatically. Despite the wealth of techniques provided earlier, the problem of entity recognition (for example, does "Polish doorknob" refer to an item or to a task?) is presented and explained in all its gory complexity. At times, the challenges seem intractable, but as the authors demonstrate time and again, there are good, available tools and specialized algorithms that can get you most of the way through the wilderness.

At no point does the presentation become so esoteric as to lose the reader — rather, the authors of Taming Text keep finding stimulating ways to lead developers into new areas that need to be mined for optimal results to ensue.






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.