Close
Enter your
text here

Privileged

Deadline Extended to Vote for the Most Significant eDiscovery Case of 2010
 

Our ‘little experiment’ to see what the readers of eDiscoveryDaily think about case law developments in 2010 needs more time as we have not yet received enough votes yet to have a statistically significant result.  So, we’ve extended the deadline to select the case with the most significant impact on eDiscovery practices in 2010 to February 28.  Evidently, calling out the vote on the last business day before LegalTech is not the best timing.  Live and learn!

As noted previously, we have “nominated” five cases, which we feel were the most significant in different issues of case law, including duty to preserve and sanctions, clawback agreements under Federal Rule of Evidence 502, not reasonably accessible arguments and discoverability of social media content.  If you feel that some other case was the most significant case of 2010, you can select that case instead.  Again, it’s very important to note that you can vote anonymously, so we’re not using this as a “hook” to get your information.  You can select your case without providing any personal information.  However, we would welcome your comments as to why you selected the case you did and you can – optionally – identify yourself as well.

To get more information about the nominated cases (as well as other significant cases), click here.  To cast your vote, click here.

And, as always, please share any comments you might have or if you’d like to know more about a particular topic.

Vote for the Most Significant eDiscovery Case of 2010!
 

Since it’s awards season, we thought we would get into the act from an eDiscovery standpoint.  Sure, you have Oscars, Emmys and Grammys – but what about “EDDies”?  (I’ll bet you wondered what Eddie Munster could possibly have to do with eDiscovery, didn’t you?)

So, we’re conducting a ‘little experiment’ to see what the readers of eDiscoveryDaily think about case law developments in 2010.  This is our first annual “EDDies” award to select the case with the most significant impact on eDiscovery practices in 2010.  No cash or prizes being awarded, or even a statuette, but a chance to see what the readers think was the most important case of the year from an eDiscovery standpoint.

We have “nominated” five cases below, which we feel were the most significant in different issues of case law, including duty to preserve and sanctions, clawback agreements under Federal Rule of Evidence 502, not reasonably accessible arguments and discoverability of social media content.  We have a link to review more information about each case, and a link at the bottom of this post to cast your vote.

Very Important!  You can vote anonymously, so we’re not using this as a “hook” to get your information.  You can click on the link at the bottom, select your case and be done with it.  However, we would welcome your comments as to why you selected the case you did and you can – optionally – identify yourself as well.  eDiscoveryDaily will publish selected comments to reflect opinion of the voters as well as the vote results on February 7.  Click here to cast your vote now!

So, here are the cases:

Duty to Preserve/Sanctions

  • The Pension Committee of the Montreal Pension Plan v. Banc of America Securities, LLC, 29010 U.S. Dist. Lexis 4546 (S.D.N.Y. Jan. 15, 2010) (as amended May 28, 2010) – “Pension Committee”: The case that defined negligence, gross negligence, and willfulness in the electronic discovery context and demonstrated the consequences (via sanctions) resulting from those activities.  Judge Shira Scheindlin titled her 85-page opinion “Zubulake Revisited: Six Years Later”.  For more on this case, click here.
  • Victor Stanley, Inc. v. Creative Pipe, Inc., 2010 WL 3530097 (D. Md. 2010) – “Victor Stanley II”: The case of “the gang that couldn’t spoliate straight” where one of the defendants faced imprisonment for up to 2 years (subsequently set aside on appeal) and the opinion included a 12 page chart delineating the preservation and spoliation standards in each judicial circuit.  For more on this case, click here and here.

Clawback Agreements

  • Rajala v. McGuire Woods LLP, 2010 WL 2949582 (D. Kan. July 22, 2010) – “Rajala”: The case that addressed the applicability of Federal Rule of Evidence 502(d) and (e) for “clawback” provisions for inadvertently produced privileged documents.  For more on this case, click here.

Not Reasonably Accessible

  • Major Tours, Inc. v. Colorel, 2010 WL 2557250 (D.N.J. June 22, 2010) – “Major Tours”: The case that established a precedent that a party may obtain a Protective Order relieving it of the duty to access backup tapes, even when that party’s failure to issue a litigation hold caused the data not to be available via any other means.  For more on this case, click here.

Social Media Discovery

  • Crispin v. Christian Audigier Inc., 2010 U.S. Dist. Lexis 52832 (C.D. Calif. May 26, 2010) – “Crispin”: The case that used a 24 year old law (The Stored Communications Act of 1986) to address whether ‘private’ data on social networks is discoverable.  For more on this case, click here.

