Welcome to the new eLessons Learned

eDiscovery Written by Law Students

eDiscovery Written by Law Students

eLessons Learned features insightful content authored primarily by law students from throughout the country. The posts are written to appeal to a broad spectrum of readers, including those with little eDiscovery knowledge.

Law + Technology + Human Error

Law + Technology + Human Error

Each blog post: (a) identifies cases that address technology mishaps; (b) exposes the specific conduct that caused a problem; (c) explains how and why the conduct was improper; and (d) offers suggestions on how to learn from these mistakes and prevent similar ones from reoccurring.

New to the eDiscovery world?

New to the eDiscovery world?

Visit our signature feature, e-Discovery Origins: Zubulake, designed to give readers a primer on the e-discovery movement through blog posts about the Zubulake series of court opinions which helped form the foundation for e-discovery. Go There

Contribute to eLessons Learned

Contribute to eLessons Learned

Interested students may apply for the opportunity to write for e-Lessons Learned by filling out the simple application. Go There

How Can You Check if Your Insurance Customer is Faking an Injury? Get Evidence Before Requesting Access to Their Social Media!

A growing trend in insurance disputes is a demand for insurers to have access to the claimant’s social media content.  In January 2013, the District of Montana had to consider whether to compel a woman to produce all of her social media photos.  The court did not grant this request and the decision serves as a good example of what is, or is not, an effective way to request this information. In Keller, one of the plaintiffs claimed she injured her head, neck, and back in an automobile accident when the vehicle she was driving was struck from behind. Her mother also suffered injuries in the accident.  At the time of the accident, they were insured under an automobile liability policy issued by the defendant. The plaintiffs made a claim for uninsured motorist benefits under the policy. The defendant, under Federal Rule 37, moved for an order compelling the plaintiffs to respond to discovery requests for the production of their social network site content.  The defendant’s rationale for the request was the plaintiffs alleged a “host of physical and emotional injuries.”  In respect to the mother, the defendant argued “there is no good reason for her to shield information that might shed light on her or her daughter's injuries.”  This is the language of the request: Request for Production No. 18: Please produce a full printout of all of Plaintiff [driver]’s social media website pages and all photographs posted thereon including, but not limited to, Facebook, Myspace, Twitter, LinkedIn, LiveJournal, Tagged, Meetup, myLife, Instagram and MeetMe from August 26, 2008 to the present. Request for Production No. 19: Please produce a full printout of all of Plaintiff’s [mother's] social media website pages and all photographs posted thereon including, but not limited to, Facebook, Myspace, Twitter, LinkedIn, LiveJournal, Tagged, Meetup, myLife, Instagram and MeetMe from August 26, 2008 to the present. As you can imagine, the court felt these requests were overbroad.  It is well settled that social media content is discoverable, but the requestor must make a threshold showing that publicly available information on those sites undermines the plaintiff’s claims.  The defendant did not come forward with any evidence that the content of either of the plaintiffs’ public postings in any way undermined their claims in this case. Absent such a showing, the defendant was not entitled to delve carte blanche into the nonpublic sections of the laintiffs' social networking accounts, let alone all of them. This case should serve as a lesson to other insurance litigants.  You should only request access to social media accounts if you can make a threshold showing that the social media content will be relevant and hold admissible evidence.  Otherwise you will rightly be admonished for undergoing a “fishing expedition” and your requests will be promptly denied.

Federal Judge Sanctions Corporate Defendant and Its Counsel for Gross Negligence, Bad Faith, and Failure to Comply With Discovery Requests and Court Order

