Electronic Discovery

What I’m Thankful for in Thanksgiving 2017: eDiscovery Thanks

Three years ago, I wrote about what I’m thankful for this holiday season from an eDiscovery standpoint.  I’m even more thankful and blessed now, so I thought I would do it again.  Happy Thanksgiving!

Our Great Team: It’s been a great year so far at CloudNine and I get a chance to work with all of the departments, from our terrific Client Services team that provides the hands on services that our clients need to meet their deadlines to our wonderful Support team that enables our clients to get the most out of our software products.  Thanks to our Marketing program, our blog is more popular than ever, we now conduct one to two webcasts a month and I’ve had the opportunity to speak at several conferences, including ILTA and The Masters Conference.  And, our Sales team has enabled us to continue to grow and expand our client base and set new company records!

Our Webcast Attendees and Participants: Speaking of webcasts, we’ve already done sixteen(!) of them this year and still have a couple more to conduct, including this one on eDiscovery Day.  Thanks to all of my co-presenters, including Karen DeSouza, Julia Romero Peter and, of course, Tom O’Connor.  And, thanks to everyone who has attended, many of whom have received CLE credit!  There are literally thousands of you!  :o)

Our Clients: Believe it or not, I have a day job over and above the blog – providing services to our clients.  Our services offering is one of the factors that makes CloudNine unique and I’m grateful to our clients for choosing us to assist them with their litigation and eDiscovery needs.  Not to mention that providing professional services to our clients gives me great ideas for blog posts!

Great eDiscovery Resources: As always, I’m thankful for the great resources that keep me up to date on eDiscovery trends, and they’re also great sources for blog topics!  Here are some of my favorites:

  • Ball in Your Court: Craig Ball always has the more interesting and compelling eDiscovery takes;
  • e-Discovery Team®: Ralph Losey’s blog still covers topics in more depth than any other;
  • Ride the Lightning: My go to site for data security info, courtesy of Sharon Nelson of Sensei Enterprises;
  • ACEDS: The Association of Certified E-Discovery Specialists (ACEDS) site provides regular industry updates that keep me informed and give me additional topics to cover;
  • eDiscovery Assistant: Kelly Twigger’s site is my new go to site for eDiscovery case law, giving me one place to go to check out the latest case law decisions;
  • Complex Discovery: As always, my colleague Rob Robinson is still the master at compiling stories and statistics related to eDiscovery topics, ranging from business confidence surveys to industry acquisitions to interesting articles that I may have otherwise missed (and lots more).

Our Readers: I’m also thankful for all of you who continue to read and follow this blog.  And, especially thanks to those who provide interesting and insightful comments on our posts.  We’re at over seven years now and over 1,800 posts (and counting)!  Thanks to all of you for reading and following us!

Personally, I’m very blessed and most thankful for my family, particularly my wife Paige and our kids Kiley and Carter.  I love you guys!

So, what do you think? What are you thankful for in eDiscovery or in general?  Please share any comments you might have or if you’d like to know more about a particular topic.

eDiscovery Daily will resume with new posts next Monday.

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

Here are Some More Up to Date Fun Facts on Big Data: eDiscovery Trends

For many of the webcasts that we’ve conducted at CloudNine this year, we’ve noted several big data fun facts that illustrate the challenges that many organizations face in managing increasing volumes of data.  But several of those facts are three years old.  So, we thought it would be fun to take a look at some more up to date facts about big data that you can share with your family at your annual Thanksgiving gathering!

It was just a little over three years ago that we shared these fun facts with you, courtesy of Bernard Marr.  Here are some of my favorite facts from that article back then:

  • Every 2 days we create as much information as we did from the beginning of time until 2003;
  • Over 90% of all the data in the world was created in the past 2 years;
  • The total amount of data being captured and stored by industry doubles every 1.2 years;
  • And, my favorite one – If you burned all of the data created in just one day onto DVDs, you could stack them on top of each other and reach the moon – twice.