If you feel that some other case was the most significant case of 2010, you can select that case instead.  Other notable cases include:

  • Rimkus v. Cammarata, 2010 WL 645253 (S.D. Tex. Feb. 19, 2010): Where District Court Judge Lee Rosenthal examined spoliation laws of each of the 13 Federal Circuit Courts of Appeal.
  • Orbit One Communications Inc. v. Numerex Corp., 2010 WL 4615547 (S.D.N.Y. Oct. 26, 2010): Magistrate Judge James C. Francis concluded that sanctions for spoliation must be based on the loss of at least some information relevant to the dispute (differing with “Pension Committee” in this manner).
  • DeGeer v. Gillis, 2010 U.S. Dist. Lexis 97457(N.D. Ill. Sept. 17, 2010): Demonstration of inadvertent disclosure made FRE 502(d) effective, negating waiver of privilege.
  • Takeda Pharmaceutical Co., Ltd. v. Teva Pharmaceuticals USA, Inc., 2010 WL 2640492 (D. Del. June 21, 2010): Defendants’ motion to compel the production of ESI for a period of 18 years was granted, with imposed cost-shifting.
  • E.E.O.C. v. Simply Storage Management, LLC, 2010 U.S. Dist. Lexis 52766 (S.D. Ind. May 11, 2010): EEOC is ordered to produce certain social networking communications.
  • McMillen v. Hummingbird Speedway, Inc., No. 113-2010 CD (C.P. Jefferson, Sept. 9, 2010): Motion to Compel discovery of social network account log-in names and passwords was granted.

Click here to cast your vote now!  Results will be published in eDiscoveryDaily on February 7.

The success of this ‘little experiment’ will determine whether next year there is a second annual “EDDies” award.  😉

And, as always, please share any comments you might have or if you’d like to know more about a particular topic.

eDiscovery Case Law: When is Attorney-Client Communication NOT Privileged?

One answer: When it’s from your work email account, and your employer has a written policy that company email is not private and subject to audit.  Oh, and you’re suing your employer.

In Holmes v. Petrovich Dev. Co., LLC, 2011 WL 117230 (Cal. Ct. App. Jan. 13, 2011), a California court of appeals upheld a trial court ruling that emails from a plaintiff to her attorney via her company’s computer “did not constitute ‘confidential communication between client and lawyer’ within the meaning of Evidence Code section 952” and thus were not privileged.

The plaintiff, Gina Holmes worked as an executive assistant at Petrovich Development of Sacramento, California.  When hired, she read and signed the company’s policies regarding use of computers, which informed employees that they had no right of privacy to any personal information created or maintained on company computers, and that such information was subject to monitoring.

Holmes claimed Petrovich Development became hostile when it found out she was pregnant shortly after being hired in 2004 and used her company’s computer to communicate with an attorney, eventually quitting her job and suing her employer.  During the case, emails between her and her attorney were introduced at trial “to show Holmes did not suffer severe emotional distress, was only frustrated and annoyed, and filed the action at the urging of her attorney”.  Despite plaintiff’s protests that the emails were privileged, they were not excluded from evidence at trial.  Rather, the trial court ruled that the emails “were not protected … because they were not private.”  Because the plaintiff did not prevail on any of her claims, she appealed, claiming the court erred in failing to exclude the emails.

In a 3-0 decision by the Sacramento Third Appellate District, they affirmed the findings of the trial court, stating that the plaintiff’s use of the company computer after being expressly advised that her messages were not private was “akin to consulting her attorney in one of defendants’ conference rooms, in a loud voice, with the door open, yet unreasonably expecting that the conversation overheard … would be privileged.”.  The court also noted that “communication under these circumstances is not a “‘confidential communication between client and lawyer’ “ within the meaning of section 952 because it is not transmitted “by a means which, so far as the client is aware, discloses the information to no third persons other than those who are present to further the interest of the client in the consultation….”.

So, what do you think?  Was justice served?  Please share any comments you might have or if you’d like to know more about a particular topic.

eDiscovery Trends: Metadata Mining Ethics
 

Years ago, I put together a CLE course about metadata awareness and how hidden data (such as tracked changes and comments) can cause embarrassment or even inadvertent disclosures in eDiscovery.  The production of metadata with ESI continues to be a big issue in eDiscovery and organizations need to consider how to handle that metadata (especially if it’s hidden), to avoid issues.

For those who don’t know, metadata can be simply defined as “data about data”, which is to say it’s the data that describes each file and includes information such as when it was created, when it was last modified and who last modified it.  Metadata can often be used in identifying responsive files based on time frame (of creation or last editing) or other criteria.

Many types of files can contain other hidden metadata, such as a record the changes made to a file, who made those changes, and any comments that those parties may have also added (for example, Microsoft Word has Tracked Changes and Comments that aid in collaboration to obtain feedback from one or multiple parties regarding the content of the document).  Embedded objects can also be hidden, for example, depending on how you embed an Excel table into a Word document; the entire Excel file may be accessible within the document, even though only a small part of it is displayed.

