Ad Litem Consulting, Inc.

Ad Litem Consulting, Inc.
Technical Standards
   Includes:
     - Load Files
     - Cost Codes
     - Quotes
     - For Vendors
     - For Firms

Newsletter Signup
Read about litigation tech strategies and best practices for the case and firm.
Litigation Support Department
Includes:
   - Budget Spreadsheet
   - Needs Assesment
   - Case Technology Plan
   - Task and Check Lists
   - Member's Area Access

    

Homepage

Intro
Acknowledgements
License
Preface
1.00 Introduction
1.01 For Vendors
1.02 For Firms
1.03 How to Use This Document
2.00 Business Standards
2.01 Outgoing Media Kit
2.02 Cost Codes for Litigation Support
2.03 Request for Quotes ("RFQs")
2.04 Quotes
2.05 Weekly Updates
2.06 Color Blindness
2.07 Quality Control
2.08 Required Test Load
3.00 Technical Standards
3.01 Media Labels
3.02 File, Folder and Volume Naming
3.03 CD Content and Organization
3.04 Organization of Sub-Folders
3.05 Bates Schemes
3.06 Data Files
3.07 Database Conventions
3.08 Native Files
3.09 Project Specifications Document
3.10 Bibliographical Coding Manual
3.11 Image Format
3.12 OCR
3.13 Slip-Sheets or Unitization Rules
3.14 Video
3.15 Synchronization
3.16 Transcripts
3.17 Delivery Media
4.00 Software Specific Requirements
4.01 Casesoft Suite
4.02 IPRO
4.03 Dataflight's Concordance and Opticon
4.04 Image Capture Engineering
4.05 Summation
4.06 iCONECT
4.07 inData TrialDirector
4.nn Additional Titles to Follow
5.00 Examples of What Not To Do
5.01 Media Labels
5.02 File / Folder / Volume Name Conventions
5.03 Database
5.04 Media Content
5.05 Load Files
5.06 OCR
5.07 Opticon Load Files
5.08 Image Format
5.09 Transcripts
5.10 General Errors / Issues
5.11 Real Experiences




5.05 Load Files - Technical Standards


OCR right arrow

Concordance Load Files

  1. A .DAT load file without a supporting file showing: field structure, field size and field sequence.

  2. The first line of the .DAT file should be the field names. When loading a .DAT file, this is the simplest way to see if the data loaded correctly.
  3. Badly formatted body Meta-Data. The spaces and returns must match the original text. No odd characters, such as a semi-colon, should appear in lieu of a soft-return or a space. These kinds of problems not only make the text hard to read, but they also interfere with searching.

  4. More than one document per database record. This kind of error can cost the Firm hours and days or a case. When the review team identifies all the documents to produce, a ratio other than 1:1 will result in the wrong documents getting produced along with the right documents.
  5. Databases and load files should open sorted by “Bates” or “docno”. Concordance displays records in the same order that they were loaded. Therefore a disordered load file results in a disordered database.

  6. Duplicate, overlapping or gaps in “Bates” or “docno” fields.
  7. Bates / Docno prefix contains characters other than A…Z.

  8. Bates / Docno suffix contains letters and is not zero-added to four places (.0001).

  9. Bates / Docno contains a space, such as “AA 00001”.
OCR right arrow
©2006 Ad Litem Consulting, Inc. - Litigation Support Services