In Brown v. Tellermate Holdings Ltd., Tellermate Holdings, the defendant company, terminated two employees for allegedly failing to meet sales targets over several years.  The employees, feeling that they were wrongfully terminated due to their age, filed an employment discrimination action against the company as well as other entities and individuals associated with Tellermate. Throughout pre-trial proceedings, the case was plagued with numerous discovery mishaps.  The plaintiffs requested from the defendant company data stored and maintained by Salesforce.com,[1] which would, in theory, evidence plaintiffs’ sales records over the last few years in addition to allowing the plaintiffs to compare their sales figures with other (younger) employees.  However, even though numerous discovery conferences were held, numerous discovery motions filed with the court, and several discovery orders issued by the court, the defendant corporation failed to produce the requested data and documents.  Ultimately, the plaintiffs filed for judgment and sanctions under Federal Rule 37(b)(2); the court held a three-day evidentiary hearing on the matter. The presiding judge, United States Magistrate Judge Terence P. Kemp, identified three areas in which the defendant company or its counsel failed in its obligations to the plaintiffs and the court in relation to production of documents and data: Defendant’s counsel failed to understand how Tellermate’s data stored with Salesforce.com could be obtained and produced to plaintiffs, which resulted in counsel making false statements to the plaintiffs’ counsel and the court; By failing to understand how the defendant’s data was stored and maintained, defendant’s counsel took no steps to preserve the integrity of the information in Tellermate’s database located with Salesforce.com; Defendant’s counsel failed to learn of the existence of documents relating to a prior age discrimination charge until almost a year after plaintiffs requested the documents; Defendant’s counsel produced a “document dump” resulting from counsel’s use of an overly-broad keyword search that yielded around 50,000 irrelevant documents, which plaintiffs’ counsel could not review within the time period ordered by the court. The Salesforce.com Data Judge Kemp found that Tellermate’s failure to preserve and produce the data logged on Salesforce.com’s website irreparably deprived the plaintiffs of reliable information necessary in supporting their claims.  Although defendant’s counsel initially stated that Tellermate “does not maintain salesforce.com information in hard copy format,” “cannot print out accurate historical records from salesforce.com,” and that “discovery of salesforce.com information should be directed at salesforce.com, not Tellermate,” the court found such statements to be on their face false.  In fact, Tellermate did have access to the information sought by the plaintiffs as one, and sometimes two, of Tellermate's employees enjoyed the highest level of access to the Salesforce.com information.  The court determined that the information eventually produced by the defendants could not be trusted as “even a forensic computer expert has no way to detect hat changes, deletions[,] or additions were made to the database on an historical basis.”  Because of Tellermate’s failure to preserve the Salesforce.com data, Judge Kamp precluded Tellermate from providing evidence showing that the plaintiff-employees were terminated for their alleged underperformance. Counsel’s Obligations With Respect to ESI The court found that the defense’s counsel fell short of their well-established obligations[2] to critically examine the documents and data Tellermate provided to them.  Tellermate made false representations to its counsel about the data’s availability and therefore caused undue delay in document production as well as false and misleading arguments to be made to plaintiffs’ counsel and to the court.  Subsequently, the plaintiffs were forced to file discovery motions before the court to address these discovery issues which produced the Salesforce.com data that was never properly preserved albeit its significance to the plaintiffs’ case. Judge Kemp ultimately determined that counsel for the defendant conducted an inadequate investigation of Tellermate’s electronic data while simultaneously failing to understand the most basic concepts of cloud computing and cloud storage, which led to counsel’s failing to preserve key electronic data. Control of Data Stored in the Cloud As mentioned above, Tellermate and its counsel repeatedly represented to the plaintiffs and to the court that it did not possess and could not produce any of the Salesforce.com data requested by plaintiffs.  Additionally, the defendants asserted that in light of those facts, the defendants could not preserve the data stored on Salesforce.com’s databases at any point prior to litigation. Judge Kemp dismissed these claims.  The court concluded that, without any factual basis whatsoever, no substantive argument could be made that Tellermate was prohibited from accessing the information stored on the Salesforce.com databases or that Salesforce.com was responsible for preserving Tellermate’s information and data as it was the entity that maintained possession and control of the data. In reality, Tellermate was the custodian of the data stored on the Salesforce.com databases.  While information can be stored in locations outside the immediate control of the corporate entity by third party providers, it can still be under the legal control of the owner of the data and therefore must be produced by the owner under Federal Rule 34(a)(1)(A).  Additionally, had Tellermate’s counsel critically examined the agreement between Tellermate and Salesforce.com, it would have realized that Tellermate was the owner of all data created by its employees and that Tellermate could, at any time, download the data stored on the Salesforce.com databases for preservation and production purposes. Limitations on Document Production to Avoid “Document Dumps” Tellermate produced to the plaintiffs 50,000 pages of irrelevant documents, classified by Judge Kemp as a “document dump.”  Tellermate’s counsel refused to disclose which search terms it used in deciding which documents to produce to the plaintiffs, claiming that the search terms were privileged.  In actuality, the court discovered, Tellermate’s counsel only used the full names and nicknames of employees as its search terms, which obviously yielded irrelevant documents.  Without reviewing the returned documents, and because the court’s deadline for producing relevant documents was rapidly approaching, Tellermate’s counsel produced to the plaintiffs the documents as “Attorney’s Eyes Only.” The court recognized that a protective order was permitted only when counsel held a good faith belief that such information constituted a “trade secret or other confidential research, development, or proprietary business information, and that such material was entitled to a higher level of protection than otherwise provided in the protective order.”  Tellermate could not demonstrate entitlement to this level of protection with respect to the search terms used in procuring documentation for discovery: The alleged burden imposed by a high volume production does not provide the producing party or its counsel free reign to choose a given designation and ignore the Court’s order pertaining to that designation. First, the court looked to whether competitive harm would result from the disclosure of the types of documents produced by Tellermate to a competitor; however, Tellermate’s memorandum on the issue did not contain any evidence about the harm which might result if the plaintiffs were permitted to review any particular document that was labeled “Attorney’s Eyes Only.” Second, Tellermate’s argument as to the harm it would experience was entirely conclusory and was not supported by evidence: Apart from the general concept that disclosure of some types of sensitive information to a competitor may result in harm, it contains no particularized argument which is specific to [the plaintiff], the way in which he was competing with Tellermate, and how the disclosure of any one of the 50,000 pages marked as attorneys-eyes-only would harm Tellermate’s interests. The court was astounded that Tellermate continually failed to meet the burden required to designate the documents as “Attorney’s Eyes Only” and, up until the hearing date, made no effort the redesignate a single page of the 50,000 produced in order to permit the plaintiffs from viewing the documents. Sanctions The court had absolutely no qualms with an award of attorneys’ fees for all motion practice connected to the preservation and production of the Salesforce.com data.  “Had Tellermate and its counsel simply fulfilled their basic discovery obligations, neither of these matters would have come before the Court, or at least not in the posture they did.”  The court took great concern to the extraordinary lengths the plaintiffs had to go to in order to obtain the documents maintained by the defendant and, even after several rounds of motions, were not able to obtain all of them.  The “Attorney’s Eyes Only” designation on the 50,000 documents produced was also unfounded, the court held, and unduly precluded plaintiffs from necessary evidence that supported their case, which warranted fees under Federal Rule 37(a)(5)(A). Conclusion Tellermate provides a warning to all attorneys that the realm of technology in which their clients are constantly interact with is always changing.  Therefore, so does the practice of electronic discovery.  Counsel must always meet its duties with respect to ESI by engaging in discussions with its clients and opposing counsel about ESI; being aware, and perhaps even knowledgeable, of new and emerging technologies; and investigating and assessing with its clients the sources and status of potentially relevant ESI.  By forgoing these practices, counsel opens itself and its clients to easily avoided and costly sanctions. Daniel is the Editor-in-Chief of eLessions Learned and a third-year law student at Duquesne University.  To read more about him, click here. [1]       Salesforce.com is a cloud-based customer relationship management system with more than 100,000 corporate customers around the world.  Tellermate and its employees used Salesforce.com to track their sales and other interaction with customers.  The court recognized that each sales person using the Salesforce.com management system could add, remove, or otherwise change data on their sales account. [2]       See Zubulake v. UBS Warburg LLC, 382 F.Supp.2d 536 (S.D.N.Y. 2005) (counsel had an affirmative duty to monitor preservation an d ensure all sources of discovery information were identified).

