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 File / Folder / Volume Naming - Technical Standards


The following explains how data should be organized on your deliverable to the Firm. Please let us know if you cannot meet this standard, and what standard you are prepared to deliver.

16-Bit vs. 32-Bit
Older computer software could only use filenames and folder names of very limited length. This is known as the 8.3 naming convention. If a filename is wider than 8 characters, 16-Bit programs truncate the name. So suddenly the filename “AMURPHY0000001.TIF” becomes “AMURPH~1.TIF”. If the vendor is using older software, they may be restricted to 8.3 filenames. As such, they can create a file named 0000001.TIF but not AMURPHY0000001.TIF. This restriction is a serious problem. The vendor must contact Litigation Support to determine a remedy.

File and Folder Names
1. Only the characters A...Z and the numbers 0...9 are valid
2. Filenames should be unique, matching the image key
3. Image folder names should be zero-padded to 3 wide (i.e. 001, 002, 003, 004…)

NOTE: The filename must match the image key. The only exception is where the image key contains additional characters that must be echoed in the .TIF file name. If the vendor cannot provide the full image key, please alert the Litigation Support Department immediately.

While the following is syntax for an Opticon “.LOG” load file, please use the same logic when generating the IPro “.LFP” and Summation “.DII” formats as part of every delivery. For additional examples, please look at the section 4.00 Software Specific Requirements.

Database

Cross Reference File

Actual Filename

Image Key

Image Key

Path To TIFF

 

A001

A001

D:\A001\IMAGES\001\A001.TIF

A001.TIF

Volume Names
Each CD should conform to the same standard: [PROJECT NAME][999]. So, if our project is named SMITH, the first three CDs delivered should be named: SMITH001, SMITH002 and SMITH003. Note the zero-padding.

Unless the project name is “VOL”, the volume name of the first CD should never be “VOL001”. Many applications use the name “VOL” as a default value. This has resulted in many CDs named “VOL001”. This can make identification of the related case and content difficult when the Firm has 2,000 CDs named VOL001. Do not use the vendor name as the volume prefix. Use project name as the volume name. The Bates prefix can be an acceptable project name as the volume prefix, but must confirm with the firm as to final decision. Vendors should never use their company name as the prefix. Some firms prefer to use the client-matter number as part of the project name.

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