October 10, 2011

Text data management, Part 1: Confusion

This is Part 1 of a three post series. The posts cover:

  1. Confusion about text data management.
  2. Choices for text data management (general and short-request).
  3. Choices for text data management (analytic).

There’s much confusion about the management of text data, among technology users, vendors, and investors alike. Reasons seems to include:

Above all: The use cases for text data vary greatly, just as the use cases for simply-structured databases do.

There are probably fewer people now than there were six years ago who need to be told that text and relational database management are very different things. Other misconceptions, however, appear to be on the rise. Specific points that are commonly overlooked include:


2 Responses to “Text data management, Part 1: Confusion”

  1. Mike on November 10th, 2011 5:23 pm

    I have used Temis system a lot.
    what would you say about the strenghts and weaknesses of it in comparison with Lexalytics or Attensity…u know?

  2. Curt Monash on November 10th, 2011 8:20 pm

    Temis and Lexalytics aren’t the same thing, I’d think. Temis and Attensity are closer.

    That said, I haven’t talked with the Temis folks for a few years. My first thought would be to look at Temis first for French or Italian, but Attensity for English.

Leave a Reply

Feed: DBMS (database management system), DW (data warehousing), BI (business intelligence), and analytics technology Subscribe to the Monash Research feed via RSS or email:


Search our blogs and white papers

Monash Research blogs

User consulting

Building a short list? Refining your strategic plan? We can help.

Vendor advisory

We tell vendors what's happening -- and, more important, what they should do about it.

Monash Research highlights

Learn about white papers, webcasts, and blog highlights, by RSS or email.