Case Law

“Rap Weasel” Forced to Honor $1 Million Reward Offered via YouTube – eDiscovery Case Law

It isn’t every day that eDiscoveryDaily has reason to reference The Hollywood Reporter in a story about eDiscovery case law, but even celebrities have eDiscovery preservation obligations during litigation.  In Augstein v. Leslie, 11 Civ. 7512 (HB) (SDNY Oct. 17, 2012), New York District Judge Harold Baer imposed an adverse inference sanction against hip hop and R&B artist Ryan Leslie for “negligent destruction” of a hard drive returned to him by the plaintiff after a $1 million reward was offered via YouTube.  On November 28, a jury ordered him to pay the $1 million reward to the plaintiff.

Reward Offered, then Refused

While Leslie was on tour in Germany in 2010, a laptop and external hard drive (that contained some of Leslie’s songs not yet released) were stolen.  Capitalizing on his popularity on social media, Leslie initially offered $20,000 for return of the items, then, on November 6, 2010, a video on YouTube was posted increasing the reward to $1 million.  The increase of the reward was also publicized on Leslie’s Facebook and Twitter accounts.  After Augstein, a German auto repair shop owner, returned the laptop and hard drive, Leslie refused to pay the reward alleging “the intellectual property for which he valued the laptop was not present on the hard drive when it was returned”.

Plaintiff’s Arguments as to Why Reward was not Warranted

Leslie attempted to make the case that when he used the word “offer,” that he really meant something different. He argued that a reasonable person would have understood mention of a reward not as a unilateral contract, but instead as an “advertisement” – an invitation to negotiate.

Leslie’s other argument was that, regardless whether it was an “offer” or not, Augstein failed to perform because he did not return the intellectual property, only the physical property.  Leslie claimed that he and several staff members tried to access the data on the hard drive but were unable to do so.  Leslie sent the hard drive to the manufacturer, Avastor, which ultimately deleted the information and sent Leslie a replacement drive.  The facts associated with the attempts to recover information from the hard drive and requests by the manufacturer to do the same were in dispute between Leslie, his assistant, and Avastor, who claimed no request for data recovery was made by Leslie or anyone on his team.

Judge’s Responses and Decision

Regarding Leslie’s characterization of the offer as an “advertisement”, Judge Baer disagreed, noting that “Leslie’s videos and other activities together are best characterized as an offer for a reward. Leslie ‘sought to induce performance, unlike an invitation to negotiate [often an advertisement], which seeks a reciprocal promise.’”

Regarding Leslie’s duty to preserve the hard drive, Judge Baer noted: “In this case, Leslie was on notice that the information on the hard drive may be relevant to future litigation and, as a result, had an obligation to preserve that information. Augstein contacted Leslie personally and through his attorney regarding the payment of the reward, and a short time later, the hard drive was sent by Leslie to Avastor….Leslie does not dispute these facts.”  As a result, Judge Baer found that “Leslie and his team were at least negligent in their handling of the hard drive.”

Citing Zubulake among other cases with respect to negligence as sufficient for spoliation, Judge Baer ruled “I therefore impose a sanction of an adverse inference; it shall be assumed that the desired intellectual property was present on the hard drive when Augstein returned it to the police.”  This led to the jury’s decision and award last month, causing the New York Post to characterize Leslie as a “Rap Weasel”, which Leslie himself poked fun at on Instagram.  Only in America!

So, what do you think?  Was the adverse inference sanction warranted?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

When Considering Review Solutions, Don’t Forget About Self-Documentation – eDiscovery Best Practices

When evaluating eDiscovery review solutions, there are a number of features that attorneys consider as part of their selection process.  For example: What searching capabilities does the solution have?  How does it handle native files?  How does it support annotations and redactions of images?  Can it support conceptual clustering and predictive coding?  But, one feature that often gets overlooked is the ability for the review solution to automatically document searching and review activities.  Not only does that make it easier to identify potential issues in the process; it also facilitates the ability for attorneys to demonstrate a defensible approach to discovery to the court.

There are at least three areas where self-documentation can assist in the discovery analysis and review process:

