Close
Enter your
text here

Evidence

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.

Email Metadata Leads to Petraeus Resignation – eDiscovery Trends

As reported on by Megan Garber of The Atlantic, email location data led FBI investigators to discover CIA director David Petraeus’ affair with Paula Broadwell that led to his resignation.  The irony is that FBI investigators weren’t aware of, or looking for, information regarding the affair.  Here’s what happened, according to the article.

“Sometime in May, The New York Times reports, Broadwell apparently began sending emails to Jill Kelley, the Petraeus acquaintance (her precise connection to the family isn’t yet fully clear) — and those emails were “harassing,” according to Kelley. The messages were apparently sent from an anonymous (or, at least, pseudonymous) account. Kelley reported those emails to the FBI, which launched an investigation — not into Petraeus, but into the harassing emails.”

“From there, the dominoes began to fall. And they were helped along by the rich data that email providers include in every message they send and deliver — even on behalf of its pseudonymous users. Using the ‘metadata footprints left by the emails,’ the Wall Street Journal reports, ‘FBI agents were able to determine what locations they were sent from. They matched the places, including hotels, where Ms. Broadwell was during the times the emails were sent.’ From there, ‘FBI agents and federal prosecutors used the information as probable cause to seek a warrant to monitor Ms. Broadwell’s email accounts.’”

Once the investigators received that warrant, they “learned that Ms. Broadwell and Mr. Petraeus had set up private Gmail accounts to use for their communications, which included explicit details of a sexual nature, according to U.S. officials. But because Mr. Petraeus used a pseudonym, agents doing the monitoring didn’t immediately uncover that he was the one communicating with Ms. Broadwell.”

Ultimately, monitoring of Ms. Broadwell’s emails identified the link to Mr. Petraeus and the investigation escalated, despite the fact that the investigators “never monitored Mr. Petraeus’s email accounts”.

Needless to say, if the Director of the CIA can be tripped up by email metadata from an account other than his own, it could happen to anyone.  It certainly gives you an idea of the type of information that is discoverable not just from opposing parties, but third parties as well.

So, what do you think?  Have you ever identified additional sources of data through discovery of email metadata?  Please share any comments you might have or if you’d like to know more about a particular topic.

Thanks to Perry Segal’s e-Discovery Insights blog for the tip on this story!

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.

Cloning of Computer Files: When There’s a Will, There’s a Way – eDiscovery Case Law

In Matter of Tilimbo, No. 329/M-2007, 2012 N.Y. Misc. (Surr. Ct., Bronx Cnty. Aug. 22, 2012), a court held it was permissible to order cloning of computer files where doing so did not place an unreasonable burden on a nonparty, appropriate steps were taken to protect any privileged information, and the nonparty had not previously produced the requested information in hard copy.

In this claim based on a will contest, the plaintiffs moved for an order permitting their computer forensic expert to examine the personal computer hard drive of a nonparty witness, the deceased’s attorney Patrick Wynne, limited to finding and reviewing documents related to Rose Tilimbo, her will, as well as a deed transfer from her to Salvatore Tilimbo that formed the basis of the will contest. Wynne objected on the basis that he had already, at the court’s direction, been deposed on the subject and “provided an affirmation stating that he conducted the requisite diligent search of his ‘computer files and any other [additional] relevant files’ and did not find responsive documents or computer files.” He argued that “a balancing of the sanctity of the attorney-client privilege against the scope of permissible discovery warrant[ed] the denial of the motion.”

Noting that ESI of a nonparty is discoverable, the court held that so long as it did not place an unreasonable burden on Wynne, a solo practitioner, the examination and cloning of Wynne’s computer was permissible. Although Wynne had produced in hard copy all of the documents he said he possessed, the court pointed out that such disclosures did not prevent the ESI itself from being sought. In addition, Wynne had not been able to produce any documents related to the deed transfer at issue, and any such documents that existed would clearly be material and relevant to the case. Therefore, the court offered the following parameters for the cloning:

