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


    5.05 Load Files

     

    Concordance Load Files

    1.       A .DAT load file without a supporting file showing: field structure, field size and field sequence.

    2.       The first line of the .DAT file should be the field names. When loading a .DAT file, this is the simplest way to see if the data loaded correctly.

    3.       Badly formatted body Meta-Data. The spaces and returns must match the original text. No odd characters, such as a semi-colon, should appear in lieu of a soft-return or a space. These kinds of problems not only make the text hard to read, but they also interfere with searching.

    4.       More than one document per database record. This kind of error can cost the Firm hours and days or a case. When the review team identifies all the documents to produce, a ratio other than 1:1 will result in the wrong documents getting produced along with the right documents.

    5.       Databases and load files should open sorted by “Bates” or “docno”. Concordance displays records in the same order that they were loaded. Therefore a disordered load file results in a disordered database.

    6.       Duplicate, overlapping or gaps in “Bates” or “docno” fields.

    7.       Bates / Docno prefix contains characters other than A…Z.

    8.       Bates / Docno suffix contains letters and is not zero-added to four places (.0001).

    9.       Bates / Docno contains a space, such as “AA 00001”.


    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