Searching: An application, such as FirstPass®, powered by Venio FPR™, that keeps track of every search in a search history can provide assistance to attorneys to demonstrate a defensible search approach.  eDiscovery searching is almost always an iterative process where you perform a search, analyze the results (often through sampling of the search results, which FirstPass also supports), then adjust the search to either add, remove or modify terms to improve recall (when responsive information is being missed) or improve precision (when the terms are overly broad and yielding way too much non-responsive information, such as the “mining” example we’ve discussed previously).

Tracking search history accomplishes two things: 1) it makes it easier to recall previous searches and “tweak” them to run a modified version of the search without starting from scratch (some searches can be really complex, so this can be a tremendous time saver) and, 2) it documents the natural iterative process of searching, facilitating the ability for attorneys to demonstrate a defensible search approach to discovery to the court, if necessary.  And, if you don’t think that ever comes up, check out these case summaries here, here, here and here.   Not only that, the ability to look at previous searches can be a shorten the learning curve for new users that need to conduct searches by giving them examples after which to pattern their own searches.

Tomorrow, we’ll discuss the other two areas where self-documentation can assist in the discovery analysis and review process.  Let the anticipation build!

So, what do you think?  How important are self-documentation features in a review solution to you?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Plaintiff Hammered with Case Dismissal for “Egregious” Discovery Violations – eDiscovery Case Law

Apparently, destroying your first computer with a sledgehammer and using Evidence Eliminator and CCleaner on your second computer (when you have a duty to preserve both) are not considered to be best practices for preservation.  Who knew?  😉

In Taylor v. Mitre Corp., (E.D. Va. Nov. 8, 2012), Virginia District Court Judge Liam O’Grady upheld the findings by the Magistrate Judge for dismissal of the plaintiff’s claims and payment of the defendant’s reasonable attorney’s fees and costs due to “egregious” discovery conduct.  Here’s why:

  • The plaintiff hired counsel back in 2009 “in anticipation of bringing this lawsuit against Mitre for violations of the FMLA and failure to accommodate his disabilities.  Mr. Taylor’s lawyer immediately put him on clear notice that he was required to maintain all files and documents (electronic and otherwise) related to his claim, and that deleting or discarding such files could result in sanctions including dismissal of his claim.”;
  • The plaintiff filed his EEOC claim in November 2010;
  • Sometime in 2011, the plaintiff “wiped” his work desktop, then “took a sledgehammer to it” and disposed of it in the local landfill (as noted in the footnote: “Mr. Taylor has given varying accounts of the size and type of the hammer he used to wreck the computer, but does not deny that he smashed it with some nature of mallet.”);
  • Before destroying his work computer, the plaintiff “attempted” to back up files from it “but was only partially successful”;
  • In November 2011, the plaintiff filed his complaint;
  • On July 1, the Magistrate Judge “ordered Mr. Taylor to submit his current computer, a laptop, to inspection within a week.”  The plaintiff “had represented that whatever documents he maintained during the partially successful backup operation described above had been transferred to the laptop, and the Defendant won permission to inspect the laptop”;
  • A few days later, the defendant’s forensic expert examined the laptop and determined that the plaintiff had “run a program called Evidence Eliminator, a program whose express purpose is removing ‘sensitive material’ from one’s hard drive and defeating forensic software.”  The plaintiff admitted that “he downloaded the program the same day he learned of the Court’s inspection order”;
  • The plaintiff also ran another program CCleaner (which also erases files from the computer so that they cannot be recovered) “at least twice between the time of the Court’s inspection order and the actual inspection.”

The plaintiff claimed “that CCleaner was set to run automatically, and so even if it did delete relevant documents, the deletion was not intentional.” – a claim that the court found to be “highly suspicious”.  However, when it came to the installation of Evidence Eliminator, Judge O’Grady did not mince words:

“For Mr. Taylor to download and run a program whose express purpose is deletion of evidence in direct response to the Magistrate Judge’s order that his computer be produced for inspection was to blatantly disregard his duties in the judicial system under which he sought relief. The Court finds Mr. Taylor’s conduct to be egregious and highly contemptuous of the inspection order. Mr. Taylor has forfeited his right to pursue his claims with this Court any further.”

So, what do you think?  Is this the most egregious example of spoliation you’ve ever seen?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

The Grossman-Cormack Glossary of Technology Assisted Review – eDiscovery Resources