Here are some of the more recent facts, again from Bernard Marr.  They may be dated April 2016 (OK, they’re not completely up to date), but they’re still interesting:

As always, we’ve provided the links to enable you to check out the source of each interesting big data stat.  One thing is certain about the growth of big data in the world today – the extent to which it’s growing will continue to be amazing!

So, what do you think?  What is your organization doing to combat increasing volumes of data?  Please share any comments you might have or if you’d like to know more about a particular topic.

Image Copyright © Dilbert.com

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

Florida Has a New eDiscovery Checklist: eDiscovery Best Practices

One of the best things about speaking at The Master’s Conference is that you get to see other great sessions and presentations as well.  During the Orlando event earlier this week, one of the sessions was presented by Ralph Losey, a regular thought leader interviewee on this blog, who discussed revisions and amendments to a notable Local Rule on Pretrial Procedure in Civil Actions.  Those amendments include an excellent new 33 point eDiscovery checklist.

As Ralph discussed during the session and covered on his excellent E-Discovery Team® blog here (side note: you’ve got to love any blog post with two pictures of Milton from Office Space), the United States District Court for the Southern District Court of Florida is now revising its Local Rule 16.1 on Pretrial Procedure in Civil Actions (here’s a link to the Local Rules with the revisions, including the Administrative Order regarding the amended Rules).  The amendments will go into effect on December 1, 2017.  As Ralph noted, the main revision in the local rules is the addition of a new subsection (K) under 16.1(b)(2) Conference Report that lists what must be included in the attorneys’ report:

(K) any issues about: (i) disclosure, discovery, or preservation of electronically stored information, including the form or forms in which it should be produced; (ii) claims of privilege or of protection as trial-preparation materials, including — if the parties agree on a procedure to assert those claims after production — whether to ask the court to include their agreement in an order under Federal Rule of Evidence 502: and (iii) when the parties have agreed to use the ESI Checklist available on the Court’s website (www.flsd.uscourts.gov), matters enumerated on the ESI Checklist;

Ralph calls the rule revision and checklist a “fine addition” to the local rules, indicating that his only complaint is that the rule change doesn’t go far enough on Federal Rule of Evidence 502 and Rule 502(d) orders for non-waiver of privilege (which we’ve covered several times on this blog, most recently here).  His only criticism of the checklist is its use of non-descript bullet points, instead of numbering.  So, Ralph in his blog post and also in a handout from this week’s session, changed the bullet points to Roman numeral letters for easier referencing.  He also provided comments regarding each of the items (in blue italics, so they’re easily distinguishable).

With that in mind, here are the eight categories contained within the ESI checklist (number of items in each section in parentheses):

I. Preservation (7 items)

II. Liaison (1 item)

III. Informal Discovery About Location and Types of Systems (4 items)

IV. Proportionality and Costs (6 items)

V. Search (2 items)

VI. Phasing (6 items)

VII. Production (4 items)

VIII. Privilege (3 items)

A couple of the most notable categories is the idea of having an eDiscovery liaison for each party (which I think is a great way to help ensure a smooth discovery process) and the option and approach of conducting discovery in phases (which is also a great idea to help prioritize production of ESI and keep the process moving forward).

Regardless, it’s a great resource and guide, whether you’re in Florida or not.  A copy of the checklist (again, with Ralph’s comments) can be found here.

So, what do you think?  Do you use a checklist to guide you through the discovery process? As always, 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. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Where Do You Start? Perhaps by Seeing What Other People Think: eDiscovery Best Practices

Earlier this week, Rob Robinson asked the question “Where Do I Start?” on his excellent Complex Discovery blog when discussing the most significant challenges for those seeking and sourcing eDiscovery software and software-enabled services.  Maybe one of the best places to start is by checking out the customer feedback.