Last fall, the American Bar Association published an article with a look at metadata ethics opinions, which was also recently referenced in this article.  The opinions issued to date have focused on three topics with regard to metadata production:

  • The sender's responsibility when transmitting or producing electronic files;
  • The recipient's right to examine (or "mine") files for metadata; and
  • The recipient's duty to notify the sender if sensitive data is discovered.

Sender’s Responsibility

Jurisdictions agree that an attorney sending or producing ESI has a duty to exercise caution to avoid inadvertently disclosing confidential information, though the level of caution required may vary depending upon the jurisdiction and situation.  In SBA Ethics Opinion 07-03, the State Bar of Arizona's Ethics Committee indicated that level of caution may depend upon "the sensitivity of the information, the potential consequences of its inadvertent disclosure, whether further disclosure is restricted by statute, protective order, or confidentiality agreement, and any special instructions given by the client."

Ignorance of technology is no excuse.  The Colorado Bar Association Ethics Committee states that attorneys cannot limit their duty "by remaining ignorant of technology relating to metadata or failing to obtain competent computer support." (CBA Ethics Opinion 119).

Recipient’s Right to Examine

There is less jurisdictional agreement here.  Colorado, Washington D.C. and West Virginia allow metadata mining unless the recipient is aware that the data was sent unintentionally. On the other hand, New York and Maine prohibit metadata mining – the New York State Bar Association's Committee on Professional Ethics based its decision in part on the "strong public policy in favor of protecting attorney-client confidentiality." (NYSBA Opinion 749).  Minnesota and Pennsylvania have not set a bright-line rule, stating that the decision to allow or prohibit metadata mining should depend on the case.

Recipient’s Duty to Notify

Most jurisdictions rely on their local variation of ABA Model Rule of Professional Conduct 4.4(b), which indicates that an attorney who receives confidential data inadvertently sent is obligated to notify the sender.  Maryland is one exception to that position, stating that "the receiving attorney can, and probably should, communicate with his or her client concerning the pros and cons of whether to notify the sending attorney." (MSBA Ethics Docket 2007-09).

Bottom Line

You may not be able to control what a recipient can do with your inadvertently produced metadata, but you can take steps to avoid the inadvertent production in the first place.  Office 2007 and greater has a built in Document Inspector that eliminates the hidden metadata in Office files, while publishing files to PDF will remove some metadata (the amount of metadata removed depends on the settings).  You can also use a metadata “scrubber” application such as Workshare Protect or Metadata Assistant to remove the metadata – most of these will even integrate with email so that you have the option to “scrub” the file before sending.

So, what do you think?  Have you been “stung” by hidden metadata?  Please share any comments you might have or if you’d like to know more about a particular topic.

eDiscovery Case Law: Privilege Waived for Produced Servers

If you were at the International Legal Technology Association (ILTA) trade show this past August, you may have noticed a huge unfinished building in the middle of the strip – the Fontainebleau Resort.  It sits idle after financing was pulled, forcing Fontainebleau Las Vegas LLC to file for Chapter 11 bankruptcy in June of 2009.  Naturally, lawsuits followed, between the Term Lenders and Fontainebleau Resort, LLC (FRLLC), the third party parent of Fontainebleau Las Vegas – In re Fontainebleau Las Vegas Contract Litig., (S.D. Fla. Jan 7, 2011)

A company that responded to a third party subpoena and court orders compelling production by handing over three servers to lenders without conducting any relevancy review and without reviewing two of the servers for privileged materials waived privilege for documents on the two servers that were not reviewed.

The parent company of a resort in bankruptcy proceedings was served by lenders to the resort with a subpoena for production of documents. The company did not object to the scope of the subpoena, and the court granted a motion of the lenders to compel production. Counsel for the company then halted work by an e-discovery vendor who had completed screening the company’s email server for responsive documents but had not started a privilege review because of concerns that the company could not pay for the services. Counsel for the company also sought to withdraw from the case, but the company was unable to find new counsel.

Rather than seeking a stay or challenging discovery rulings from the court, the company turned over data from a document server, an accounting server, and an email server. According to the court, the three servers were turned over to the lenders without any meaningful review for relevancy or responsiveness. Despite an agreement with the lenders on search terms for the email server, the company produced a 126 gigabyte disk with 700,000 emails from that server and then, without asking for leave of court, was late in producing a privilege log for data on the email server. The lenders sought direction from the court on waiver of privilege and their obligation if they found privileged materials in the data produced by the company. The company for the first time then raised objections to the burdensomeness of the original subpoena served over six months earlier given the company’s lack of resources or employees to conduct a document review.

The court held that the company “waived the attorney-client privilege and work product protection, and any other applicable privileges, for the materials it produced from two of three computer servers in what can fairly be described as a data dump as part of a significantly tardy response to a subpoena and to court-ordered production deadlines.” The court stated that in effect, the company “took the two servers, which it never reviewed for privilege or responsiveness, and said to the Term Lenders ‘here, you go figure it out.’”