Do you know what a “Confidence Level” is?  No, I’m not talking about Tom Brady completing football passes in coverage.  How about “Harmonic Mean”?  Maybe if I hum a few bars?  Gaussian Calculator?  Sorry, it has nothing to do with how many Tums you should eat after a big meal.  No, the answer to all of these can be found in the new Grossman-Cormack Glossary of Technology Assisted Review.

Maura Grossman and Gordon Cormack are educating us yet again with regard to Technology Assisted Review (TAR) with a comprehensive glossary that defines key TAR-related terms and also provides some key case references, including EORHB, Global Aerospace, In Re: Actos:, Kleen Products and, of course, Da Silva Moore.  The authors of the heavily cited article Technology-Assisted Review in E-Discovery Can Be More Effective and More Efficient Than Exhaustive Manual Review have provided a new reference document that may help many in the industry understand key TAR concepts better.  Or, at least recognize key terms associated with TAR.  This is version 1.01, published just this month and clearly intended to evolve over time.  As the authors note in the Preamble:

“The introduction of TAR into the legal community has brought with it much confusion because different terms are being used to refer to the same thing (e.g., ‘technology assisted review,’ ‘computer-assisted review,’ ‘computer-aided review,’ ‘predictive coding,’ and ‘content based advanced analytics,’ to name but a few), and the same terms are also being used to refer to different things (e.g., ‘seed sets’ and ‘control sample’). Moreover, the introduction of complex statistical concepts, and terms-of-art from the science of information retrieval, have resulted in widespread misunderstanding and sometimes perversion of their actual meanings.

This glossary is written in an effort to bring order to chaos by introducing a common framework and set of definitions for use by the bar, the bench, and service providers. The glossary endeavors to be comprehensive, but its definitions are necessarily brief. Interested readers may look elsewhere for detailed information concerning any of these topics. The terms in the glossary are presented in alphabetical order, with all defined terms in capital letters.

In the future, we plan to create an electronic version of this glossary that will contain live links, cross references, and annotations. We also envision this glossary to be a living, breathing work that will evolve over time. Towards that end, we invite our colleagues in the industry to send us their comments on our definitions, as well as any additional terms they would like to see included in the glossary, so that we can reach a consensus on a consistent, common language relating to technology assisted review. Comments can be sent to us at mrgrossman@wlrk.com and gvcormac@uwaterloo.ca.”

Live links, with a Table of Contents, in a (hopefully soon) next iteration will definitely make this guide even more useful.  Nonetheless, it’s a great resource for those of us that have bandied around these terms for some time.

So, what do you think?  Will this glossary help educate the industry and help standardize use of the terms?  Or will it lead to one big “Confusion Matrix”? (sorry, I couldn’t resist)  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Defendant Compelled to Produce Additional Discovery to Plaintiff – eDiscovery Case Law

During this Thanksgiving week, we at eDiscovery Daily thought it would be a good time to catch up on some cases we missed earlier in the year.  So, we will cover a different case each day this week.  Enjoy!

Where the facts of the case led a court to conclude that certain electronically stored information (ESI) could contain evidence relevant to the case, the court ordered a party to comply with its discovery obligations related to that ESI.

In Freeman v. Dal-Tile Corp., No. 5:10-CV-00522-BR, 2012 U.S. Dist. (E.D.N.C. Oct. 2, 2012), a case alleging harassment and discrimination, among other claims, against her former employer Dal-Tile Corporation, the plaintiff brought a motion to compel, asserting that some of the defendant’s discovery responses related to its search for ESI were deficient.

Specifically, the plaintiff sought to compel a keyword search of preserved e-mails belonging to certain individuals for a time frame that began two months after the plaintiff left Dal-Tile. The defendant objected, arguing that because the plaintiff had already left the company during the time frame for e-mails requested, any such e-mails “could not be relevant to Plaintiff’s harassment claims, because ‘the sole issue is whether Dal-Tile knew or should have known of the harassment and failed to take appropriate steps to halt it.’”

