More and more electronically stored information (“ESI”) is being housed in databases — structured data repositories — rather than in discrete word processing, spreadsheet, and presentation files. Databases house call-center records, sales and warehouse information, and numerous web sites. E-mail messages may be archived in large databases. And yet, in spite of its critical relevance in litigation and regulatory matters, few - if any - standards have emerged for properly preserving and producing this type of ESI.
The Sedona Conference® Working Group 1 on Electronic Document Retention and Production has just published a new commentary on the discovery of information from databases that analyzes issues surrounding the reasonable and defensible treatment of some of the most common structured data repositories in use today. The Database Principles address key areas of disagreement between litigants, including defining relevance in the context of multi-field, multi-record databases; identifying useful formats for the production of relevant database information; and validating data extracted from larger databases.
This 90-minute webinar, presented by members of the Database Principles drafting and editing team, will provide a brief background regarding the organizational nature and structure of common databases before discussing how the six new Database Principles can be used to find an appropriate way to share (and to protect) database information in discovery. Pricing
$79 Working Group Members of The Sedona Conference®
$99 General Public
Watch This Seminar Now!
CDs:
To purchase a CD of this program, please call 1-800-701-5161. Discounts
apply for program registrants.
The Sedona Conference® Database Principles: Addressing the Preservation and Production of Databases and Database Information in Civil Litigation
Presentation
How are databases different from discrete files?
Why are current “best practice” discovery requests poorly matched to database discovery?
What is “relevant” in a database?
Negotiating reasonable production formats
Validating database information: mechanical vs. substantive accuracy