Ad Litem Consulting, Inc.

Ad Litem Consulting, Inc.
Technical Standards
   Includes:
     - Load Files
     - Cost Codes
     - Quotes
     - For Vendors
     - For Firms

Newsletter Signup
Read about litigation tech strategies and best practices for the case and firm.
Litigation Support Department
Includes:
   - Budget Spreadsheet
   - Needs Assesment
   - Case Technology Plan
   - Task and Check Lists
   - Member's Area Access

    

Homepage

Intro
Acknowledgements
License
Preface
1.00 Introduction
1.01 For Vendors
1.02 For Firms
1.03 How to Use This Document
2.00 Business Standards
2.01 Outgoing Media Kit
2.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.00 Technical Standards
3.01 Media Labels
3.02 File, Folder and Volume Naming
3.03 CD Content and Organization
3.04 Organization of Sub-Folders
3.05 Bates Schemes
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.00 Software Specific Requirements
4.01 Casesoft Suite
4.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.00 Examples of What Not To Do
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.08.02 Relational Databases - Technical Standards


Certain software stores data in such a way that it will not make sense if printed in linear fashion. A "relational" database presents such a dilemma. A relational database stores related information in multiple tables. Each table therefore only presents part of the actual picture. It is only by matching up records across the tables that the combined data presents useful and complete information.

The best way to present this information is to print a report using the relational database software.

Relational databases should be reviewed in native format. The document review system should include a record that references the relational databases.

In the case of an accounting system, the Firm may decide to employ an expert witness who will review in native format. Production may consist of reports the expert printed. Alternately, the other side may be able to send their own expert to use the accounting system and print their own reports for their review.

Other databases may result in printed pages as a result of review. These pages should be treated per the accounting system example.

©2006 Ad Litem Consulting, Inc. - Litigation Support Services