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

 3.03 CD Content and Organization - Technical Standards


Each CD should contain the same folders each time. This structure is important, as the media is not copied to a single subfolder. Instead, “data” goes under a different folder tree than “images”. If not segregated, Litigation Support will have to perform this separation.

D:\[VOLUME NAME]\

Your CD should have a root folder, named the same as the volume name.

D:\[VOLUME NAME]\IMAGES\

All images and image subfolders reside here.

D:\[VOLUME NAME]\OCR\

This folder contains multi-page ASCII text files. The filename matches the “BegBates” key, e.g. A001.TXT, A011.TXT, and A013.TXT.

D:\[VOLUME NAME]\DATA\

All “load”, “database”, “structure” and technical files reside here.

D:\[VOLUME NAME]\PROJECT\

1. Document coding instructions,
2. Project manuals,
3. Vendor contact information,
4. Source information,
5. Ranges information.

D:\[VOLUME NAME]\ATTACH\

All native files reside here, as applicable.

NOTE: Each CD must be self-contained. This means a CD containing A001…A010 must contain the images, database load file, OCR and cross reference file for A001...A010. A delivery of CD01...CD10 should have the load files for CD01 on CD01. Having load files for CD01...CD10 all reside on CD10 is incorrect. If the firm loses the “load files” CD, the corresponding CDs may not be usable. Further, this means tracking down 2 CDs every time there is a problem.

 
©2006 Ad Litem Consulting, Inc. - Litigation Support Services