Format Of Production – Page 8 – Electronic Discovery Law

Wal-Mart Stores, Inc. v. Cuker Interactive, LLC, NOo. 5:14-CV-5262, 2015 WL 11120890 (W.D. Ark. April 9, 2015)

Dec 01 2015

Key Insight: Where parties agreed to produce in native format but Defendant then loaded its information into a hosted database and indicated that Plaintiff could view the docs, including some metadata, but could only receive production of specified documents in a static image format, at a cost for each such ?exportation,? and where Defendant argued such production complied with Rule 26(f) and that the data was in a reasonably usable form, the court held the parties to their agreement, reasoning that ?[s]imply put, native format means native format? and also rejected Defendant?s security concerns, agreeing with Plaintiff that production on an external hard drive was acceptable; court?s order stated that parties would ?produce discovery from electronic or computer-based media directly to each other in native format, on external hard drives whenever possible.?

Electronic Data Involved: ESI

Arkansas River Power Auth. v. Babcock & Wilcox Power Generation Grp., Inc., No. 14-cv-00368-CMA-NYW, 2015 WL 2128312 (D. Colo. May 5, 2015)

Dec 01 2015

Key Insight: Addressing several disputes, court concluded that parties having agreed on an ESI production ?must only comply with Rule 34(b)(2)(E)(ii)? and that the question was therefore whether the defendant ?produced its ESI in the form in which it is ordinarily maintained or in a reasonably usable form or forms. The rule clearly requires one or the other, but not both.?; where defendant produced majority of its documents in a reasonably usable form (TIFF), court declined to compel production of additional metadata

Nature of Case: Breach of contract and related claims

Electronic Data Involved: ESI

Moore v. Wayne Smith Trucking, Inc., No. 14-1919, 2015 WL 6438913 (E.D. La. Oct. 21, 2015)

Dec 01 2015

Key Insight: Court concluded that Facebook materials are discoverable but would not require Defendant to produce his username and password and instead ordered Defendant to provide his attorney with postings from the relevant time period to be reviewed by the attorney?and not the defendant?to identify responsive information

Nature of Case: Personal injury

Electronic Data Involved: Social network contents (e.g., Facebook, MySpace)

Truesdell v. Thomas No. 5:13-cv-552-Oc-10PRL, 2015 WL 2022991 (M.D. Fla. Apr. 30, 2015)

Dec 01 2015

Key Insight: Court denied Motion to Compel Production of Electronically Stored Data where plaintiff said that 1500 printed pages of defendant?s database usage history were inadequate under FRCP 34(e)(ii) because they were not easily searchable. Plaintiff sought to compel production of the electronic version of the data to include metadata, but the court said that the printed information was not as cumbersome as the plaintiff suggested because only a limited time period contained within the pages was relevant; the data did not originate from the defendant, so the defendant did not have the ability to manipulate the data to provide it only for the limited time period; and the plaintiff was unable to identify any information contained in the electronic version of the data that was not also contained in the printed pages.

Nature of Case: Privacy Rights

Electronic Data Involved: Database

In re State Farm Lloyds, 13?14?00616?CV, 2015 WL 6520998 (Tex. App. Oct. 28, 2015)

Dec 01 2015

Key Insight: Court denied petition for writ of mandamus, where real party properly requested native and near-native format of production for ESI, including metadata, under Texas Rules of Civil Procedure 196.4. Court said that relator was not entitled to unilaterally produce ESI in a ?reasonably usable? format and had offered only conclusory testimony that production of ESI in the requested format was unduly burdensome.

Nature of Case: Insurance claim

Electronic Data Involved: ESI

Wilson v. Conair, No. 1:14-cv-00894-WBS-SAB, 2015 WL 1994270 (E.D. Cal. Apr. 30, 2015)

Dec 01 2015

Key Insight: Although ?[t]he rules do not require a party to produce ESI in the form most helpful to the opposing party[,]? the court ordered Defendant to produce additional discovery in TIFF format and to produce the metadata for all documents already produced (in PDF format)

Nature of Case: Class action

Electronic Data Involved: ESI (.xls, proprietary format)

SFP Works LLC v. Buffalo Armory LLC, No. 14-13575, 2015 WL 7294580 (E.D. Mich. Nov. 19, 2015)

Dec 01 2015

Key Insight: Where Plaintiff alleged it could not access the data produced by defendant?even with the use of specialized software provided by Defendant and the assistance of a third party vendor?and refused the options provided by defendant insisting instead that defendant must re-load the date to ensure it was not corrupted, the court noted Plaintiff?s failure to timely seek a solution to the discovery problems or to mitigate the difficulties by pursuing any of the offered remedial measures and denied the motion to compel access to the at-issue information

Nature of Case: Patent infringement

Electronic Data Involved: ESI (“operational data”)

Banks v. St. Francis Health Ctr., Inc., No. 15-cv-2602-JAR-TJJ, 2015 WL 7451174 (D. Kan. Nov. 23, 2015)

Dec 01 2015

Key Insight: Addressing Plaintiff?s Motion to Compel, court overruled Defendant?s objection to producing ESI in native format with metadata where Defendant failed to indicate in its objection the form of production it intended to use instead and did not support its objection by explaining why it could not or should not be required to produce as requested and, in fact, admitted that it had previously produced material in native format; court denied without prejudice Plaintiff?s motion to compel responses outlining Defendant?s search efforts (sometimes called “discovery on discovery”) where Plaintiff?s counsel failed to confer with Defense counsel prior to bringing the motion, as is required by the District of Kansas? ESI Guidelines

Nature of Case: Title VII: racial discrimination, retaliatory conduct

Electronic Data Involved: ESI

Dekeyser v. Thyssenkrupp Waupaca Inc., No. 08-c-0488, 2015 WL 10937559 (E.D. Wis. Apr. 10, 2015)

Dec 01 2015

Key Insight: Where Defendant initially produced material safety data sheets in TIFF format and later in hard copy but Plaintiff complained they were ?extremely difficult? to utilize because of the number of duplicates, the ?absence of organization? and the small font size (despite having relied upon the productions for purposes of summary judgment), court was swayed by Plaintiff?s expert?s articulation regarding the lack of burden rather than Defendant?s vague attestations of the burden of reproduction and, reasoning that Plaintiff had not produced all of the information requested in its initial production (e.g., certain data fields from the database in which the material safety data sheets were maintained) and that the prior productions were in a form that degraded searchability, ordered reproduction of the requested information i.e., ?all data and information maintained in [Defendant?s] databases relating to the MSDS and all data inputted by [Defendant] concerning the same, in an electronic, organized and usable format.?

Nature of Case: FLSA

Electronic Data Involved: Contents of database

Good v. Am. Water Works Co., Inc., No. 2:14-1374, 2015 WL 1757978 (S.D. W. Va. Apr. 17, 2015)

Dec 01 2015

Key Insight: Where defendant objected to Plaintiffs? requests for production on grounds of relevance, but nevertheless produced the information in the format in which it was ordinarily maintained (Microsoft SQL Server format) and also provided Plaintiffs with the means to access the data in a ?parallel environment? and then later in an excel format for a limited period of time, indicating that the earlier periods of time were not reasonably accessible, and where Plaintiffs ultimately ?did not disagree? that the information was not as useful as they had thought, the court found the rest of the requested information (from the earlier time periods) was not reasonably accessible and that the burden of production outweighed its likely benefit and denied the motion to compel unless good cause could be shown

Electronic Data Involved: Archived ?SCADA? data from a Microsoft SQL Server format

Tag:Format Of Production