“The court finds that the cloning would not place an unreasonable burden upon Wynne if all of the computers can be cloned at his office in four hours or less on a date and at a time that he selects, which may include in whole or in part a time after normal business hours. Alternatively, the cloning will be allowed outside of Wynne’s office if it can be done by removing the computer(s) on a Saturday at any time selected by Wynne and returned to his office by Monday between 8:30 and 9:00 a.m. If Wynne prefers, the computer(s) may be removed from his office on any other day, provided the computer(s) are returned to his office within 24 hours. If the cloning is to be done outside of Wynne’s office and more than one computer is to be cloned, then at Wynne’s option, only one computer may be removed from his office at a time. In the event that the cloning can be accomplished within the time allocated herein either at Wynne’s office or by removal of the computer(s), Wynne shall have the right to select whether or not he wants the cloning to be done at his office. In the event that the cloning requested by the movants cannot be performed within the time frame provided herein, the court finds that the disruption to Wynn’s practice of law outweighs the benefits that the movants might obtain from the information provided by the cloning. Furthermore, should a computer be removed from Wynne’s office and not returned within the time provided herein, the movants shall pay Wynne $200 for each hour or part thereof that the return is delayed.”

In addition, the forensic analysts were limited to locating documents likely to lead to discoverable evidence related to the decedent and were given specific instructions on what to do with any unrelated documents that were accidentally uncovered.

So, what do you think?  Should cloning of the computer have been allowed?  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.

eDiscovery Daily is Two Years Old Today!
 

It’s hard to believe that it has been two years ago today since we launched the eDiscoveryDaily blog.  Now that we’ve hit the “terrible twos”, is the blog going to start going off on rants about various eDiscovery topics, like Will McAvoy in The Newsroom?   Maybe.  Or maybe not.  Wouldn’t that be fun!

As we noted when recently acknowledging our 500th post, we have seen traffic on our site (from our first three months of existence to our most recent three months) grow an amazing 442%!  Our subscriber base has nearly doubled in the last year alone!  We now have nearly seven times the visitors to the site as we did when we first started.  We continue to appreciate the interest you’ve shown in the topics and will do our best to continue to provide interesting and useful eDiscovery news and analysis.  That’s what this blog is all about.  And, in each post, we like to ask for you to “please share any comments you might have or if you’d like to know more about a particular topic”, so we encourage you to do so to make this blog even more useful.

We also want to thank the blogs and publications that have linked to our posts and raised our public awareness, including Pinhawk, The Electronic Discovery Reading Room, Unfiltered Orange, Litigation Support Blog.com, Litigation Support Technology & News, Ride the Lightning, InfoGovernance Engagement Area, Learn About E-Discovery, Alltop, Law.com, Justia Blawg Search, Atkinson-Baker (depo.com), ABA Journal, Complex Discovery, Next Generation eDiscovery Law & Tech Blog and any other publication that has picked up at least one of our posts for reference (sorry if I missed any!).  We really appreciate it!

We like to take a look back every six months at some of the important stories and topics during that time.  So, here are some posts over the last six months you may have missed.  Enjoy!

We talked about best practices for issuing litigation holds and how issuing the litigation hold is just the beginning.

By the way, did you know that if you deleted a photo on Facebook three years ago, it may still be online?

We discussed states (Delaware, Pennsylvania and Florida) that have implemented new rules for eDiscovery in the past few months.

We talked about how to achieve success as a non-attorney in a law firm, providing quality eDiscovery services to your internal “clients” and how to be an eDiscovery consultant, and not just an order taker, for your clients.

We warned you that stop words can stop your searches from being effective, talked about how important it is to test your searches before the meet and confer and discussed the importance of the first 7 to 10 days once litigation hits in addressing eDiscovery issues.

We told you that, sometimes, you may need to collect from custodians that aren’t there, differentiated between quality assurance and quality control and discussed the importance of making sure that file counts add up to what was collected (with an example, no less).

By the way, did you know the number of pages in a gigabyte can vary widely and the same exact content in different file formats can vary by as much as 16 to 20 times in size?

We provided a book review on Zubulake’s e-Discovery and then interviewed the author, Laura Zubulake, as well.

BTW, eDiscovery Daily has had 150 posts related to eDiscovery Case Law since the blog began.  Fifty of them have been in the last six months.

P.S. – We still haven't missed a business day yet without a post.  Yes, we are crazy.

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.

eDiscovery Case Law: Social Media Is No Different than eMail for Discovery Purposes
 