In Rob’s article Where Do I Start? Seeking and Sourcing eDiscovery Software, he provides technology buying cycle steps to serve as a framework for helping individuals and organizations address the buying process challenge for eDiscovery software, as follows:

  1. Determine the Discovery Problem or Goal
  2. Identify Discovery Technology Critical to the Solution
  3. Form a Shortlist of Provider Solutions
  4. Talk to End Users of Solutions on Shortlist
  5. Evaluate Potential Solution Options (Discussions, Demonstrations, Trials)
  6. Select Solution and Negotiate Pricing and Terms

Rob notes that, in particular, steps three and four often pose unique challenges given the number of offerings and providers in the eDiscovery ecosystem.  However, one way to differentiate those offerings and providers is through customer feedback.  As Rob notes:

“For those interested in a more targeted, bottoms-up approach to evaluating possible software or software-enabled service solutions, several online technology review sites are available for helping individuals to understand offerings through the lens of customer feedback.”

Rob lists three sites to check out, which are:

Each site is a little bit different, but each is useful in their own way.

Capterra gives you the ability to sort products in several different ways, including “hot products”, most reviews and highest rated.  When you click on the star rating for a provider, you can see the individual reviews for that provider, which includes provider pros and cons identified by each reviewer, as well as an overall score and overall comment about their impression of the product.

G2 Crowd gives you a Crowd Grid® for eDiscovery, which looks at Market Presence and Satisfaction to identify Niche players, Contenders (I coulda been a contender!), High Performers and Leaders.  You have to know the icon for each of the providers (hint: ours is a blue cloud) or put your cursor on the provider to figure it out.  When you click on the provider icon, you get a popup with the provider name and their star rating – click on that and you get a listing of the reviews for that provider where the reviewers indicate things such as what they like best about the provider, what they dislike, recommendations to others considering the product and business problems solved and benefits from using the product.

Gartner Peer Insights lists the providers with the ability to sort by number of reviews, as well as overall rating.  When you put your cursor on a provider, you can choose to “read reviews” or “compare”, where you can select two or more providers and line them up side by side to compare based on various features.  If you sign up for full access to the site, you can read the full reviews, which are considerably extensive.

Reading the provider’s reviews can be an essential part of “doing your homework” prior to engaging that provider to evaluate them on your own because they can help you identify considerations that you might not otherwise think of on your own.  Consider checking out the reviews on these sites to learn “the good, the bad and the ugly” that the providers may or may not tell you themselves.

So, what do you think?  Do you check out product reviews when considering an eDiscovery provider? As always, 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. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Here’s an Opportunity to Learn More About On-Premise and Off-Premise Solutions and Where CloudNine Fits in Both: eDiscovery Trends

Many say that the cloud is revolutionizing eDiscovery as we know it, while others still prefer the control of the on-premise eDiscovery solutions they’re used to using.  So, what factors should you consider when selecting your own eDiscovery solution?  Thanks to our friends at ACEDS, you can learn more about the different approaches and how CloudNine supports both of those environments.

Today’s ACEDS webinar at noon CT (1pm ET, 10am PT) is titled On-Premise, Off-Premise or Both?  This is a one-hour session that I will be conducting that is part presentation and part demonstration, including a couple of new modules we’ve recently introduced at CloudNine.

Presentation Highlights:

  • Drivers for eDiscovery Technology Solution Decisions Today
  • The Cloud vs. No Cloud Debate
  • A Comparative Approach to eDiscovery Technology
  • Key Components of an eDiscovery Technology Solution

Demonstration Highlights:

  • CloudNine eDiscovery Platform (Upload/Process/Review/Produce)
  • NEW: Outpost from CloudNine: Data Transfer into Relativity
  • NEW: CloudNine Automated Data Collection

If you want an opportunity to learn a lot more about CloudNine and how we address today’s challenges with both on-premise and off-premise technology, this webinar is for you!  To sign up for today’s webcast, click here.  Hope to see you there!

So, what do you think?  Do you feel overwhelmed by the eDiscovery solution choices that exist today?  If so, please feel free to join us!  And, as always, 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. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Here’s a Chance to Keep What Could Go Wrong from Going Wrong: eDiscovery Best Practices

