Summation’s demise?

I guess you would have to say that this blog concerns litigation support and my single emphasis of getting rid of Summation by the year 2010 in the law firm setting.  I’d like to just get rid of it right now if I could.  (The same things goes for Concordance for all you out there using that.)  I mean, why are we doing this to ourselves?  We hate using these awful databases.  They suck.  Nobody likes using them.  But we go ahead and deploy these useless no-good programs anyway on a daily basis that cost our clients plenty of $$$, and from what I can tell from my 20 years worth of experience, for no-good reason that I can think except to keep the economy going?  I mean KA-Ching.  This sh*t is expensive.  I hate to think this, but who else is benefitting from useless garbage databases except the vendors who are making out like bankers?  Hum, who are these vendors who have pathed themselves in a little niche with one little word, “processing,” in the EDRM metrics?  Hum….  Well, I think we should replace this one little word, “processing,” altogether; scrap it in the scrapheap database junkyard where it belongs, and get ourselves around to better words, such as “indexing,” and “migrating,” and “universal viewer,”  where we should have been throwing our clients’ money around since 2000 at least when Microsoft created the first indexing server.  Duh.  So, this is the topic of my blog. No, not the rantings of a lunatic indentured servant who works for a law firm!  But, better “death to the database.”  That’s it.  So, come along into the world of data manipulation, what tools are cool, and how can we start focusing on solutions to make our lives better.   And I need your help.  I wish I had $300,000 for a contest, but I don’t.  I’m just a Werkin Gurl like you.  But I would like a few developers to pay attention, wrap a viewer around a search string or two and give me a line to code.  I’m not asking for too much.