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

    3.08.02 Relational Databases

    Certain software stores data in such a way that it will not make sense if printed in linear fashion. A "relational" database presents such a dilemma. A relational database stores related information in multiple tables. Each table therefore only presents part of the actual picture. It is only by matching up records across the tables that the combined data presents useful and complete information.

     

    The best way to present this information is to print a report using the relational database software.

     

    Relational databases should be reviewed in native format. The document review system should include a record that references the relational databases.

     

    In the case of an accounting system, the Firm may decide to employ an expert witness who will review in native format. Production may consist of reports the expert printed. Alternately, the other side may be able to send their own expert to use the accounting system and print their own reports for their review.

     

    Other databases may result in printed pages as a result of review. These pages should be treated per the accounting system example.

     

    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