North Carolina Magistrate Judge William A. Webb disagreed, stating that it was “reasonable to expect” that e-mails written or received during that time period “could contain historical e-mails, i.e., an e-mail chain, given that the requested search period begins only two months after Plaintiff resigned.” Moreover, the plaintiff’s request hit the mark for other reasons: “The custodians whose e-mail Plaintiff requests to have searched are . . . the human resource officer who investigated Plaintiff’s complaints, and . . . the regional vice-president to whom [the human resources officer] reported her investigation findings.” In addition, the search terms that the plaintiff requested were “appropriately limited in number and scope and, thus, reasonably calculated to lead to the discovery of admissible evidence.”

Moreover, Judge Webb noted, Dal-Tile did “not assert[ ] that it would be unduly burdensome to search the e-mail[s requested]” or the hard drive of the human resources officer, a search of which the plaintiff had included in her request.

Therefore, the plaintiff’s motion was granted.

So, what do you think?  Should the plaintiff’s motion have been granted?  Please share any comments you might have or if you’d like to know more about a particular topic.

From All of Us at CloudNine Discovery and eDiscovery Daily, Happy Thanksgiving!  eDiscovery Daily will resume with new posts next Monday.

Case Summary Source: Applied Discovery (free subscription required).  For eDiscovery news and best practices, check out the Applied Discovery Blog here.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Rambus’ “Shred Days” Result in Sanctions Yet Again – eDiscovery Case Law

During this Thanksgiving week, we at eDiscovery Daily thought it would be a good time to catch up on some cases we missed earlier in the year.  So, we will cover a different case each day this week.  Enjoy!

By the way, the Rambus cases are among the most “famous” from an eDiscovery spoliation standpoint.  As you’ll see from the description below, Rambus is still paying for activities way back in 1998 that have been ruled to be spoliation of data.

In Hynix Semiconductor Inc. v. Rambus, Inc., No. C-00-20905 RMW, 2012 U.S. Dist. (N.D. Cal. Sept. 21, 2012), California District Judge Ronald Whyte used his discretion to fashion an appropriate fact-specific sanctions award after it found a party willfully destroyed evidence despite reasonably foreseeable litigation, it destroyed such evidence in bad faith, and the opposing party suffered prejudice.

In this discovery dispute over spoliation and sanctions in a patent lawsuit, the district court reconsidered this case after its previous decision was vacated by the Federal Circuit and remanded. Previously, in this court, Hynix Semiconductor Inc. et al. (Hynix) had “unsuccessfully urged” that Rambus, Inc. (Rambus) had engaged in the spoliation of evidence, and “its ‘unclean hands’ warranted dismissal of its patent infringement claims.” On appeal, however, the Federal Circuit remanded the case so that the district court could consider it under a different spoliation test, which had been applied in another case presenting an identical spoliation issue, Micron Technology, Inc. v. Rambus Inc., 645 F.3d 1311 (Fed. Cir. 2011) (Micron II).

Therefore, the court had to analyze whether “Rambus destroyed records at a time when litigation was reasonably foreseeable. If so, the court will determine whether Rambus acted in bad faith. Next, the court will determine the nature and extent of any prejudice suffered by Hynix as a result of the spoliation. Finally, the court will decide what sanction is appropriate, if any.”

The court found that Rambus engaged in spoliation of evidence when it destroyed documents on “Shred Days” in 1998, 1999, and 2000 when it invited an outside company to Rambus to shred documents that employees provided for shredding in accordance with the company’s document retention policy. The court found that on those Shred Days, litigation was reasonably foreseeable. Noting that the “important question” was not when Rambus’s duty to preserve arose, “but rather the binary question of whether litigation was reasonably foreseeable by the date on which documents were destroyed,” the court found that although litigation was not foreseeable when Rambus destroyed some of its back-up tapes in July 1998, it was reasonably foreseeable by the time of Shred Day 1998.

At the time the back-up tapes were destroyed in July, the court pointed to numerous questions that existed about the success of Rambus’s patented product and what features the existing patents covered. Management had only held hypothetical discussions about potential targets of litigation, and they had not discussed in depth budgeting for litigation. Destruction of back-up tapes was done “primarily” for “housekeeping” purposes.

By the time Shred Day 1998 occurred, however, Rambus “anticipated instituting litigation.” A Rambus officer, Joel Karp, whom the company hired in 1997 to assess whether competitors were infringing on Rambus’s patents, had advised employees of the company’s documentation retention policy, and “the fact that he advised them to discard documents that questioned the patentability of ideas suggests he had litigation on his mind.” Moreover, a litigation strategy was being “aggressively developed,” and Rambus was turning its attention heavily toward a certain part of its business, which it believed it had to fight to protect.