However, because the company prepared a privilege log for the email server, the court added that privileges were not waived for materials from the email server. Also, the lenders were directed to alert the company to any “clearly privileged material they may find during their review of the production on the documents and accounting servers.” Although the court was not ruling on admissibility at trial of that privileged material, the lenders would be allowed to use it during pre-trial preparations, including depositions.

So, what do you think?  Was justice served?  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 Case Law: Rajala v. McGuire Woods

Yesterday, we took a look at “Pension Committee”, Judge Shira Scheindlin’s significant opinion regarding the duty for plaintiffs (as well as defendants) to preserve ESI and sanctions for failing to live up to that duty.

The holiday week look back at cases continues with Rajala v. McGuire Woods LLP, (D. Kan. July 22, 2010), which addresses the applicability of Federal Rule of Evidence 502(d) and (e) in McGuire Woods’ request for a clawback provision for privileged documents.

As part of negotiations over an appropriate protective order covering the treatment of confidential information, defendant McGuire Woods drafted a proposed order that included a clawback provision. Plaintiff opposed inclusion of a clawback provision in the agreement, arguing that the protective order should not deal with privilege issues and that “[t]he parties are free to enter stipulations at other times over other discovery issues, including … waiver of privileges and clawbacks… There is no need to force the issue here.” The protective order was subsequently entered without a clawback provision. After further meet and confer sessions, plaintiff still would not enter into a clawback agreement, and defendant filed a motion for entry of a clawback provision.

Agreeing with defendant’s arguments, the Court held that both Federal Rule of Civil Procedure 26(f) and Federal Rule of Evidence 502 contemplated the use of clawback provisions and that “entry of an order containing a clawback provision is not dependent on the agreement of the parties.” Because of the extensive amount of ESI in the litigation, and because defendant is a law firm with thousands of clients and a high risk of potential inadvertent disclosure, the Magistrate Judge concluded that defendant had made the requisite showing of good cause for entry of a clawback provision:

“[T]his case is precisely the type of case that would benefit from a clawback provision. Such a provision will permit the parties to conduct and respond to discovery in an expeditious manner, without the need for time-consuming and costly pre-production privilege reviews, and at the same time preserve the parties’ rights to assert the attorney-client privilege or work product immunity.”

So, what do you think?  Is this the most significant eDiscovery case of 2010?  Please share any comments you might have or if you’d like to know more about a particular topic.

Case Summary Source: Sidley Austin LLP.

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: Discovery Compelled for Social Media Content

Discoverability of social-media usage continues to be a hot topic for eDiscovery.  Information for litigants’ LinkedIn, Facebook, Twitter and MySpace accounts can be the “smoking gun” for litigators looking to pursue or defend a claim.

In McMillen v. Hummingbird Speedway, Inc., No. 113-2010 CD (C.P. Jefferson, Sept. 9, 2010), defendant Hummingbird Speedway, Inc. sought to compel discovery of the plaintiff’s social network account log-in names, and passwords.  A copy of the opinion granting that Motion to Compel is available here.

The plaintiff was allegedly injured during a stock car race in the summer of 2007.  During the litigation that followed, defendant Hummingbird Speedway, Inc. requested production of plaintiff’s user names, log-in names, and passwords for any social network accounts – to which the plaintiff objected, arguing that the information was confidential.  Based on information in the public sections of the plaintiff’s social network accounts, the defendant filed a Motion to Compel.

In his opposition to the motion, the plaintiff argued that communications with friends via social media sites were private and protected from disclosure. The court disagreed, indicating that the plaintiff was essentially asking the court to recognize an evidentiary privilege for such communications, but that there is no “social media privilege” recognized by Pennsylvania’s court or legislature.

The court also noted that those communications were not privileged based on “Wigmore’s test for privilege”, which requires the plaintiff to establish four factors:

  • “His communications originated in the confidence that they would not be disclosed”;
  • “The element of confidentiality is essential to fully and satisfactorily maintain the relationship between the affected parties”;
  • “Community agreement that the relationship must be sedulously fostered”; and
  • “The injury potentially sustained to the relationship because of the disclosure of the communication outweighs the benefit of correctly disposing of litigation”.

Because the plaintiff failed to establish these factors, the court ultimately ruled that “Where there is an indication that a person’s social network sites contain information relevant to the prosecution or defense of a lawsuit…and the law’s general dispreference for the allowance of privileges, access to those sites should be freely granted”.

So, what do you think?  There have been other cases where the discoverability of social media was called into question – have you experienced any?  Please share any comments you might have or if you’d like to know more about a particular topic.

P.S. – For those (like me) who didn’t know what the word “sedulously” meant, I’ve provided a link to the definition above… 🙂