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.07 Database Conventions - Technical Standards There are two main categories of discovery: electronic and paper. Electronic discovery software extracts “metadata” from the file. The metadata contains fields and values ranging from email subject to the last print date of a spreadsheet. Different file types may yield different types metadata. This means the firm may need to pay for bibliographic coding for certain kinds of electronic discovery to achieve a complete database. If 20% of a database has no author information, this will impact search results and confidence. All electronic discovery yields “full text”. Full text is quite literally all the text inside a word processing or spreadsheet file or any other electronic files. Full text removes the need for OCR. Like OCR, full text does not provide bibliographic coding such as author and recipient. Full text will provide 100% accurate content where paper OCR may be 80% accurate or better, depending on the quality of the paper. Load File Field Order As possible, the firm attempts to keep field order consistent for like types of databases. As such, the firm appreciates the vendor matching their load file to our field order. Our document reviewers expect to see the same fields in the same order for all databases. Please help us make this happen. The exclusion of certain fields or their incorrect order may require Litigation Support to bill time to the client for correcting these problems. This is one reason why the Database Structure file (see 3.06) is so important. While the vendor should provide the Firm with every field possible for electronic discovery, the following list from the law firm includes certain fields that we require at a minimum and in the following sequence. Depending upon the production or pre-production status of a collection, certain fields may contain no data. Please refer to the Bibliographic Coding Instructions for bibliographic coding. Note: These files, “load file field order” and “bibliographic coding instructions” should reside in the “DATA” and “PROJECT folders”, respectively, on the delivery. |
||||