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.08 Image Format

     

    1.       Multi-Page TIFFs. There are two major problems with multi-page TIFFs. The main issue is the inability to easily divide one document into two. Selecting the “logical bindings” option in scanning along with use of slip-sheets is a great way to ensure the required one document to one record division in the database.

    2.       Unless otherwise specified, we do not want Bates stamps or any other type of stamp applied to our images.

    3.       TIFF images of Excel spreadsheets where columns are too narrow causing cell content to appear as “#######” instead of the actual value.

    4.       TIFF images of Excel spreadsheets where the cells show the formula instead of the resulting value. An example of this would be a summing cell that should show the grand total for a column but instead shows something such as “=sum(A1..A10)”.

     

    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