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




4.06 iConect - Technical Standards


iCONECTnxt (from iCONECT Development, LLC)

This section was provided by iCONECT Development, LLC.

iCONECTnxt Data Load Files

iCONECTnxt supports the following load file types:

  • CSV file
  • Delimited text file / Customized load files
    The user can choose from pre-defined templates or specify custom delimiters.
  • OCR text files / Load List files
    If OCR content was not part of the original data import, the OCR text can be loaded later by using an OCR Load List file (your vendor may refer to this as a “Control List”). The OCR Load List file maps the OCR text files to the appropriate record in an iCONECTnxt database by using a cross-referencing field (typically the Bates number field).

The OCR Load List file from your vendor will have the following structure:

MSC0010042,J:\[VOLUME]\OCR\MSC001042.txt
MSC0010046,J:\[VOLUME]\OCR\MSC001046.txt

The first field (in the example above, a Bates number) identifies the record that requires the OCR text. The second field provides the path to the OCR text file.

Note: In the example above, the Bates number (e.g., MSC0010042) matches the name of the OCR text file. However, the OCR text file can be named differently (this is up to your vendor).

Tip: Your vendor should prepare the OCR Load List file to cross-reference at the record (not page) level (i.e., one text file per record regardless of the number of pages in that record). This format will allow the OCR to be loaded when your vendor has placed the text files in subdirectories.

iCONECTnxt Image Load Files

Images are loaded into iCONECTnxt through the use of an Imagelink file that maps the physical location of images to an iCONECTnxt database field. This enables users to launch images directly from an iCONECTnxt database by clicking a link.

The Imagelink file content can imported from one of the following load file types:

  • Doculex 5
  • Opticon

Note: If the load file is not Doculex 5 or Opticon, you can use a free load file converter (IConvert) available from IPRO at http://www.iprotech.com.

To learn more about iCONECT, please visit http://www.iCONECT.com.

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