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.04.05 Attach Folder

    This is the home of native files. If there is a movie clip or spreadsheet associated with the collection, this is where is must reside. Of course, once on the folder, the full path will be:

     

    X:\ATTACH\CLIENT#\MATTER#\DATABASE NAME\VOLUME\ATTACH\

     

     

    FOLDERS

    CONTENT

    D:\[VOLUME NAME]\ATTACH\0001\

    The first 1,000 native files

    D:\[VOLUME NAME]\ATTACH\0002\

    The next 1,000 native files

    D:\[VOLUME NAME]\ATTACH\0003\

    And so on…

    D:\[VOLUME NAME]\ATTACH\0004\

    …and so forth

    D:\[VOLUME NAME]\ATTACH\0005\

     

     

    NOTE: Zero-Padding is very important. This is especially true if you have 9999 subfolders.

     

    One of the reasons why it is important to have a standard number of native files per folder is so that Litigation Support can easily determine where missing attachments may reside.

     

    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