You Might Want to Rethink Your Next Fishing Expedition in Tennessee

The scope of discovery, as stated in Federal Rule 26, has been construed very broadly in its relevancy standard.  Any and all requesting parties can seek production of documents and information as long as “the discovery appears reasonably calculated to lead to the discovery of admissible evidence.”  And while this standard has the tendency of having the producing parties provide all requested, non-privileged documents within their control, some courts have determined there are exceptions. In Potts v. Dollar Tree Stores, Inc., the Middle District of Tennessee determined that requests for private Facebook pages require the rquesting party must meet a threshold showing that the information sought is likely to be found on the social media site and lead to admissible evidence. In Potts, the plaintiff filed suit against her former employer, Dollar Tree Stores, Inc., claiming harassment and discrimination based on the plaintiff’s race, a hostile work environment, and retaliation.  After discovery disputes, the defendant filed a motion to compel claiming that the plaintiff did not produce a number of requested items and documents, including: Facebook data, any and all computer and storage devices used during and after the plaintiff’s employment, tax returns, any relevant documents in online email accounts, as well as other items.  The plaintiff’s response to the defendant’s request asserted that she produced what documents were in her possession, that the defendant’s request for the physical production of her computer was unduly burdensome, and that the defendant is not entitled to access to her private Facebook account due to other court holdings requiring a threshold showing that the Facebook page would undermine the producing party’s claim(s). Since, the Sixth Circuit Court of Appeals had not yet ruled on requesting parties’ access to private Facebook pages, the Middle District of Tennessee relied on outside court rulings in Thompkins v. Detroit Metro. Airport, 278 F.R.D. 387, 388 (E.D. Mich. 2012) and McCann v. Harleysville Ins. Co. of N.Y., 910 N.Y.S.2d 614 (N.Y.App. Div. 2010).  Courts in Michigan and New York held that, while Facebook accounts are not considered privileged or necessarily protected by notions of privacy, requesting parties should not be allowed to go on fishing expeditions in hopes of finding relevant information to their case.  In resolving the issue of rummaging for information, the courts held that a requesting party seeking access to private Facebook accounts must meet a threshold showing that the social media page will likely lead to admissible evidence.  Adopting the idea of a “threshold showing,” the Potts court determined that the defendant fell short in showing that the information it gathered from the plaintiff’s public Facebook page would lead to admissible evidence if the plaintiff had given more access. The court determined that the defendant was entitled to certain documents in the defendant’s motion to compel that Plaintiff had not yet produced in discovery, but accepted the plaintiff’s assertion that she no longer had certain requested documents that would not have been relevant to the case.  When dealing with the physical production of the plaintiff’s computer, the court resolved that an agreed neutral party would search for relevant documents on the plaintiff’s computer, using both parties’ agreed-upon word search.  As for the the defendant seeking attorneys’ fees incurred in preparing the motion to compel, the court ruled that Federal Rule 26(b)(2) gives discretion to the court in relieving any undue burdens on responding parties during discovery.  The court did not require the plaintiff to pay the defendant’s attorneys’ fees due to the plaintiff having reasonable objections to the defendant’s discovery requests.

