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.04 Media Content

     

    1.       Each CD should be “self-contained”. If 5 CDs arrive and the load files for all 5 CDs reside on CD #5, then that is wrong. The idea here is to be able to reload any CD as quickly as possible. Sometimes collections become separated over time. It is conceivable that CD #5, with all the database and image load files, could be lost. This means CD #1 through #4 are now incomplete. Each CD should be self-contained.

    2.       For a given project, all load files (Concordance .DAT and Opticon .LOG) should use the same field names, ordering and structure as the first delivery.

    3.       A "synch" file provides the text to go with the video. That term is generic. There are multiple file types to consider. If you are a Sanction user, you want an .MDB. The vendor cannot tell what formats the Litigation Support person uses unless they are told or request that information.

     

    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