Litigation Support Technical Standards
by Mark Lieb



Sample Content
  • Table of Contents
  • Introduction
  • For Vendors
  • For Firms


  • Business Standards
  • Cost Codes
  • Outgoing Media Kit
  • RFQs
  • Quotes


  • Technical Standards
  • Media Labels
  • Bates Schemes
  • Native Files
  • File-Folder Names


  • Downloads
  • The Standard
  • The Book


  • Software Load Files
  • CaseSoft
  • IPRO
  • To Be Added


  • What Not To Do
  • Media Labels
  • Load Files
  • Transcripts
  • General Errors


  • More Resources
  • LSVA
  • Litigation Support
  • Ad Litem Consulting


  • Mark Lieb
    Ad Litem Consulting



    litgation





    Home | TOC | Previous | Next | Download


    4.06 iCONECT

    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.

     


    Home | TOC | Previous | Next | Download


    Contact Ad Litem

    (C)2005 Ad Litem Consulting, Inc.









    About Litigation Support Technical Standards

    This document was initially designed to eliminate any discrepancy between firm technical needs and how the vendor created the technical aspect of their products. Litigation Support spends needless hours changing the vendor delivery. The firm pays for product that litigation support will have to modify. Today, the document covers as many technical requirements as possible for as many types of discovery and software as possible.

    To get a good idea of the reason for these explicit directions, please visit the final section of this document entitled, “Things not to do”. All of these examples are from real life. All of these examples caused headaches, delaying reviews, productions and more.

    I hope that this document is helpful to you.

























    Template by Steves Templates