In Robinson v. Jones Lang LaSalle Americas, Inc., No. 3:12-cv-00127-PK (D. Or. Aug. 29, 2012), Oregon Magistrate Judge Paul Papak found that social media is just another form of electronically stored information (ESI), stating “I see no principled reason to articulate different standards for the discoverability of communications through email, text message, or social media platforms. I therefore fashion a single order covering all these communications.”

In this employment discrimination case, the defendants sought discovery from the plaintiff, including “all of Robinson's email and text message communications with current and former Jones Lang employees” and, most notably “all social media content involving Robinson since July 1, 2008, including photographs, videos, and blogs, as well as Facebook, linkedIn, and MySpace content that reveals or relates to Robinson's. "emotion, feeling, or mental state," to "events that could be reasonably expected to produce a significant emotion, feeling, or mental state," or to allegations in Robinson's complaint”.

In rendering his decision, Judge Papak referenced “[t]he most frequently cited and well-reasoned case addressing the discoverability of social media communications involving emotional distress” (E.E. O. C. v. Simply Storage Mgmt., LLC, 270 F.R.D. 430, 432 (S.D. Ind. 2010)).  In that case, Judge Papak noted that “the court recognized that social media can provide information inconsistent with a plaintiffs allegation that defendant's conduct caused her emotional distress, whether by revealing alternate sources of that emotional distress or undermining plaintiff s allegations of the severity of that distress.”

With the principles of the Simply Storage case in mind, Judge Papak ordered the plaintiff to produce:

“(I) any:

(a) email or text messages that plaintiff sent to, received from, or exchanged with any current and former employee of defendant, as well as messages forwarding such messages; or

(b) online social media communications by plaintiff, including profiles, postings, messages, status updates, wall comments, causes joined, groups joined, activity streams, applications, blog entries, photographs, or media clips, as well as third-party online social media communications that place plaintiff's own communications in context;

(2) from July 1, 2008 to the present;

(3) that reveal, refer, or relate to:

(a) any significant emotion, feeling, or mental state allegedly caused by defendant's conduct; or

(b) events or communications that could reasonably be expected to produce a significant emotion, feeling, or mental state allegedly caused by defendant's conduct.”

Understanding the difficulty of establishing an appropriate level of discovery, Judge Papak stated “As Simply Storage recognized, it is impossible for the court to define the limits of discover in such cases with enough precision to satisfy the litigant who is called upon to make a responsive production…Nevertheless, the court expects counsel to determine what information falls within the scope of this court's order in good faith and consistent with their obligations as officers of the court. Defendant may, of course, inquire about what "has and has not been produced and can challenge the production if it believes the production falls short of the requirements of this order."…Moreover, the parties may ask the court to revise this order in the future based on the results of plaintiffs deposition or other discovery.”

So, what do you think?  Should all media be handled the same in discovery, or should there be differences?  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.

eDiscovery Case Law: More Sanctions for Fry’s Electronics
 

In E.E.O.C. v Fry’s Electronics, Inc., No. C10-1562RSL, 2012 U.S. Dist. (W.D. Wash. July 3, 2012), Washington District Judge Robert S. Lasnik ordered several sanctions against the defendant in this sexual harassment case (including ordering the defendant to pay $100,000 in monetary sanctions and ordering that certain evidence be considered presumptively admissible at trial), but stopped short of entering a default judgment against the defendant.  This ruling came after having previously ordered sanctions against the defendant less than two months earlier.

Prior Sanctions

On May 10, Judge Lasnik granted in part plaintiffs' motion for sanctions in this case, finding that the defendant had spoliated evidence, including data and computer hard drives. In that ruling, Judge Lasnik believed that the prejudicial effect of the spoliation could be counteracted by “(a) instructing the jury that one of the justifications for firing [one of the plaintiffs] was pretextual and (b) allowing plaintiff considerable leeway in arguing what information might have been gleaned from the computer hard drives had they not been destroyed by defendant”. At the time, Judge Lasnik also indicated “some concern regarding the efficacy and thoroughness of defendant's searches” which led to more information being discovered after he ordered a second search.

Additional Spoliation and Misconduct

