At long last, with several copies in production `pre-release` use, I will be letting NCT Compliance Search 1.0 out into the public. The key difference between `Compliance Search` and nearly any other search product, is that normally a search tool isn't designed to find everything that could possibly match. Rather, they're all designed to sort through the potential matches and return a manageable set most likely to contain what you're looking for. In short, they're really more of a `filter` than a `collector`. They're designed NOT to find everything.
Compliance search is designed to find absolutely all matches, and store them in a safe spot where you can then print, archive, or otherwise manipulate them. A search tool gives you a list of what it found and a short description. Compliance search copies the actual document, or optionally `renders` that document to appear as it would if viewed natively in that source database (usually for non-mail databases where viewing a document out of context is not effective).
Compliance Search is being used by companies driven by a legal requirement to report all documents which mention a key phrase, and by companies looking to track activity related to a particular product or event. In addition to finding matches among documents, NCT Compliance Search can optionally reproduce an entire reply chain thread if just a single document member of that thread contains a match.
The very first production use of the product generated this quote, which I am eternally grateful for having recieved permission to publish.
`Worked out great ! On the real search I received 22 results that searched
46 gig and finished in under five minutes. I was using two threads so as
not impact my mailserver.`
John Teer, D-Link Systems
Comment Entry |
Please wait while your document is saved.
still was in my philological profession. Such a tool would enhance a lot the
datacollection, that was that painfull back then and was really necessary to be
able to do the real work on the material later on.