|
|
Home | TOC | Previous | Next | Download
1.
When there is bad
OCR, an appropriate error code and warning to the firm is required. Things such
as handwriting and graphics will not provide good OCR results. As such the
vendor must warn the firm and Litigation Support about these issues and the
associated “<<OCR ERROR>>” text. In this fashion, the
law firm knows a legitimate error from a missed problem. This can result in a "false
positive" in terms of QC looking for errors.
2.
Vendor must use Auto-Rotate
on every image. This ensures the 5 – 10% of images facing sideways or
upside-down get quality OCR. Documents such as hierarchical employee charts are
almost always designed landscape instead of portrait. All of these names and
titles should be easy to OCR, unless auto-rotate is off.
Home | TOC | Previous | Next | Download
Contact Ad Litem
(C)2005 Ad Litem Consulting, Inc.
|
About Litigation Support Technical Standards
This document was initially designed to eliminate any discrepancy between firm technical needs and how the vendor created the technical aspect of their products. Litigation Support spends needless hours changing the vendor delivery. The firm pays for product that litigation support will have to modify. Today, the document covers as many technical requirements as possible for as many types of discovery and software as possible.
To get a good idea of the reason for these explicit directions, please visit the final section of this document entitled, “Things not to do”. All of these examples are from real life. All of these examples caused headaches, delaying reviews, productions and more.
I hope that this document is helpful to you.
|
Template by Steves Templates
|
|
