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.02 IPRO

     

    This section provided by IPRO.

     

    IPRO Tech, Inc. - LFP File Format

     

    LFP files (also called load files) are used to build the image database and to instruct IPRO View how to display a project’s images.  The image’s file location; file type, boundary, and Bates number make up the LFP file.

     

    Here are three methods for creating an .LFP file.

     

    First, the discovery vendor provides an LFP file upon completion of the imaging phase for a project or case.

     

    Second, one can use IPRO's free utility, IConvert.

     

    This is a free download at http://www.IproCorp.com.

     

    The IConvert tool will convert many load file formats to either LFP or other software formats, such as Summation and Opticon. It is a handy tool for people who don't even use any other IPRO products internally.

    Third, manually edit or create an LFP file using a text editor.

     

    Each record (or line) in the LFP file begins with a 2-letter code that determines the action the viewer will perform. To load an image, we will start the line with IM.

     

    Commas separate some parts of the record along with semi-colons for the rest of the line.  The command in the LFP file takes effect after you load or import the LFP file. (Import > Import LFP File from the IPRO Tech Utility menu).

     

    Here are two examples of an LFP record. In our examples, we use the MSC collection. It contains two documents, two pages each. The volume name is MSC001.

     

    Example 1: Single Page .TIF files

     

    IM,MSC00014,D,0,@MSC001;IMAGES\ 00\ 00;MSC00014.TIF;2

    IM,MSC00015,,0,@MSC001;IMAGES\ 00\ 00;MSC00015.TIF;2

    IM,MSC00016,D,0,@MSC001;IMAGES\ 00\ 00;MSC00016.TIF;2

    IM,MSC00017,,0,@MSC001;IMAGES\ 00\ 00;MSC00017.TIF;2

     

    Example 2: Multi-Page .TIF files

     

    IM,MSC00014,D,1,@MSC001;IMAGES\ 00\ 00;MSC00014.TIF;2

    IM,MSC00015,,2,@MSC001;IMAGES\ 00\ 00;MSC00014.TIF;2

    IM,MSC00016,D,1,@MSC001;IMAGES\ 00\ 00;MSC00016.TIF;2

    IM,MSC00017,,2,@MSC001;IMAGES\ 00\ 00;MSC00016.TIF;2

     

    Note: Because the files are multi-page, the entire bates range (or image key range) must point to the same .TIF file. As example, MSC00014 contains both "14" and "15". Therefore, to view page 15, the computer must display MSC00014.TIF.

     

    The following provides a breakdown of the fields:

     

    Value

    Description of Purpose

    IM

    Import code identifier (Importing New Page/Image database record)

    MSC00014

    The image key/document id number

    D

    Document designation; only designate the first page of each document.

    0

    Offset to the Tiff file.  Always 0 for single page tiff files.  When creating Multi-Page Tiff files, this number will increment for the pages within the file.  (If there is an 11 page document, the offset would start at 1 and end at 11 and the next tiff file would start over at 1.

    @MDEMO

    CD volume name

    IMAGES\00\00

    Directory path on the CD for the image

    MSC00014.TIF

    Filename for the image.

    ;2

    Tells IPRO the Types* of image file, e.g. tiff, PDF

     

    *Supported Image Types and their specification in the LFP file are:

     

    1.                   Type 1 is for IPRO Tech image from DOS-Based version, still supported (.IMG)

    2.                   Type 2 is for Standard single and multiple page black & white or color TIFF (.TIF)

    3.                   Type 3 is for IPRO Tech stacked TIFF (.STF)

    4.                   Type 4 is for Color image (.BMP, .PCX, .JPEG or .PNG)

    5.                   Type 5 is for black & white .PDF

    6.                   Type 6 is for Color .PDF

    7.                   Type 7 is to Auto-detect the .PDF type, e.g. Color or Black & White

     

    To learn more about IPRO, please visit http://www.iprocorp.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