So You Want to Destroy Documents? Then Be Prepared to Be Sanctioned!

This case involves a lawsuit for patent infringement concerning memory chip technology. In 2006, the court found that SK Hynix Inc. had infringed on Rambus, Inc.’s patent. The issue presented in 2013 was in regards to the destruction of documents. The court found that Rambus had spoilated documents in bad faith that ultimately prejudiced SK Hynix. The three main factors that the court looked at in this case in making a determination about sanctions are: The degree of fault of Rambus; The degree of prejudice suffered by SK Hynix; and Whether there is a lesser sanction than dismissal that will address the prejudice to SK Hynix and will deter similar conduct in the future by Rambus and others. The degree of fault is clearly present in this case on behalf Rambus. While it was reasonably foreseeable that litigation would occur, Rambus not only destroyed large volumes of documents but they kept no records of what was destroyed. Because of this, it is impossible to know what evidence was lost and it is unknown if the documents destroyed were singled out because they were potentially damaging documents. The difficulties created as a result of Rambus’ conduct are the fault of Rambus and therefore they must suffer the consequences. While it is unclear the degree of prejudice suffered by SK Hynix, it is presumed that SK Hynix has been prejudiced in its ability to litigate its equitable claims and defenses as a result of the destruction of documents related to the Joint Electron Engineering Conference. This missing information would have been required to license its technology at a fair, reasonable, and non-discriminatory rate. To satisfy the third prong of the test, the court decided that a dismissal was not warranted in this case as the conduct by Rambus was not severe enough. While bad faith and prejudice are both present in this case, they would not justify a dismissal. The less severe sanction available would be a monetary fine. While not as severe, the fine most likely will still deter others from engaging in similar conduct in the future. Ultimately, while the court found that what Rambus did was not right, it did not feel that is was so egregious that it warranted a dismissal of the verdict and rather felt a fine was more appropriate. As a result, Rambus was fined $250 million dollars. This monetary sanction is to be applied as a credit against the previous judgment awarded. To avoid an outcome like this in the future, all parties involved in litigation should never destroy documents. Jennifer Whritenour received her B.S. in Political Science and History in 2011 from the University of Scranton. In 2014 she received her J.D. from Seton Hall University School of Law.

Is Negligent Spoliation of Evidence Sufficient to Warrant Permissive Adverse Jury Instruction?