Thus, finding that Rambus had engaged in spoliation beginning with Shred Day 1998, the court turned to analyze whether Rambus acted with “unclean hands.” The court set forth the applicable standard: “To find bad faith in the spoliation context, ‘the district court must find that the spoliating party intended to impair the ability of the potential defendant to defend itself.’” While Rambus asserted that it conducted document destruction only to execute its “neutral” document retention policy, Hynix argued that regardless of Rambus’s compliance with its own document retention policy, Rambus knew litigation was reasonably foreseeable and destroyed documents in bad faith “to gain a litigation advantage.” In addition, Hynix argued that Karp ordered Rambus employees to destroy documents selectively, keeping ones that would protect their patents and destroying ones that would cause difficulty in litigation.

Parsing the evidence, the court found:

“Although the evidence does not support a conclusion that Rambus deliberately shredded documents it knew to be damaging, the court concludes that Rambus nonetheless spoliated evidence in bad faith or at least willfully. This conclusion is based upon the facts that: (1) Rambus destroyed records when litigation was reasonably foreseeable; (2) Karp, the officer in charge of the destruction, was experienced in litigation and undoubtedly knew that relevant documents should not be destroyed when litigation is reasonably foreseeable; (3) the destruction was part of a litigation plan; (4) one of the motives of the destruction was to dispose of potentially harmful documents; and (5) Rambus shredded a huge number of documents without keeping any records of what it was destroying.”

The court then turned to the issue of whether Rambus’s bad faith spoliation of evidence had prejudiced Hynix. The Micron II court set forth the applicable standard for evaluating prejudice: “‘Prejudice to the opposing party requires a showing that the spoliation materially affect[s] the substantial rights of the adverse party and is prejudicial to the presentation of his case.’ (citation omitted) ‘In satisfying that burden, a party must only come forward with plausible, concrete suggestions as to what [the destroyed] evidence might have been.’” Moreover, if the spoliation had already been determined to have been in bad faith, the spoliating party had a heavy burden to show its document destruction had not prejudiced the other party. Yet, the court cautioned, “the alleged misconduct by the spoliator . . . must relate directly to an issue concerning which the complaint is made.”

Here, Hynix had claimed that Rambus’s patents were invalid, and the court explained, “the invalidity defenses of anticipation and obviousness depend upon how one of ordinary skill in the art would have understood the prior art.” In this case, all prior art was accessible to Hynix and therefore the document destruction did not prejudice Hynix. The other defense of “inadequate written description” similarly turned on information that was available to Hynix. As such, the court found that Hynix’s invalidity defenses were not prejudiced by Rambus’s spoliation of evidence.

On the other hand, however, the court found that Rambus did not overcome Hynix’s allegations of prejudice based on its unenforceability complaint against Rambus. The court found that “it appear[ed] plausible that spoliated evidence might have shed additional light on the scope” of certain disclosure obligations that Rambus had with respect to its patents. Because this allegation offered a concrete suggestion for Hynix as to what the destroyed evidence could have been, Rambus had a heavy burden to disprove prejudice, which the court found it could not overcome.

Having concluded that Rambus “spoliated documents in bad faith and that Hynix has established prejudice,” the court then considered sanctions, noting it had “wide discretion whether to hold the patents-in-suit unenforceable pursuant to Hynix’s unclean hands defense, or to impose a different sanction.”

The court used the following analysis to evaluate the appropriateness of sanctions:

“In gauging the propriety of the sanction, the district court must take into account

“(1) the degree of fault of the party who altered or destroyed the evidence; (2) the degree of prejudice suffered by the opposing party; and (3) whether there is a lesser sanction that will avoid substantial unfairness to the opposing party and, where the offending party is seriously at fault, will serve to deter such conduct by others in the future.” (citation omitted) The sanction ultimately imposed must be commensurate with the analysis of these factors.”

In examining the Rambus’s degree of fault, the court found that