During a Rule 30(b)(6) deposition held on May 30, the plaintiffs learned for the first time that the accused individual had previously been accused of sexual harassment in 2001 and that an investigation had been conducted. According to Judge Lasnik, the defendant “intentionally withheld this information and the related documents from discovery by raising unfounded objections and ‘negotiating’ a narrowing of the discovery requests” and found the defendant's conduct to be “unfair, unwarranted, unprincipled, and unacceptable”.

Misconduct by the defendants noted by Judge Lasnik also included the redaction of responsive information, “[e]ven after defendant's objections to certain discovery requests were overruled”, as well as production of hundreds of pages of information with the “fallacious argument” that they were relevant to the claims.

Consideration of Default Judgment Sanction

Judge Lasnik noted that it is “once again left to determine whether to strike defendant's answer and enter default judgment against it”, but noted that dismissal is a “harsh sanction” and the following factors must be considered when determining “whether a dispositive sanction is appropriate under either its inherent powers or Rule 37(b): (1) the public's interest in the expeditious resolution of litigation; (2) the Court's need to manage its docket efficiently and effectively; (3) the risk of prejudice to the party seeking sanctions; (4) the public policy in favor of considering cases on the merits; and (5) the availability of less drastic sanctions.”  While finding that the first three factors supported a dispositive sanction, Judge Lasnik ruled against a dispositive sanction in factor 4, indicating that “[t]he public has an interest in a determination of those issues based on the facts, rather than by judicial fiat”.

Lesser Sanctions Ordered

Instead, Judge Lasnik ordered lesser sanctions, indicating that “Defendant's affirmative defenses related to (i) its efforts to prevent and correct harassment in the workplace, (ii) plaintiffs' failure to utilize protective and corrective opportunities provided by defendant, (iii) its good faith and/or privilege to act as it did in this case are STRICKEN.” He also stated that certain documents and testimony related to “other complaints or reports of sexual harassment” at the company were “presumptively admissible at trial”. He also ordered sanctions of $100,000 “to offset the excess costs caused by defendant’s discovery violations, to punish unacceptable behavior, and as a deterrent to future bad conduct” to be split evenly between the two individual plaintiffs, the EEOC and the Court Clerk.

So, what do you think?  Are you surprised that the defendant didn’t receive a default judgment sanction?  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.

eDiscovery History: Zubulake’s e-Discovery
 

In the 22 months since this blog began, we have published 133 posts related to eDiscovery case law.  When discussing the various case opinions that involve decisions regarding to eDiscovery, it’s easy to forget that there are real people impacted by these cases and that the story of each case goes beyond just whether they preserved, collected, reviewed and produced electronically stored information (ESI) correctly.  A new book, by the plaintiff in the most famous eDiscovery case ever, provides the “backstory” that goes beyond the precedent-setting opinions of the case, detailing her experiences through the events leading up to the case, as well as over three years of litigation.

Laura A. Zubulake, the plaintiff in the Zubulake vs. UBS Warburg case, has written a new book: Zubulake's e-Discovery: The Untold Story of my Quest for Justice.  It is the story of the Zubulake case – which resulted in one of the largest jury awards in the US for a single plaintiff in an employment discrimination case – as told by the author, in her words.  As Zubulake notes in the Preface, the book “is written from the plaintiff’s perspective – my perspective. I am a businessperson, not an attorney. The version of events and opinions expressed are portrayed by me from facts and circumstances as I perceived them.”  It’s a “classic David versus Goliath story” describing her multi-year struggle against her former employer – a multi-national financial giant.

Zubulake begins the story by developing an understanding of the Wall Street setting of her employer within which she worked for over twenty years and the growing importance of email in communications within that work environment.  It continues through a timeline of the allegations and the evidence that supported those allegations leading up to her filing of a discrimination claim with the Equal Employment Opportunity Commission (EEOC) and her subsequent dismissal from the firm.  This Allegations & Evidence chapter is particularly enlightening to those who may be familiar with the landmark opinions but not the underlying evidence and how that evidence to prove her case came together through the various productions (including the court-ordered productions from backup tapes).  The story continues through the filing of the case and the beginning of the discovery process and proceeds through the events leading up to each of the landmark opinions (with a separate chapter devoted each to Zubulake I, III, IV and V), then subsequently through trial, the jury verdict and the final resolution of the case.

