Ad Litem Consulting, Inc.
|
|||||||||||||||||
|
|||||||||||||||||
|
Homepage Intro Acknowledgements License Preface 1.00 Introduction 2.00 Business Standards 2.01 Outgoing Media Kit
3.00 Technical Standards2.02 Cost Codes for Litigation Support 2.03 Request for Quotes ("RFQs") 2.04 Quotes 2.05 Weekly Updates 2.06 Color Blindness 2.07 Quality Control 2.08 Required Test Load 3.01 Media Labels
4.00 Software Specific Requirements3.02 File, Folder and Volume Naming 3.03 CD Content and Organization 3.04 Organization of Sub-Folders 3.04.01 Images Folder
3.05 Bates Schemes3.04.02 OCR Folder 3.04.03 Data Folder 3.04.04 Project Folder 3.04.05 Attach Folder 3.06 Data Files 3.07 Database Conventions 3.08 Native Files 3.09 Project Specifications Document 3.10 Bibliographical Coding Manual 3.11 Image Format 3.12 OCR 3.13 Slip-Sheets or Unitization Rules 3.14 Video 3.15 Synchronization 3.16 Transcripts 3.17 Delivery Media 4.01 Casesoft Suite
5.00 Examples of What Not To Do4.02 IPRO 4.03 Dataflight's Concordance and Opticon 4.04 Image Capture Engineering 4.05 Summation 4.06 iCONECT 4.07 inData TrialDirector 4.nn Additional Titles to Follow 5.01 Media Labels
5.02 File / Folder / Volume Name Conventions 5.03 Database 5.04 Media Content 5.05 Load Files 5.06 OCR 5.07 Opticon Load Files 5.08 Image Format 5.09 Transcripts 5.10 General Errors / Issues 5.11 Real Experiences |
3.04.05 Attach Folder - Technical Standards 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\
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. |
||||||||||||||||