“Rambus’s fault was significant but not as great as that of a spoliator who knows of adverse evidence and specifically alters, hides or destroys that evidence. There is a possibility that Rambus did not destroy any evidence that would have been beneficial to Hynix’s litigation position. However, because Rambus is the party that destroyed documents by the box and bag without keeping any record of what was destroyed, Rambus must suffer the consequences of that uncertainty.”

Hynix’s degree of prejudice was significant, the court held, because it “was arguably prejudiced in its ability to litigate its equitable claims and defenses,” and if it had been able to better litigate them, it possibly could have avoided a royalty fee that was awarded against it based on a previous determination that Rambus’s patents were valid.

Therefore, the court “conclude[d] that the sanction most commensurate with Rambus’s conduct and [the fact that a royalty rate was previously awarded] is to strike from the record evidence supporting a royalty in excess of a reasonable, nondiscriminatory royalty. Such a remedy recognizes that Rambus’s patents have been determined to be valid while at the same time recognizing that Rambus’s spoliation of evidence should preclude it from entitlement to a royalty that places Hynix at a competitive disadvantage.” The court decided to use its discretion to fashion a sanction, noting that “a retrial of the case with either an adverse jury instruction or an evidentiary exclusion order would involve considerably more delay and expense,” and there had already been great delay in reaching a final determination in the case.

So, what do you think?  Was it appropriate to issue sanctions at this point and, if so, were they harsh enough?  Please share any comments you might have or if you’d like to know more about a particular topic.

Case Summary Source: Applied Discovery (free subscription required).  For eDiscovery news and best practices, check out the Applied Discovery Blog here.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Louisiana Order Dictates That the Parties Cooperate on Technology Assisted Review – eDiscovery Case Law

During this Thanksgiving week, we at eDiscovery Daily thought it would be a good time to catch up on some cases we missed earlier in the year.  So, we will cover a different case each day this week.  Enjoy!

In the case In re Actos (Pioglitazone) Products Liability Litigation, No. 6:11-md-2299, (W.D. La. July 27, 2012), a case management order applicable to pretrial proceedings in a multidistrict litigation consolidating eleven civil actions, the court issued comprehensive instructions for the use of technology-assisted review (“TAR”).

In an order entitled “Procedures and Protocols Governing the Production of Electronically Stored Information (“ESI”) by the Parties,” U.S. District Judge Rebecca Doherty of the Western District of Louisiana set forth how the parties would treat data sources, custodians, costs, and format of production, among others. Importantly, the order contains a “Search Methodology Proof of Concept,” which governs the parties’ usage of TAR during the search and review of ESI.

The order states that the parties “agree to meet and confer regarding the use of advanced analytics” as a “document identification mechanism for the review and production of . . . data.” The parties will meet and confer to select four key custodians whose e-mail will be used to create an initial sample set, after which three experts will train the TAR system to score every document based on relevance. To quell the fears of TAR skeptics, the court provided that both parties will collaborate to train the system, and after the TAR process is completed, the documents will not only be randomly sampled for quality control, but the defendants may also manually review documents for relevance, confidentiality, and privilege.

The governance order repeatedly emphasizes that the parties are committing to collaborating throughout the TAR process and requires that they meet and confer prior to contacting the court for a resolution.

So, what do you think?  Should more cases issue instructions like this?  Please share any comments you might have or if you’d like to know more about a particular topic.

Case Summary Source: Applied Discovery (free subscription required).  For eDiscovery news and best practices, check out the Applied Discovery Blog here.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Judge Carter Refuses to Recuse Judge Peck in Da Silva Moore – eDiscovery Trends

It seems like ages ago when New York Magistrate Judge Andrew J. Peck denied the motion of the plaintiffs in Da Silva Moore v. Publicis Groupe & MSL Group, No. 11 Civ. 1279 (ALC) (AJP) to recuse himself in the case.  It was all the way back in June.  Now, District Court Judge Andrew L. Carter, Jr. has ruled on the plaintiff’s recusal request.

In his order from last Wednesday (November 7), Judge Carter stated as follows:

“On the basis of this Court’s review of the entire record, the Court is not persuaded that sufficient cause exists to warrant Magistrate Judge Peck’s disqualification…Judge Peck’s decision accepting computer-assisted review … was not influenced by bias, nor did it create any appearance of bias.”