An employer doesn’t need an attorney to tell him or her that destroying evidence relevant to litigation may make the court very unhappy.  Often times, when a party acts in bad faith by intentionally destroying evidence, the court will impose a sanction such as an “adverse inference” jury instruction.  This type of instruction orders the jury to infer that the missing evidence would have been detrimental to the guilty party.  But what if a party did not intentionally destroy evidence in bad faith, but rather lost the evidence due to a negligent mistake?  Should the same adverse inference instruction be used? In Pillay v. Millard Refrigerated Services, the court held that even if a party is merely negligent in destroying evidence, a jury may presume that the evidence would have been unfavorable to that party.  This permissive adverse inference instruction differs from the circumstances where the court determines that the party acted in bad faith because the court gives the jury the option of making an adverse inference.  Typically, when bad faith is present, the court will instruct the jury that it should presume the missing evidence is detrimental to the party who destroyed it.  This instruction differs from the instruction in Pillay where the court gave the jury the option of making the adverse inference. The Pillay court imposed a permissive adverse inference jury instruction when an employer negligently deleted relevant information.  The employer claimed that it terminated an employee because the employee’s production levels were down.  The employee claimed that he was terminated for unlawful reasons and that the employer’s labor management system (“LMS”) would show that the employee’s production level exceeded expectations. The employer, however, no longer possessed the LMS data because of routine deletions of the data after one year.  The data was deleted despite opposing counsel’s numerous requests to preserve all relevant documents and evidence. The employer argued sanctions were not warranted because the LMS data was not deleted intentionally or in bad faith.  The court rejected this argument holding that even without a showing of bad faith, the court has the discretion to impose sanctions when a party’s negligence causes information to be lost.  The court sanctioned the employer with the following permissive adverse jury instruction: Pillay contends that Millard at one time possessed data documenting [an employee’s] productivity and performance that was destroyed by Millard.  Millard contends that the loss of data was accidental.  You may assume that such evidence would have been unfavorable to Millard only if you find by a preponderance of the evidence that (1) Millard intentionally or recklessly caused the evidence to be destroyed; and (2) Millard caused the evidence to be destroyed in bad faith. Moving forward, this case means litigants must be extra careful in preserving evidence that may be relevant to litigation.  One negligent misstep, even if done without any showing of bad faith, may be the cause of an adverse jury instruction that can potentially be the deciding factor in a lawsuit. E-DiscoParty, a Seton Hall University School of Law graduate (class of 2014), served on the executive board of the Seton Hall Law Review and is a member of the Interscholastic Moot Court Board. E-DiscoParty now clerks for a Justice on the Supreme Court of New Jersey. 

Don’t Bite Off More Than You Can Chew: Requesting Party Does NOT Always Bear the Production Costs Related to E-Discovery