Throughout the book, Zubulake relays her experiences, successes, mistakes, thought processes and feelings during the events and the difficulties and isolation of being an individual plaintiff in a three-year litigation process.  She also weighs in on the significance of each of the opinions, including one ruling by Judge Shira Scheindlin that may not have had as much impact on the outcome as you might think.  For those familiar with the opinions, the book provides the “backstory” that puts the opinions into perspective; for those not familiar with them, it’s a comprehensive account of an individual who fought for her rights against a large corporation and won.  Everybody loves a good “David versus Goliath story”, right?

The book is available at Amazon and also at CreateSpace.  Look for my interview with Laura regarding the book in this blog next week.

So, what do you think?  Are you familiar with the Zubulake opinions?  Have you read the book?  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.

eDiscovery Case Law: Judge Scheindlin Says “No” to Self-Collection, “Yes” to Predictive Coding
 

When most people think of the horrors of Friday the 13th, they think of Jason Voorhees.  When US Immigration and Customs thinks of Friday the 13th horrors, do they think of Judge Shira Scheindlin?

As noted in Law Technology News (Judge Scheindlin Issues Strong Opinion on Custodian Self-Collection, written by Ralph Losey, a previous thought leader interviewee on this blog), New York District Judge Scheindlin issued a decision last Friday (July 13) addressing the adequacy of searching and self-collection by government entity custodians in response to Freedom of Information Act (FOIA) requests.  As Losey notes, this is her fifth decision in National Day Laborer Organizing Network et al. v. United States Immigration and Customs Enforcement Agency, et al., including one that was later withdrawn.

Regarding the defendant’s question as to “why custodians could not be trusted to run effective searches of their own files, a skill that most office workers employ on a daily basis” (i.e., self-collect), Judge Scheindlin responded as follows:

“There are two answers to defendants' question. First, custodians cannot 'be trusted to run effective searches,' without providing a detailed description of those searches, because FOIA places a burden on defendants to establish that they have conducted adequate searches; FOIA permits agencies to do so by submitting affidavits that 'contain reasonable specificity of detail rather than merely conclusory statements.' Defendants' counsel recognize that, for over twenty years, courts have required that these affidavits 'set [ ] forth the search terms and the type of search performed.' But, somehow, DHS, ICE, and the FBI have not gotten the message. So it bears repetition: the government will not be able to establish the adequacy of its FOIA searches if it does not record and report the search terms that it used, how it combined them, and whether it searched the full text of documents.”

“The second answer to defendants' question has emerged from scholarship and caselaw only in recent years: most custodians cannot be 'trusted' to run effective searches because designing legally sufficient electronic searches in the discovery or FOIA contexts is not part of their daily responsibilities. Searching for an answer on Google (or Westlaw or Lexis) is very different from searching for all responsive documents in the FOIA or e-discovery context.”

“Simple keyword searching is often not enough: 'Even in the simplest case requiring a search of on-line e-mail, there is no guarantee that using keywords will always prove sufficient.' There is increasingly strong evidence that '[k]eyword search[ing] is not nearly as effective at identifying relevant information as many lawyers would like to believe.' As Judge Andrew Peck — one of this Court's experts in e-discovery — recently put it: 'In too many cases, however, the way lawyers choose keywords is the equivalent of the child's game of 'Go Fish' … keyword searches usually are not very effective.'”

Regarding search best practices and predictive coding, Judge Scheindlin noted:

“There are emerging best practices for dealing with these shortcomings and they are explained in detail elsewhere. There is a 'need for careful thought, quality control, testing, and cooperation with opposing counsel in designing search terms or keywords to be used to produce emails or other electronically stored information.' And beyond the use of keyword search, parties can (and frequently should) rely on latent semantic indexing, statistical probability models, and machine learning tools to find responsive documents.”

“Through iterative learning, these methods (known as 'computer-assisted' or 'predictive' coding) allow humans to teach computers what documents are and are not responsive to a particular FOIA or discovery request and they can significantly increase the effectiveness and efficiency of searches. In short, a review of the literature makes it abundantly clear that a court cannot simply trust the defendant agencies' unsupported assertions that their lay custodians have designed and conducted a reasonable search.”