Judge Carter also noted, “Disagreement or dissatisfaction with Magistrate Judge Peck’s ruling is not enough to succeed here…A disinterested observer fully informed of the facts in this case would find no basis for recusal”.

Since it has been a while, let’s recap the case for those who may have not been following it and may be new to the blog.

Back in February, Judge Peck issued an opinion making this case likely the first case to accept the use of computer-assisted review of electronically stored information (“ESI”) for this case.  However, on March 13, District Court Judge Andrew L. Carter, Jr. granted the plaintiffs’ request to submit additional briefing on their February 22 objections to the ruling.  In that briefing (filed on March 26), the plaintiffs claimed that the protocol approved for predictive coding “risks failing to capture a staggering 65% of the relevant documents in this case” and questioned Judge Peck’s relationship with defense counsel and with the selected vendor for the case, Recommind.

Then, on April 5, Judge Peck issued an order in response to Plaintiffs’ letter requesting his recusal, directing plaintiffs to indicate whether they would file a formal motion for recusal or ask the Court to consider the letter as the motion.  On April 13, (Friday the 13th, that is), the plaintiffs did just that, by formally requesting the recusal of Judge Peck (the defendants issued a response in opposition on April 30).  But, on April 25, Judge Carter issued an opinion and order in the case, upholding Judge Peck’s opinion approving computer-assisted review.