The plaintiff, Country Vintner, had an agreement with a winery (Esmeralda, who was not named a party to the action) to be the exclusive wholesaler of Alamos, which is an Argentinean wine, in North Carolina. A few years later, the defendant, Gallo, started supplying the wine to a variety of other wholesalers, but not to Country Vintner. The plaintiff sued Gallo for violations of the North Carolina Wine Distribution Agreements Act and for violations of the N.C. Unfair and Deceptive Trade Practices Act. Inevitably, there were disagreements over discovery of Electronically Stored Information (ESI). The plaintiff wanted emails and other ESI that would establish that there had been some sort of collusion between Esmeralda and Gallo that ended up excluding Country from the distribution of Alamos. The parties agreed to narrow the discovery request to certain key words, date restrictions, employees, etc., in order to accommodate Gallo’s complaints of an undue burden and expense to produce the requested information.  After much deliberation, and accompanying motions, the district court decided to adopt Country’s proposal, ordering several search-narrowing guidelines. Gallo then collected more than 62 gigabytes of data and gave the data to their lawyers to process and review. The lawyers processed the data into a) searchable data, b) removed system files and exact duplicates, c) and ran several variations of the 19 proposed search terms and phrases. The district court eventually granted Gallo a motion to dismiss the complaint regarding the Unfair and Deceptive Trade Practices Act, and also granted them summary judgment for the remaining Wine Act complaint. Then, perhaps getting a little ahead of itself, Gallo sought to recover $111,047.75 for their eDiscovery work. They broke down the costs as follows: $71,910.00 – for “flattening” and “indexing,” basically making the files searchable and removing duplicate content; $15,660.00 – for extracting the metadata, facilitating data review and other such things; $178.59 – for the conversion from native format to a .tif or .pdf format; $74.16 – for electronically Bates stamping the information; $40.00 – for copying the data onto a disc; $23,185.00 – for ensuring the “quality” of the data and ensure proper preparation of the documents for opposing counsel. The court granted a drastically reduced ESI-related recovery in the amount of $218.59. This covered the costs for copying or duplicating the files but not for their preparation or anything else. The court relied on a 2012 Third Circuit decision (Race Tires Am., Inc. v. Hoosier Racing Tire Corp.) and interpreted the applicable statute (28 U.S.C. § 1920(4), a.k.a. the “taxation of costs” statute) to exclude ESI processing costs. When Gallo appealed this decision, the Fourth Circuit affirmed the lower court’s decision. The court proceeded to go through the history of taxation of costs, which hadn’t existed prior to 1853, and has been slowly added to our law over the years. The latest version of section 1920 was amended in 2008, and allowed for fees for “printed or electronically recorded transcripts necessarily obtained for use in the case;” and “fees for exemplification and the costs of making copies of any materials where the copies are necessarily obtained for use in the case.” The court cited a Supreme Court decision that discussed the purpose of section 1920, and said that taxable costs should be a small fraction of the overall costs in litigation, and therefore should be interpreted narrowly to include only what is written in the law. Therefore, “making copies” was interpreted quite literally to include only the costs of actually making the copies, which in this case meant conversion to PDF and TIFF formats, and copying them onto a CD/DVD. Interestingly, the court also responded to the claim that the current e-technology requires more extensive preparation and therefore greater costs, by saying that preparation of discovery documents was always a big cost, yet were not authorized by Congress to be “taxable.” Gallo also tried to argue that when the statute provided for “exemplification” to be included in taxable costs, that it would include the costs in this case, since they had to load the information onto a review platform. The court said that exemplification does not apply here, since it means “an official transcript of a public record, authenticated as a true copy for use as evidence.” In our case, the charges didn’t include either any public records to be authenticated, or any exhibits. So the costs did not qualify as exemplification. What can be learned from this case is that although there are many things that go into the preparation of any type of discovery, including ESI, the costs of that preparation are not always carried by the requesting party. Undoubtedly, the charges that the defendant was trying to tax onto the plaintiff were legitimate. However, the history of the taxable charges laws has shown that the costs of production of discovery have been greatly limited to the copying stage, and not to the production.  I would suggest, therefore, that before a party actually goes through the production and incurs its costs, perhaps they should include the costs into their discovery agreement. Akiva Shepard received his J.D. from Seton Hall University School of Law in 2014. Akiva has worked for a New York State Supreme Court Judge in Kings County and for a NJ real estate firm. 

Judge Not Lest Ye Be Judged

Defendant Youkers was sentenced to an eight-year prison term. Youkers thereafter filed a motion for a new trial alleging that the judge who sentenced him engaged in improper communications and was not impartial. In particular, the father of Youkers’s girlfriend was one of the judge’s Facebook friends. The father also sent a message to the judge about Youkers’s pending case. Despite these potentially alarming facts, the judge testified that he knew the father because they both ran for office during the same election cycle. The judge testified that a mere Facebook friend designation was the extent of their relationship. Upon receiving the message from the father, the judge told the father that such communication was improper and he notified the appropriate individuals. To make Youkers’s allegations even weaker, the father was actually seeking leniency for Youkers. The court notes that the American Bar Association (ABA) has said in formal opinions that judges are not barred from using social media. Merely designating someone as a friend on Facebook “does not show the degree or intensity of a judge’s relationship with a person.” ABA Standing Comm. On Ethics & Prof’l Responsibility, Formal Op. 462 (2013). Accordingly the court concluded that the mere fact that the father and the judge were Facebook friends, by itself, did not suggest bias or partiality. The court concluded that there was no evidence of actual bias. Furthermore, because the judge fully complied with the Texas Committee on Judicial Ethics’ recommended procedure for treatment of ex parte communications, a reasonable person would conclude that there was no appearance of impropriety. Had the judge not followed state procedure on the treatment of ex parte communications, things might have gone differently. Judges should be very careful about all their communications and relationships over social media. Although in this case there was no communication between the judge and the father besides the father’s message and the judge’s response, a court might be willing to find bias if there was an ongoing relationship. Although a mere Facebook friendship alone does not establish anything, other communications over Facebook might have the effect of tending towards partiality. Rocco Seminerio is a 2014 Seton Hall University School of Law graduate. Mr. Seminerio focused his studies in the areas of Estate Planning, Elder Law, and Health Law. He graduated from Seton Hall University’s undergraduate program in 2011 with a degree in Philosophy. He is also interested in the life sciences.