Today, I’m in Orlando, at The Master’s Conference Orlando event, which is a full day of educational sessions covering a wide range of topics.  Here is a link with more information about today’s conference and our panel discussion due up at 10:00 am today local time.  If you’re in the Orlando area, come check it out!

As data complexity, discovery costs, and regulatory challenges increase in volume and impact, the pulse rate of publicly highlighted eDiscovery mistakes continues to build. While these mistakes are unfortunate for those who experienced them, they can be beneficial to the rest of us in highlighting mistakes you can avoid in your own cases.  Here’s your chance to learn from their mistakes and keep what could go wrong from going wrong.

On the third annual E-Discovery Day, Friday, December 1 at noon CST (1:00pm EST, 10:00am PST), CloudNine will conduct the webcast Murphy’s eDiscovery Law: How to Keep What Could Go Wrong From Going Wrong. In this one-hour webcast that’s CLE-approved in selected states, we will discuss examples of recent eDiscovery disasters and highlight the common characteristics of those disasters and what can be done to avoid them in your own cases.  Topics include:

  • Attorney Duty of Competence
  • Avoiding the Mistake in Assuming that Discovery Begins When the Case is Filed
  • How to Proactively Address Inadvertent Privilege Productions
  • Up Front Planning to Reduce Review Costs
  • How to Avoid Getting Stuck with a Bad Production from Opposing Counsel
  • Understanding Your Data to Drive Discovery Decisions
  • Minimizing Potential ESI Spoliation Opportunities
  • How to Avoid Processing Mistakes that Can Slow You Down
  • Common Searching and Redaction Mistakes and How to Avoid Them
  • Checklist of Items to Ensure a Smooth and Accurate Production
  • Managing Communications: Attorney and Vendor Responsibilities

I’ll be presenting the webcast, along with Tom O’Connor, who is now a Special Consultant to CloudNine!  If you follow our blog, you’re undoubtedly familiar with Tom as a leading eDiscovery thought leader (who we’ve interviewed several times over the years) and I’m excited to have Tom as a participant in this webcast!  To register for it, click here.  Even if you can’t make it, go ahead and register to get a link to the slides and to the recording of the webcast (if you want to check it out later).  This is your opportunity to avoid mistakes that others have made.

So, what do you think?  What do you do when things go wrong?  Scream?  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. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Does this Ring a Bell? Court Orders Plaintiff’s Quick Peek Over Defendant’s Objections: eDiscovery Case Law

In Fairholme Funds, Inc. v. United States, No. 13-456C, (Fed. Cl. Oct. 23, 2017), Judge Margaret M. Sweeney, despite the defendant’s strong objection, granted the plaintiffs’ motion to compel a “quick peek” production of approximately 1,500 documents withheld as privileged pursuant to the bank authorization and deliberative process privileges.

Case Background

In this case where the plaintiffs sought just compensation under the Fifth Amendment, contending that the defendant engaged in taking their property without just compensation, the defendant produced additional documents multiple times during the course of discovery when challenged.  After their most recent status report filed on June 30, the parties indicated that defendant produced an additional 3,500 documents in response to the court’s March 7 order, and as a result of that production, plaintiffs identified thirty-eight documents they contended should not be withheld for privilege.

Following its review of the thirty-eight documents, the defendant produced an additional twenty-two documents.  In response to the release of these additional documents, plaintiffs proposed that the parties use the quick peek procedure authorized by FRE 502(d).  In response, the defendant objected, quoting a note published by The Sedona Conference (in its Commentary on Protection of Privileged ESI covered by us here), as follows:

“[FRE] 502(d) does not authorize a court to require parties to engage in ‘quick peek’ … productions and should not be used directly or indirectly to do so. … Rule 502 was designed to protect producing parties, not to be used as a weapon impeding a producing parties’ right to protect privileged material. Compelled disclosure of privileged information, even with a right to later claw back the information, forces a producing party to ring a bell that cannot be un-rung.”

After the defendant did not agree to the use of the procedure, the plaintiffs filed a motion to compel.