Not done, the plaintiffs filed an objection on May 9 to Judge Peck’s rejection of their request to stay discovery pending the resolution of outstanding motions and objections (including the recusal motion, which has yet to be ruled on.  Then, on May 14, Judge Peck issued a stay, stopping defendant MSLGroup’s production of electronically stored information.  Finally, on June 15, in a 56 page opinion and order, Judge Peck denied the plaintiffs’ motion for recusal, which Judge Carter has now upheld.

So, what do you think?  Will Judge Carter’s decision not to recuse Judge Peck restart the timetable for predictive coding on this case?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Defendant Claiming Not Reasonably Accessible Data Has Some ‘Splaining To Do – eDiscovery Case Law

In Murray v. Coleman, No. 08-CV-6383, 2012 U.S. Dist. (W.D.N.Y. Sept. 12, 2012), the plaintiff alleged harassment and retaliation in connection with his employment with the New York State Department of Correctional Services (DOCS). This discovery dispute arose when the plaintiff requested access to certain electronic records, alleging that the defendants withheld them.

In his motion, the plaintiff asserted that the defendants “never provided a ‘chronological e-mail history of any kind.’” In response, defense counsel “simply aver[red] that after plaintiff filed this motion to compel, he provided plaintiff with…‘the documents sought’ and, therefore, plaintiff’s motion is ‘moot.’” The plaintiff responded to the defendant’s reply, asserting that “‘virtually no electronic records [were] included’ in defendant’s discovery responses.”

Because the defense counsel’s response to the plaintiff’s motion was “terse,” New York Magistrate Judge Jonathan Feldman stated that it was “difficult . . . to determine whether defendants have in fact produced all relevant electronic records and e-mails as demanded by plaintiff.” Lacking in defense counsel’s response were “details regarding how and where electronically stored information (“ESI”) is held, what efforts were made to preserve relevant ESI, and the method used by defendants to locate, search and produce relevant ESI.”

As such, Judge Feldman “construe[d the defendants’] response as a claim that ESI, including e-mails, [were] not . . . produced because the data demanded [was] destroyed or [was] not ‘reasonably accessible’” pursuant to Rule 26(b)(2)(B) of the Federal Rules of Civil Procedure, which requires a producing party to “show that the information is not reasonably accessible because of undue burden or cost.”

Therefore, because the defendants had not sufficiently demonstrated that the ESI was not reasonably accessible, Judge Feldman ordered as follows:

“Defense counsel shall file an affidavit of a person with direct knowledge of DOCS’s document and e-mail retention system stating: (1) the document/e-mail retention policy used by DOCS currently and during the relevant time periods, (2) the dates of e-mails “reasonably accessible” for production in this litigation, (3) the back up or legacy system, if any, used by DOCS to preserve or archive e-mails that are no longer “reasonably accessible” and whether responsive documents or data may potentially be found on such back up or legacy systems, (4) whether accessing archived or back up e-mails would be unduly burdensome or costly and why, and (5) the date when a litigation hold or document preservation notice was put in place by DOCS regarding this matter and either a copy of or a description of the preservation or litigation hold utilized by DOCS.”  [emphasis added]

Judge Feldman ordered the defense to provide this affidavit within 30 days.

So, what do you think?  Was this an appropriate ruling given the situation?  Or did the defendant deserve sanctions?  Please share any comments you might have or if you’d like to know more about a particular topic.

Case Summary Source: Applied Discovery (free subscription required).  For eDiscovery news and best practices, check out the Applied Discovery Blog here.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Defendant Ordered to Retain Outside Vendor, Monetary Sanction Awarded – eDiscovery Case Law

In Carrillo v. Schneider Logistics, Inc. (C.D. Cal. Oct. 5, 2012), California Magistrate Judge David Bristow ordered the defendant to “retain, at its expense, an outside vendor, to be jointly selected by the parties, to collect electronically stored information and email correspondence”.  The defendant was ordered to produce all surveillance videotapes responsive to plaintiffs’ discovery requests and monetary sanctions were awarded for plaintiff’s attorney fees and costs incurred as a result of the defendant’s discovery violations.

Sequence of Events of Defendant’s Discovery Failures

In this class action wage and hour case against the defendants (a Wal-Mart provider), the plaintiffs filed a Motion to Compel responses to the first set of requests for production of documents.  Here’s a sequence of events that led to the filing of the motion (all dates in 2012):

  • On February 1, plaintiffs propounded their First Set of Requests for Production of Documents to the defendant;
  • The defendant provided its initial responses on March 12 and supplemental responses on April 4;
  • The plaintiffs, believing that the defendant’s document production was incomplete, began a series of meet and confers with the defendant, and expressed concern that the defendant had not produced all responsive non-privileged documents;
  • On May 31, the plaintiffs filed a Motion to Compel regarding the defendant’s failure to produce documents relating to Wal-Mart and their alleged failure to conduct a proper search and produce responsive documents;
  • After the Court ordered the parties to further meet and confer, the parties resolved their dispute and submitted a proposed order, which resulted in the Court ordering the defendant to supplement its responses to the requests for production of documents and produce responsive documents, including those relating to Wal-Mart. The defendant was also ordered to produce a custodian of records and person most knowledgeable regarding Schneider’s document retention policies;
  • Following the Court’s Order, the defendant produced an additional 23,000 documents, many of which related to categories of documents the defendant previously claimed did not exist;
  • The defendant also designated two employees to address the defendant’s retention policies and its efforts to search for responsive documents. When these witnesses appeared for their depositions, however, they were unable to answer many basic questions regarding the defendant’s document retention policies and the defendant’s search for responsive documents;
  • On July 10, the plaintiffs deposed an area manager for the defendant who testified that she had deleted various emails, including reports, continued to delete documents up to the date of her deposition, and that she had never received an instruction advising her not to delete such emails;

This led the plaintiffs to file their Motion to Compel on August 23, as they identified a “substantial number of emails and surveillance videotapes which had not been produced”.

Judge Bristow’s Ruling

Noting that the “record reflects – at best – a haphazard search for records”, Judge Bristow stated that the defendant had “disregarded its obligation to conduct a reasonably diligent search for responsive documents, including, as explained below, electronically stored information.”  Noting that at least 20 employees of the defendant regularly used “@wal-mart.com” email accounts for conducting business, the judge also noted that the defendant had still not produced any emails from those accounts and discounted the defendant’s contention that it had “no control” over those documents since the defendant’s employees used the Wal-Mart email address as their primary work email account.  The judge also ruled that the defendant had withheld surveillance videotapes and that it had not taken adequate steps to preserve documents.

As a result, the defendant was ordered to retain an outside vendor to collect ESI and email correspondence within 45 days and produce all responsive videotapes within 10 days.  The plaintiff was given 11 days to file a brief detailing their claim for attorneys’ fees and costs, with the defendant having two weeks to respond regarding the reasonableness of the stated costs.  Judge Bristow did deny the plaintiff’s request for other sanctions without prejudice as “premature”.

So, what do you think?  Have you seen other cases where parties were ordered to retain an outside vendor?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.