Losey notes that “A classic analogy is that self-collection is equivalent to the fox guarding the hen house. With her latest opinion, Schiendlin [sic] includes the FBI and other agencies as foxes not to be trusted when it comes to searching their own email.”

So, what do you think?  Will this become another landmark decision by Judge Scheindlin?  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.

eDiscovery Trends: First Pass Review – Domain Categorization of Your Opponent’s Data
 

Even those of us at eDiscoveryDaily have to take an occasional vacation; however, instead of “going dark” for the week, we thought we would republish a post series from the early days of the blog (when we didn’t have many readers yet)  So chances are, you haven’t seen these posts yet!  Enjoy!

Yesterday, we talked about the use of First Pass Review (FPR) applications (such as FirstPass®, powered by Venio FPR™) to not only conduct first pass review of your own collection, but also to analyze your opponent’s ESI production.  One way to analyze that data is through “fuzzy” searching to find misspellings or OCR errors in an opponent’s produced ESI.

Domain Categorization

Another type of analysis is the use of domain categorization.  Email is generally the biggest component of most ESI collections and each participant in an email communication belongs to a domain associated with the email server that manages their email.

FirstPass supports domain categorization by providing a list of domains associated with the ESI collection being reviewed, with a count for each domain that appears in emails in the collection.  Domain categorization provides several benefits when reviewing your opponent’s ESI:

  • Non-Responsive Produced ESI: Domains in the list that are obviously non-responsive to the case can be quickly identified and all messages associated with those domains can be “group-tagged” as non-responsive.  If a significant percentage of files are identified as non-responsive, that may be a sign that your opponent is trying to “bury you with paper” (albeit electronic).
  • Inadvertent Disclosures: If there are any emails associated with outside counsel’s domain, they could be inadvertent disclosures of attorney work product or attorney-client privileged communications.  If so, you can then address those according to the agreed-upon process for handling inadvertent disclosures and clawback of same.
  • Issue Identification: Messages associated with certain parties might be related to specific issues (e.g., an alleged design flaw of a specific subcontractor’s product), so domain categorization can isolate those messages more quickly.

In summary, there are several ways to use first pass review tools, like FirstPass, for reviewing your opponent’s ESI production, including: email analytics, synonym searching, fuzzy searching and domain categorization.  First pass review isn’t just for your own production; it’s also an effective process to quickly evaluate your opponent’s production.

So, what do you think?  Have you used first pass review tools to assess an opponent’s produced ESI?  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.

eDiscovery Trends: First Pass Review – Fuzzy Searching Your Opponent’s Data
 

Even those of us at eDiscoveryDaily have to take an occasional vacation; however, instead of “going dark” for the week, we thought we would republish a post series from the early days of the blog (when we didn’t have many readers yet)  So chances are, you haven’t seen these posts yet!  Enjoy!

Tuesday, we talked about the use of First Pass Review (FPR) applications (such as FirstPass®, powered by Venio FPR™) to not only conduct first pass review of your own collection, but also to analyze your opponent’s ESI production.  One way to analyze that data is through synonym searching to find variations of your search terms to increase the possibility of finding the terminology used by your opponents.

Fuzzy Searching

Another type of analysis is the use of fuzzy searching.  Attorneys know what terms they’re looking for, but those terms may not often be spelled correctly.  Also, opposing counsel may produce a number of image only files that require Optical Character Recognition (OCR), which is usually not 100% accurate.

FirstPass supports "fuzzy" searching, which is a mechanism by finding alternate words that are close in spelling to the word you're looking for (usually one or two characters off).  FirstPass will display all of the words – in the collection – close to the word you’re looking for, so if you’re looking for the term “petroleum”, you can find variations such as “peroleum”, “petoleum” or even “petroleom” – misspellings or OCR errors that could be relevant.  Then, simply select the variations you wish to include in the search.  Fuzzy searching is the best way to broaden your search to include potential misspellings and OCR errors and FirstPass provides a terrific capability to select those variations to review additional potential “hits” in your collection.

Tomorrow, I’ll talk about the use of domain categorization to quickly identify potential inadvertent disclosures and weed out non-responsive files produced by your opponent, based on the domain of the communicators.  Hasta la vista, baby! J

In the meantime, what do you think?  Have you used fuzzy searching to find misspellings or OCR errors in an opponent’s produced ESI?  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.