Large Volumes of ESI Irrelevant in Determining Accessibility

In W Holding Co., Inc. v. Chartis Ins. Co. of Puerto Rico, the receiver of Westernbank, FDIC-R brought action under the Financial Institutions Reform, Recovery, and Enforcement Act (FIRREA) against the banks’ directors and officers (D & O’s) for gross negligence, breach of fiduciary duties, fraudulent conveyances, and adverse domination. Prior to discovery, FDIC-R proposed an order establishing a protocol for discovery of Wesernbank’s ESI and to reduce the number of written interrogatories it would receive. The D & O’s offered a competing protocol. The court denied FDIC-R’s request to alter the number of interrogatories and issued a separate order to establish ESI protocol. When FDIC stepped in as a receiver for Westernbank, it possessed 6.8 terabytes of ESI and over 900,000 paper documents. FDIC spent $2.1 million to put the ESI into a system called DMS iConnect (“DMS”), an internal database where the relevant paper documents were scanned into digital images and processed to generate searchable text. FDIC waned to use a second contractor-maintained system called Relativity to give its litigation opponents searchable access to selected data, which will cost $450 per gigabyte to move. FDIC-R wanted D & O to share in the costs. FDIC–R advanced three rationales in support of its proposal: (1) ESI production costs are analogous to “copying costs” borne by the requestor; (2) the Westernbank ESI is “not reasonably accessible” under Rule 26(b)(2)(B); and (3) the seven-factor test applied in Zubulake III requires cost-shifting in this case. The court disagrees with all three FDIC-R’s arguments. As to the argument that production costs are analogous to copying costs, the Court felt that FDIC-R failed to explain how those costs are outside the realm of gathering and preparation expenses customarily borne by responding parties. As for accessibility, the Court disagreed with FDIC-R’s position that Federal Rule of Civil Procedure 26(b)(2)(B) required cost-shifting when large volumes of ESI were involved. To be inaccessible, the FDIC-R would have to argue the “cost or burden” of production is tied to “some technological feature that inhibits accessibility.” However, the FDIC-R failed to raise any technological issues. The court further noted that the relevant data had already been uploaded into a searchable and organized retrieval system. The court also rejected FDIC-R’s third argument that the seven-factor test in Zubulake III requires cost shifting. Zubake also requires that the date in question be inaccessible, which the Court already stated was not. Finally, as to the request to limit the number of interrogatories, the Court believed the requests were “too speculative to merit a ruling at this time.” The Court felt that until the parties take more affirmative discovery steps, there is no ground for the Court to alter the defaults under the Federal Rules of Civil Procedure. Salim received his B.A. in Applied Communications, with a minor in Legal Studies, from Monmouth University. In 2014 he received his J.D. from Seton Hall University School of Law in 2014. Salim’s past experiences include interning for a personal injury law firm prior to attending law school, as well as judicial internships in the Civil and Family Divisions.

eDiscovery Expertise: Is Knowing Too Much A Ground For Judicial Recusal?

