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.10 General Errors / Issues

     

    1.       Databases and Opticon load files where every document is one page. While possible and quite likely to have 1 single page document, a database comprised entirely of 13,000 one-page documents is highly unlikely.

    2.       While a document containing 13,000 pages is possible, is it unlikely. A database with several 13,000 page documents is extremely unlikely. This could be a physical versus logical document breaks issue.

    3.       Do not create a new image sub-folder for each document. A CD with 300 1-page documents should result in 1 folder of 300 images. 300 folders each containing 1 page is incorrect.

    4.       When generating electronic or paper documents, the vendor should never add their company information to the header or footer.

    5.       Add your own real life war stories to the growing list. Visit http://www.eDiscovery.org today.

     


    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