Judge’s Ruling

Judge Sweeney began with an analysis of [FRE] 502(d) and noted that the “general purpose” of the rule was to resolve longstanding disputes regarding inadvertent production and subject matter waiver and to address complaints about the cost of protecting privileged materials, which she noted were “two issues not relevant to the current dispute.”  Judge Sweeney also indicated (as the plaintiffs pointed out in their argument) that the advisory committee note to [FRE] 502(d) specifically stated that “a confidentiality order is enforceable whether or not it memorializes an agreement among the parties to the litigation”.

As a result, Judge Sweeney, noting the defendant’s “piecemeal” production and the desire to “facilitate the speedy and efficient conclusion of jurisdictional discovery”, granted the plaintiffs’ motion, partially because she had “every reason to believe” that the plaintiffs would seek in camera review of the documents.  Judge Sweeney stated: “Given the court’s heavy caseload and limited resources, the use of the quick peek procedure is a much more viable and attractive option. Not only will the court not have to expend its time and resources on a task that should be performed by the parties, but both parties will benefit from the prompt (or at least more prompt) resolution of outstanding discovery disputes. Thus, even though defendant has already reviewed the subject material multiple times, plaintiffs will continue to seek production of these materials, which will, in turn, continue to place a burden on the court—one which could be alleviated through the parties’ use of the quick peek procedure.”

So, what do you think?  Was the court wrong in going against The Sedona Conference recommendations?  Please share any comments you might have or if you’d like to know more about a particular topic.

Case opinion link courtesy of eDiscovery Assistant.

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

Addressing the Inconsistent Email Address: eDiscovery Best Practices

I recently had a client who was trying to search a fairly sizable archive in CloudNine (about 2.75 TB comprised of several million documents) and searching for emails to and from a given custodian.  That search proved a little more challenging than expected due to a legacy Microsoft Exchange attribute.  Let’s take a look at that scenario, substituting a generic email address.

If you have John Dough, who is an employee at Acme Parts, his email address might look like this: jdough@acmeparts.com.  And, for many emails that he sends to others, that’s how his email address might be represented.  However, it could also be represented this way, especially in his Sent Items folder in Exchange:

/O=ACME PARTS/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=jdough

Why does it look like that and not like the “normal” email address that ends in “acmeparts.com”?  Because it’s a different type of address.

The first example – jdough@acmeparts.com – is an SMTP address.  This is the email address you commonly use and refer to when providing others your email address.  It’s probably even on your business card.

The second example – /O=ACME PARTS/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=jdough – is the Exchange x500 address – it’s the internal Exchange address for your account.  So, why does that address exist?

It’s because when Microsoft decided to change the way servers were managed in Exchange 2007, they retained a single administrative group for backwards compatibility and stored details of Exchange 2007 servers there.  The legacyExchangeDN property of the mailbox in Active Director stores this information and, depending on the setup and version of the Exchange server when the emails are pulled from it, could be used as the address shown on some emails (especially when they’re received from internal parties).  I still see it pop up occasionally with some of the email collections that we encounter.

Fun fact for you: The value “FYDIBOHF23SPDLT” after “Exchange Administrative Group” is actually an encoded version of the string “EXCHANGE12ROCKS” with each character replaced with the letter that follows it in the alphabet (E->F, X->Y etc.).

So, what does that mean to you?  It can mean a more challenging effort to locate all of the emails for a given custodian or key party.

To address the situation, I generally like to perform a search for “exchange administrative group” or “FYDIBOHF23SPDLT” in the email participant fields (i.e., To, From, Cc, Bcc).  If I don’t get any hits, then I don’t have any Exchange x500 addresses and there are no worries.

If I do get hits, then I have to account for these email addresses.  Both the SMTP and Exchange x500 address have at least one thing in common – the custodian name.  Typically, that’s first initial and last name, but there are variations as some organizations (if they’re small enough) use just the first or last name for email addresses.  And, if you have two people with the same first initial and last name, you have to distinguish them, so the address could include middle initial (e.g., jtsmith) or number (e.g., jtsmith02).

