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.05 Bates Schemes - Technical Standards


While it is helpful to have a “significant” Bates prefix (“ACME” versus “A”), brevity is not without merit. Use the “KISS rule”: keep it simple, Simon. Just think how many times you will need to write or enter the prefix. Also, there are computer issues that almost mandate certain syntax. Please use the following conventions when constructing the prefix.

We recommend using the project name for the prefix. In this fashion, each collection, project, Bates and files carry the same name. If you have 5 separate discovery collections, you will have 5 projects, 5 unique Bates prefixes and 5 unique filename prefixes. When it is time to produce, a new Bates scheme can be applied.

Guidelines for creating a correct Bates prefix:

  1. No more than 5 characters wide
  2. Only use uppercase letters from A to Z
  3. Bates prefix should not end in “L”, “O”, “I” or “D”
  4. No spaces or hyphens between the prefix and number

Explanations / Examples:

  1. Good Bates prefixes include: A, AA, AAA, AAAA, AAAAA.
  2. Bad Bates prefixes include: 9A, 9A9, A9, A9-, A-A-A, 0-A-0, A 0001.
  3. OCR may mistake certain letters for the numbers “1” and “0”.

Rules for creating a correct Bates suffix:

  1. Suffix should be numeric
  2. Suffix should be zero-padded to four (4) positions, the ten-thousandths place
  3. Suffix should never contain spaces, hyphens, underlines or characters other than 0 through 9.

Good Bates suffixes include: .0001, .9999, .0100
Bad Bates suffixes include: .A, .0A, .A01, .A-1

Examples:
The following two tables will show the identical ranges using proper and incorrect prefixes and suffixes.

Correct Bates ranges:

BegBates

EndBates

Description

A001

A010

Prefix is short. Easy to see where prefix ends and

A011

A011

the next Bates number begins.

A011.0001

A011.0026

Zero-padded and numeric ensures proper sorting and

A011.0027

A015

software friendly format.

A016.0001

A016.0010

  

Incorrect Bates ranges:

BegBates

EndBates

Problem

A9001

A9010

Is the document number 1 or 9001?

A9011

A9011

Is the prefix A or A9?

A9011.A

A9011.Z

Suffix is a letter, resulting in sorting issues.

A9011.BA

A9015

Suffix contains letter(s), resulting in sorting issues.

A9016.1

A9016.10

Suffix has no zero-padding resulting in bad sorting.
Also, inconsistent suffix naming convention.

 

 

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