Just like TNT, the Second Circuit sure knows drama.  After years of protracted litigation, the Second Circuit finally put an end to an attempt to recuse a judge for knowing too much about eDiscovery and predictive coding. On April 10, 2013, in an incredibly brief order most likely meant to send a message deeper than its two sentences, a Second Circuit Judge denied a request for the recusal of Judge Andrew J. Peck from an ongoing employment discrimination case.  According to Judge Jane A. Restani, “Petitioners have not ‘clearly and indisputably demonstrate[d] that [Magistrate Judge Peck] abused [his] discretion’ in denying their court recusal motion… or that the district court erred in overruling their objection to that decision.” The contentious attempts to recuse Judge Peck stemmed from a discovery dispute after Judge Peck ordered the parties to use a method of predictive coding during discovery.  Although the parties seemed to agree that predictive coding should be used, they could not agree on the methods of predictive coding that would be implemented.  The plaintiffs believed that Judge Peck favored the defendants in his order, and therefore they moved to recuse the judge because of his established history with eDiscovery and more specifically, his history of actively advocating predictive coding. Judge Peck has a long history of participating in eDiscovery conferences  and was considered one of the Court’s “experts in e-discovery.”  National Day Laborer Organizing Netwrok v. U.S. Immigration and Customs Enforcement Agency, 2012 WL 2878130, 11 (S.D.N.Y. 2012).  Judge Peck was even involved in one of the first cases to order the discovery of electronic data.  Atlantic-Monopoly, Inc. v. Hasbro, Inc., 958 F.Supp 895 (S.D.N.Y. 1995). Despite the strong undertones of the order’s brevity, the plaintiffs continued to fight this seemingly uphill battle and later filed a cert petition to the Supreme Court. Rather than attacking Judge Peck’s background and connections to the eDiscovery community, the plaintiffs in this case should have instead accepted that judges need to actively participate in conferences and seminars to better understand the technology implicated in eDiscovery.  Just as attorneys can no longer ignore the ramifications of eDiscovery, judges too must enhance their knowledge to further develop this complicated area of law and readily adapt it to continually changing technology.  Judges should not be punished or accused of bias for engaging in programs geared towards teaching them about technology and its implications on eDiscovery.  If this were at all all permitted, judges would be afraid to participate in seminars and review panels, which would stagnate the development of the law, a process that is already far-behind the rapid progress experienced by technology. Jeffrey, a Seton Hall University School of Law graduate (Class of 2014), focused his studies primarily in the area of civil practice but also completed significant coursework concerning the interplay between technology and the legal profession.  He was a cum laude graduate of the University of Connecticut in 2011, where he received a B.S. in Business Administration with a concentration in Entrepreneurial Management. 

Request for E-Discovery Restart Because Defendant Used Keyword Culling is Shot Down by Seventh Circuit Judge

By the time In re Biomet made it in front of a Seventh Circuit Judge for a ruling, 2.5 million documents and attachments were produced to the plaintiffs in this large class action case against Biomet.  The plaintiffs wanted the judge to order the discovery of electronically stored information.  The plaintiff’s Steering Committee was unhappy with the amount of documents produced and claimed that it should have been almost five times that amount. The plaintiffs challenged the electronic discovery procedure that Biomet had undertaken.  Specifically, the plaintiffs wanted the judge to make a ruling that the defendant’s process was “tainted” by their use of keyword culling.  The judge disagreed and refused to make such a ruling, which would have thrown Biomet back to almost square one. Biomet went through an extensive process to cultivate documents to produce for the plaintiffs. Biomet first used “electronic search options, then predictive coding, and finally personal review.”  The plaintiff’s issue was primarily the first step that defendants irrevocably ruined the rest of their document production from the get-go. To first identify what documents would be relevant the defendant used a “combination of electronic search functions” which included keyword culling.  The defendant’s original pool consisted of 19.5 million documents and attachments which the first step narrowed down to 3.9 million (eventually getting to 2.5 million documents).  The plaintiffs thought they should have produced 10 million documents and said their keyword searches were the problem. The plaintiffs cited to a New York Law Journal article that said that keyword searches were “only 20 percent” responsive.  According to the plaintiffs, Biomet’s approach was flawed because it used the “less accurate” method of keyword search in the beginning instead of predictive coding.  They asked for the judge to rule that the defendants had to go back to the first step and use predictive coding with “plaintiffs and defendants jointly entering the ‘find more like this commands’. The judge found that the plaintiff’s journal article and one cited search claiming that Boolean and keyword searches are less effective at producing relevant documents were insufficient in proving that Biomet did not meet its discovery obligations.  Instead, the judge found that its procedure did comply with FRCP 26(b) and 34(b)(2).  The judge also refused to read into the rules that Biomet had to allow the plaintiffs to sift through possibly privileged documents with them. The judge also found that Biomet fulfilled their federal requirements as proven through their statistical sampling and confidence tests that they ran over their documents.  This sampling found that less than 1.34 percent of the documents that weren’t selected would be responsive and that between 1.37 and 2.47 of the original 19.5 were.  Biomet’s process singled out 16 percent out of that original. The judge cited heavily to FRCP 26 (b)(2)(C) and said that Plaintiffs’ request did not comport well with proportionality.  Biomet had already spent $1.07 million and “will total between 2 million and 3.25 million.”  Were Biomet to go back to their original bank of ESI, it would cost them in the low seven-figures.  The judge said that it would not make Biomet do that just to test the plaintiffs’ theory that more responsive documents would be found through predictive coding instead of keyword searches.