In its Search form, CloudNine performs an autocomplete of a string typed in for a field, identifying any value for the field that contains that string.  So, an autocomplete for “jdough” in the To, From, Cc or Bcc fields would retrieve both examples at the top of this post if they were present – and also any personal email addresses if he used his first initial and last name on those too.  If it seems apparent that all “jdough” entries are associated with the custodian you’re looking for, then the search can be as simple as “contains jdough” (e.g., From contains jdough to get all variations in the From field).  If it looks like you have email addresses for somebody else, then you may have to search for the specific addresses.  Either way, you can use that technique to ensure retrieval of all of John Dough’s email address variations.

So, what do you think?  Have you encountered Exchange x500 addresses in your email collections? As always, 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. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Facebook Wants You to Send Them Your Naked Pictures to Prevent Revenge Porn. I’m Not Kidding: Data Privacy Trends

It sounds crazy, right?  Facebook wants you to stop worrying about your nudes being shared without your consent by actually sending it your nude photos.  It may not be crazy as it sounds.

In the article Facebook: upload your nudes to stop revenge porn, written by Lisa Vaas on the aptly named site Naked Security (what else?), the concept is introduced this way: “Facebook hasn’t given much detail, but from what little has been shared it sounds like it’s planning to use hashes of our nude images, just like law enforcement uses hashes of known child abuse imagery.”

Just as we generate hash values of documents in eDiscovery to identify duplicates, the same type of technology can be applied to photos.  So, the same photo, or identical copies of it, will always create the same hash.  A hash of your most intimate picture is no more revealing than this example provided in the article:

48008908c31b9c8f8ba6bf2a4a283f29c15309b1

Since 2008, the National Center for Missing & Exploited Children (NCMEC) has made available a list of hash values for known child sexual abuse images, provided by ISPs, that enables companies to check large volumes of files for matches without those companies themselves having to keep copies of offending images or to actually pry open people’s private messages.

The hash originally used to create unique file identifiers was MD5, but Microsoft at one point donated its own PhotoDNA technology (which creates a unique signature for an image by converting it to black and white, resizing it, and breaking it into a grid) to the effort.

Facebook hasn’t provided any detail as to whether that’s the technology it plans to use, but it has announced a pilot program with four countries – the UK, the US, Australia and Canada – in which people will typically be advised to send the photos to themselves via Messenger.  Facebook says that it won’t be storing nude pictures but will use photo-matching technology to tag the images after they’re sent via its encrypted Messenger service.  In theory, that would be enough to enable Facebook to take action to prevent any re-uploads, without the photo being stored or viewed by employees.

The author notes that she has submitted questions to Facebook for more info and poses an interesting question in the article: “For example, what safeguards are in place to ensure that people can’t take any old picture they want – a non-porn publicity photo, for example – and send it in, under the false premise that it’s a nude and that it’s a photo they themselves have the rights to have expunged from social media circulation?”

Good question.  Nonetheless, it’s an interesting concept and idea to prevent revenge porn – provided you can actually convince people to upload those photos and trust Facebook with them.

So, what do you think?  Do you trust hash technology to keep your most embarrassing photos from becoming public? As always, please share any comments you might have or if you’d like to know more about a particular topic.

Hat tip to Sharon Nelson and her Ride the Lightning blog (my go to source for interesting cybersecurity news) for the reference to the story.

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

Court Chastises Parties for Turning Case into a “Discovery Slugfest”: eDiscovery Case Law

In UnitedHealthcare of Fla., Inc. et al. v. Am. Renal Assoc., Inc. et al., No. 16-cv-81180-Marra/Matthewman (S.D. Fla. Oct. 20, 2017), Florida Magistrate Judge William Matthewman granted in part and denied in part the plaintiffs’ Motion for Reconsideration or Modification of Omnibus Discovery Order, clarifying the Court’s previous order regarding custodians and search terms, while denying the remainder of the plaintiff’s motion.  Judge Matthewman also chastised both parties for their lack of cooperation on search terms.

In the Court’s August order, the Court permitted Defendants to select an additional 16 custodians and an additional 12 search terms and to request more at a later date if Defendants have a good-faith basis to do so and also ruled that the defendants had not waived any privilege and did not have to produce a privilege log.

In the current Motion, the plaintiffs argued that the Court should reconsider or modify its Order because the Court never made a finding that Plaintiffs’ production was deficient, there is no evidence that would support such a conclusion, the Court did not tailor the additional custodians or search terms to “any purported inadequacy nor to any proportionality limits”, the Court did not “provide any mechanism for ensuring that ARA’s custodians and search terms do not capture an overwhelmingly, burdensome, disproportionate amount of information”, and the Court’s Order was “patently unfair”.  The plaintiffs also argued that the Court should reconsider its decision not to compel the defendants to provide a privilege log because they “wrongfully withheld a responsive, non-privileged document, and the Court should not rely on Defendants’ counsel’s representations that they have no additional non-privileged responsive documents.”

Noting that “the only asserted new evidence submitted by Plaintiffs consists of Docket Entries 303-1 through 303-4” (which included email correspondence, a list of the additional 16 custodians, a list of additional 12 search terms and a Declaration from the Director of e-Discovery at the plaintiff company), Judge Matthewman focused on the last paragraph of the Declaration, which stated:

“In my opinion and based on my experience, if additional time is taken to reexamine the search terms to minimize some of the more obvious deficiencies and then, after the search terms are run, allow for the parties to evaluate which terms hit on an excessive number of documents and narrow them accordingly, the process could be sped up significantly as the volume of documents for the steps after collection and indexing will likely be greatly reduced.”

In response, Judge Matthewman stated: “Ironically, this type of cooperation is exactly what this Court has been expecting from the parties and their counsel throughout this case—to work together to arrive at reasonable search terms, to run those search terms and engage in sampling to see if the search terms are producing responsive documents or excessive irrelevant hits, and then to continue to refine the search terms in a cooperative, professional effort until the search terms are appropriately refined and produce relevant documents without including an excessive number of irrelevant documents. However, despite what paragraph 12 of the Declaration suggests, and despite this Court’s suggestions to the parties and their counsel as to the cooperative and professional manner in which the parties should engage in the e-discovery process in this case, there has instead been an apparent lack of cooperation and constant bickering over discovery, especially e-discovery. The alleged new evidence submitted by Plaintiffs, that is, the list of additional search terms and custodians and the Declaration, clearly show that, where, as here, parties in a large civil case do not cooperatively engage in the e-discovery process, the collection and indexing of documents and the production of relevant documents, become much more difficult.”

Indicating that “the parties and their counsel, through their many discovery disputes and their litigiousness, have unnecessarily turned this case into what can best be termed as a ‘discovery slugfest’”, Judge Matthewman noted that “the parties have filed well over 50 discovery motions, responses, replies, notices, and declarations, many of which have been filed under seal” and that the Court “has held at least six discovery hearings in 2017, most of which were lengthy and contentious.”

Judge Matthewman also referenced several resources regarding cooperation for the parties to consider, including The Sedona Conference, the Federal Judges’ Guide to Discovery, as well as comments from Supreme Court Chief Justice John Roberts regarding the 2015 Amendments to Federal Rules of Civil Procedure 1 and 26.  With that in mind, Judge William granted in part and denied in part the plaintiffs’ Motion for Reconsideration or Modification of Omnibus Discovery Order, clarifying the Court’s previous order regarding custodians and search terms, while denying the remainder of the plaintiff’s motion, including their dispute over the number of custodians and search terms and the failure to require the defendants to produce a privilege log.

So, what do you think?  What can we learn from the parties’ lack of cooperation in this case?  Please share any comments you might have or if you’d like to know more about a particular topic.

Case opinion link courtesy of eDiscovery Assistant.

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