Close
Enter your
text here

Privileged

Apple Can’t Mention Inadvertent Disclosure in Samsung Case – eDiscovery Case Law

Back in January, Quinn Emanuel Urquhart & Sullivan LLP was sanctioned for their inadvertent disclosure in the Apple vs Samsung litigation (commonly referred to as “patentgate”).  California Magistrate Judge Paul S. Grewal handed down an order on motions for sanctions against Quinn Emanuel (in essence) requiring the firm to “reimburse Apple, Nokia, and their counsel for any and all costs and fees incurred in litigating this motion and the discovery associated with it”.  Many felt that Samsung and Quinn Emanuel got off lightly.  Now, Apple can’t even mention the inadvertent disclosure in the upcoming Samsung trial.

According to a story on Law360 (subscription required), U.S. District Court Judge Lucy Koh barred Apple last Wednesday from presenting evidence that Quinn Emanuel leaked confidential information regarding an Apple license agreement, saying that such testimony could prejudice jurors.  “The court believes any evidence [on the leak] could be irrelevant and a waste of time. It would confuse the jury and is outweighed by prejudice,” Judge Koh said. “Apple says it doesn’t intend to bring in any information of that violation unless Samsung opens the door.”

Judge Koh also came close to barring Apple from introducing evidence on the total revenues Samsung earned selling its products that are alleged to infringe on Apple patents. In their damages retrial in November where Apple was awarded $290.5 million (bringing the total awarded for infringing on Apple products to almost $930 million), Samsung’s revenues became a sticking point.  Although Samsung argued last week that Apple shouldn’t be allowed to bring up any of Samsung’s revenues or profits from the accused products, Judge Koh said she wouldn’t go that far. Apple’s damages expert uses many of those numbers in his calculations, and it would be “weird” to limit his testimony on income he considered in those calculations, she said.

For our previous coverage of the case, click here, here, here, here, here and here.

So, what do you think? Is this the case that never ends?  Will there be much more to come?  Do you wish you had some of the fees from this case?  Please share any comments you might have or if you’d like to know more about a particular topic.

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

EDRM Updates Privacy & Security Risk Reduction Model – eDiscovery Best Practices

The Electronic Discovery Reference Model (EDRM) continues to pile up the accomplishments. In addition to announcing a transition to nonprofit status by May 2014, since the May annual meeting, several EDRM projects (Metrics, Jobs, Data Set and the new Native Files project) have already announced new deliverables and/or requested feedback and EDRM also published new Collection Standards for collecting electronically stored information (ESI).  Now, EDRM is making updates to earlier accomplishments from just five months ago.

As they announced last week, EDRM announced the reintroduction and refinement of its Privacy & Security Risk Reduction Model (PSRRM). Initially introduced last September by EDRM’s Data Set group (and covered on this blog here), the model provides a process for reducing the volume of private, protected and risky data by using a series of steps applied in sequence as part of the information management, identification, preservation and collection phases of the Electronic Discovery Reference Model.

The PSRRM model is used prior to producing or exporting data containing risky information such as privileged or proprietary information. The middle steps are cyclical and are repeated until the amount of private material is reduced to a desirable amount. The private data is finally quarantined in the final step before the remaining information is produced.

Recent high profile data breaches at Target and Neiman Marcus are prime examples to illustrate that high risk data can cause significant trouble and exposure for organizations today.  As their press release notes, EDRM has revised the PSRRM to include industry feedback and real-world experiences using the model in data remediation and eDiscovery projects to help companies address this exposure in an organized and systematic manner.

The current resource page for the PSRRM model is located here.

So, what do you think?  How do you handle security of your organization’s sensitive data?  Please share any comments you might have or if you’d like to know more about a particular topic.

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

Quinn Emanuel Sanctioned for Inadvertent Disclosure, Samsung Escapes Sanction – eDiscovery Case Law

California Magistrate Judge Paul S. Grewal has now handed down an order on motions for sanctions against Samsung and the Quinn Emanuel law firm in the never-ending Apple v. Samsung litigation for the inadvertent disclosure of confidential agreements that Apple had with Nokia, Ericsson, Sharp and Philips – now widely referred to as “patentgate”.

After discovery on the matter, Judge Grewal ruled as follows:

“Quinn Emanuel shall reimburse Apple, Nokia, and their counsel for any and all costs and fees incurred in litigating this motion and the discovery associated with it, as required by Rule 37 in the absence of ‘substantial justification’ or other showing of ‘harmlessness,’ neither of which the court finds here. That expense, in addition to the public findings of wrongdoing, is, in the court’s opinion, sufficient both to remedy Apple and Nokia’s harm and to discourage similar conduct in the future.”

Basically, Judge Grewal determined that “what began as a chorus of loud and certain accusations had died down to aggressive suppositions and inferences, and without anything more, Quinn Emanuel and Samsung cannot reasonably be subject to more punitive sanctions”.

Apple and Nokia had proposed a number of “creative” sanctions that Quinn and Samsung ranging from an injunction against Samsung in the case to a ten-year ban from representing any party adverse to Nokia – suggestions that Judge Grewal referred to as “ludicrously overbroad”.

For a link to the order, click here.

For our previous coverage of the case, click here, here, here, here and here.

So, what do you think?  Did Samsung and Quinn Emanuel get off lightly?  Or was the sanction appropriate?   Please share any comments you might have or if you’d like to know more about a particular topic.

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

Samsung Again Owes Apple Almost $1 Billion, Sanction Deadline Nears – eDiscovery Case Law

The news continues to get worse for Samsung Electronics Co. in its colossal legal battle with Apple Inc…

A California federal jury ruled on November 21 that Samsung owes Apple $290.5 million for selling mobile devices that infringed five iPhone and iPad patents, bringing the total awarded for infringing on Apple products to almost $930 million.

The jury deliberated over the course of three days before reaching its decision and awarding the amount, which was less than the $380 million Apple sought from Samsung, but far more than Samsung’s efforts to cap damages at $53 million.

In August of last year, Apple was awarded over a billion dollar verdict, but U.S. District Judge Lucy Koh later reduced those damages to a measly $599 million and ordered a retrial on 13 of Samsung’s products, saying the earlier jury’s math on those gadgets didn’t add up.

And, that may not be the worst of it for Samsung.  Due to the disclosure of confidential agreements that Apple had with Nokia, Ericsson, Sharp and Philips – now widely referred to as “patentgate” – Samsung and its outside counsel Quinn Emanuel Urquhart & Sullivan LLP are facing sanctions for that disclosure.

According to a declaration from Nokia’s Chief Intellectual Property Officer, Paul Melin, on June 4, in a meeting between Samsung and Nokia licensing executives, Dr. Seungho Ahn informed Nokia that the terms of the Apple-Nokia license were known to him. Specifically, according to Mr. Melin, Dr. Ahn stated that Apple had produced the Apple-Nokia license in its litigation with Samsung, and that Samsung’s outside counsel had provided his team with the terms of the Apple-Nokia license. Mr. Melin recounts that to prove to Nokia that he knew the confidential terms of the Apple-Nokia license, Dr. Ahn recited the terms of the license, and even went so far as to tell Nokia that “all information leaks.”

Partner John Quinn of Quinn Emanuel acknowledged the inadvertent disclosure, which was apparently due to an associate at the firm failing to obscure a footnote and two paragraphs while performing a digital redaction of a 150-page report which was posted on an FTP site that was accessible by Samsung personnel.

As a result, California Magistrate Judge Paul S. Grewal ordered an “in camera” review of documents that Samsung claimed as privileged which Apple doubted that they were legitimately withheld from its lawyers.  Then, on November 8 after the review was conducted, Judge Grewal ordered Samsung and Quinn Emanuel to show cause why they should not be sanctioned, stating that “it appears…that sanctions against Samsung and its attorneys are warranted”.  However, he gave Samsung one last chance to defend its actions ordering Samsung to file a brief by December 2 (today) to explain why it should not be sanctioned, while also allowing Apple and Nokia to file a brief to propose appropriate sanctions, with a hearing on the matter set for next Monday, December 9.

So, what do you think?  Can it get any worse for Samsung?   Please share any comments you might have or if you’d like to know more about a particular topic.

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

The Ubiquitous Apple Samsung Case and “Patentgate” – eDiscovery Case Law

When something gets the “gate” suffix added to it, that’s not a good thing.

It’s hard to believe that a case can get more intense than when a billion dollar verdict is awarded (later reduced to a measly $599 million), but the Apple v. Samsung case seems to only be getting more intense, due to the disclosure of confidential agreements that Apple had with Nokia, Ericsson, Sharp and Philips – now widely referred to as “patentgate”.

Here is a summary of events as they are described in California Magistrate Judge Paul S. Grewal’s Order from October 2 regarding Apple’s motion for sanctions (which Nokia joined):

“During the massive fact discovery in this case between August 2011 and March 2012, Apple produced copies of a number of its patent license agreements, including a June 2011 license between Apple and Nokia. Apple marked the Apple-Nokia license as “Highly Confidential —Attorney Eyes’ Only” as permitted by the court’s protective order. Apple also produced and marked as “Highly Confidential —Attorney Eyes’ Only” similar patent license agreements it has reached with Ericsson, Sharp, and Philips.”

“As fact discovery transitioned to expert discovery, on March 24, 2012, Samsung’s outside counsel sent Samsung a draft expert report by Dr. David J. Teece. Dr. Teece’s report concerned damages to be awarded for Apple’s alleged infringement of Samsung’s asserted declared-essential patents. Because it addressed highly confidential, attorneys’ eyes only information, the report should have been fully redacted of that information before it was sent. However, intentionally or inadvertently, it was not. The report as distributed included key terms of each of the four Apple license agreements.”

“Samsung’s outside counsel [Quinn Emanuel Urquhart & Sullivan LLP] posted the report on an FTP site that was accessible by Samsung personnel. An email providing instructions to access the FTP site was addressed to the regular client distribution list used by counsel to provide Samsung personnel updates regarding this case. The information was then sent, over several different occasions, to over fifty Samsung employees, including high-ranking licensing executives. Specifically, on at least four occasions between March 24, 2012 and December 21, 2012, Samsung’s outside counsel emailed a copy of some version of the report to Samsung employees, as well as various counsel representing Samsung in courts and jurisdictions outside the United States.”

“At this point, things get murky. According to a declaration from Nokia’s Chief Intellectual Property Officer, Paul Melin, on June 4, 2013, in a meeting between Samsung and Nokia licensing executives, Dr. Seungho Ahn informed Nokia that the terms of the Apple-Nokia license were known to him. Specifically, according to Mr. Melin, Dr. Ahn stated that Apple had produced the Apple-Nokia license in its litigation with Samsung, and that Samsung’s outside counsel had provided his team with the terms of the Apple-Nokia license. Mr. Melin recounts that to prove to Nokia that he knew the confidential terms of the Apple-Nokia license, Dr. Ahn recited the terms of the license, and even went so far as to tell Nokia that “all information leaks.” Mr. Melin also reports that Dr. Ahn and Samsung then proceeded to use his knowledge of the terms of the Apple-Nokia license to gain an unfair advantage in their negotiations with Nokia, by asserting that the Apple-Nokia terms should dictate terms of a Samsung-Nokia license.”

Over the next few weeks, Samsung appealed the order to District Judge Lucy Koh, who was even more critical, finding the disclosures “improper” and Samsung’s lack of cooperation “inexcusable”.  A couple weeks later, Samsung provided sworn declarations, including one by Dr. Ahn that strongly contradicted Nokia’s representation of the June meeting. At a follow up hearing, Judge Grewal said he was not yet convinced that sanctions were warranted, ordering an “in camera” review of documents that Samsung claimed as privileged which Apple doubted that they were legitimately withheld from its lawyers.

As for Quinn Emanuel, who is also facing potential sanctions, partner John Quinn acknowledged the inadvertent disclosure, which was apparently due to an associate at the firm failing to obscure a footnote and two paragraphs while performing a digital redaction of the 150-page report and announced the creation of a new document retention policy to provide a “second pair of eyes” and avoid similar errors in the future (as reported by IT-Lex)

This past Friday, Judge Grewal ordered Samsung and Quinn Emanuel to show cause why they should not be sanctioned, stating “Having finally crawled out from under the boxes, it appears to the undersigned that if anything was breached, it was this court’s protective order, and that sanctions against Samsung and its attorneys are warranted”.  However, he gave Samsung one last chance to defend its actions ordering Samsung to file a brief by December 2 to explain why it should not be sanctioned, while also allowing Apple and Nokia to file a brief to propose appropriate sanctions, with a hearing on the matter set for December 9.

It will be interesting to see what transpires from here.  There have been at least 31 court filings so far this year in this case, so it looks like they’re just getting warmed up.

So, what do you think?  Are Quinn Emanuel and Samsung in serious trouble?  Please share any comments you might have or if you’d like to know more about a particular topic.

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

Court Rules Defendant Doesn’t Have Controls of PCs of Former Members, Denies Plaintiff’s Motion to Compel – eDiscovery Case Law

To require a party to produce evidence in discovery, the party must have “possession, custody, or control” of the evidence. In Kickapoo Tribe of Indians of the Kickapoo Reservation in Kansas v. Nemaha Brown Watershed Joint District No. 7, No. 06-CV-2248-CM-DJW (D. Kan. Sept. 23, 2013), the defendant did not have control over the personal computers of its former members, employees, or staff; it did not have the legal right to obtain information from them “on demand.” Therefore, the court rejected the plaintiff’s motion to compel and refused to order the forensic examination of the personal computers of current or former members, employees, or staff.

In this water rights lawsuit, the Tribe filed a motion to compel seeking an order that the defendant district produce documents and permit the forensic examination of its computers. In August 2012, the Tribe issued a request for production of the documents and computers for inspection on two counts it had recently added to its second amended complaint. Although the district responded, the Tribe found the response lacking and claimed that the district had not produced all responsive documents.

The district objected on four grounds. First, and most important to the requests at issue here, the district maintained that it could not “compel former members of the Board of Directors, former staff, or former employees to produce documents that are in their possession but that are not in the possession of the Watershed District itself.” Second, the district averred that the requests duplicated earlier discovery requests on the first four counts of the complaint, where discovery had already closed. Third, the requests were vague and could include privileged documents. Fourth, the district had already produced all documents.

The court agreed that the district did not “have the duty or ability to compel production of documents from persons no longer associated with the District that are not parties to this action.” Under Federal Rule of Civil Procedure 34(a)(1), the district did not have “possession, custody, or control” of the requested documents, which it defined as having “actual possession, custody, or control” or “the legal right to obtain the documents on demand.” The Tribe could not meet its burden to prove that the district had control of the requested documents.

However, the district had not shown that the requests were duplicative or cumulative; if any documents were privileged, the district would have to provide a privilege log. It rejected the Tribe’s claim that documents from a third party supported its argument that the district had not produced all documents.

As for the Tribe’s request for an order requiring the forensic mirror imaging of the computers personally owned by the current and former district board members, employees, and staff, the court sided with the district. The advisory committee notes to Rule 34(a), which permits the inspection of electronically stored information, provide that “the inspection of a responding party’s hard drive is not routine, but might be justified in some circumstances.” Here, the district did not have possession, custody, or control of these computers and thus could not produce them; moreover, the Tribe could not show “beyond speculation” that these computers were used for district business. Finally, the court noted that it had “significant concerns regarding the intrusiveness of the request and the privacy rights of the individuals to be affected,” especially in light of the Tribe’s “broad, non-specific request” for inspection.

So, what do you think?  Should the motion to compel have been granted?   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.

What is “Reduping?” – eDiscovery Explained

We’ve talked about “reduping” before, but since this question came up with a client recently, I thought it was worth revisiting.

As emails are sent out to multiple custodians, deduplication (or “deduping”) has become a common practice to eliminate multiple copies of the same email or file from the review collection, saving considerable review costs and ensuring consistency by not having different reviewers apply different responsiveness or privilege determinations to the same file (e.g., one copy of a file designated as privileged while the other is not may cause a privileged file to slip into the production set).  Deduping can be performed either across custodians in a case or within each custodian.

Everyone who works in electronic discovery knows what “deduping” is.  But how many of you know what “reduping” is?  Here’s the answer:

“Reduping” is the process of re-introducing duplicates back into the population for production after completing review.  There are a couple of reasons why a producing party may want to “redupe” the collection after review:

  • Deduping Not Requested by Receiving Party: As opposing parties in many cases still don’t conduct a meet and confer or discuss specifications for production, they may not have discussed whether or not to include duplicates in the production set.  In those cases, the producing party may choose to produce the duplicates, giving the receiving party more files to review and driving up their costs (yes, it still happens).  The attitude of the producing party can be “hey, they didn’t specify, so we’ll give them more than they asked for.”
  • Receiving Party May Want to See Who Has Copies of Specific Files: Sometimes, the receiving party does request that “dupes” are identified, but only within custodians, not across them.  In those cases, it’s because they want to see who had a copy of a specific email or file.  However, the producing party still doesn’t want to review the duplicates (because of increasing costs and the possibility of inconsistent designations), so they review a deduped collection and then redupe after review is complete.

As a receiving party, you’ll want to specifically address how dupes should be handled during production to ensure that you don’t receive duplicate files that provide no value.

Many review applications support the capability for reduping.  For example, CloudNine Discovery‘s review tool (shameless plug warning!) OnDemand®, enables duplicates to be suppressed from review, but then enables the same tags to be applied to the duplicates of any files tagged during review.  When it’s time to export documents for production, the user can decide at that time whether or not to export the dupes as part of that production.

So, what do you think?  Do any of your cases include “reduping” as part of production?   Please share any comments you might have or if you’d like to know more about a particular topic.

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

For Successful Discovery, Think Backwards – eDiscovery Best Practices

The Electronic Discovery Reference Model (EDRM) has become the standard model for the workflow of the process for handling electronically stored information (ESI) in discovery.  But, to succeed in discovery, regardless whether you’re the producing party or the receiving party, it might be helpful to think about the EDRM model backwards.

Why think backwards?

You can’t have a successful outcome without envisioning the successful outcome that you want to achieve.  The end of the discovery process includes the production and presentation stages, so it’s important to determine what you want to get out of those stages.  Let’s look at them.

Presentation

As a receiving party, it’s important to think about what types of evidence you need to support your case when presenting at depositions and at trial – this is the type of information that needs to be included in your production requests at the beginning of the case.

Production

The format of the ESI produced is important to both sides in the case.  For the receiving party, it’s important to get as much useful information included in the production as possible.  This includes metadata and searchable text for the produced documents, typically with an index or load file to facilitate loading into a review application.  The most useful form of production is native format files with all metadata preserved as used in the normal course of business.

For the producing party, it’s important to save costs, so it’s important to agree to a production format that minimizes production costs.  Converting files to an image based format (such as TIFF) adds costs, so producing in native format can be cost effective for the producing party as well.  It’s also important to determine how to handle issues such as privilege logs and redaction of privileged or confidential information.

Addressing production format issues up front will maximize cost savings and enable each party to get what they want out of the production of ESI.

Processing-Review-Analysis

It also pays to determine early in the process about decisions that affect processing, review and analysis.  How should exception files be handled?  What do you do about files that are infected with malware?  These are examples of issues that need to be decided up front to determine how processing will be handled.

As for review, the review tool being used may impact production specs in terms of how files are viewed and production of load files that are compatible with the review tool, among other considerations.  As for analysis, surely you test search terms to determine their effectiveness before you agree on those terms with opposing counsel, right?

Preservation-Collection-Identification

Long before you have to conduct preservation and collection for a case, you need to establish procedures for implementing and monitoring litigation holds, as well as prepare a data map to identify where corporate information is stored for identification, preservation and collection purposes.

As you can see, at the beginning of a case (and even before), it’s important to think backwards within the EDRM model to ensure a successful discovery process.  Decisions made at the beginning of the case affect the success of those latter stages, so don’t forget to think backwards!

So, what do you think?  What do you do at the beginning of a case to ensure success at the end?   Please share any comments you might have or if you’d like to know more about a particular topic.

P.S. — Notice anything different about the EDRM graphic?

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.

A Model for Reducing Private Data – eDiscovery Best Practices

Since the Electronic Discovery Reference Model (EDRM) annual meeting just four short months ago in May, several EDRM projects (Metrics, Jobs, Data Set and the new Native Files project) have already announced new deliverables and/or requested feedback.  Now, the Data Set project has announced another new deliverable – a new Privacy Risk Reduction Model.

Announced in yesterday’s press release, the new model “is a process for reducing the volume of private, protected and risky data by using a series of steps applied in sequence as part of the information management, identification, preservation and collection phases” of the EDRM.  It “is used prior to producing or exporting data containing risky information such as privileged or proprietary information.”

The model uses a series of six steps applied in sequence with the middle four steps being performed as an iterative process until the amount of private information is reduced to a desirable level.  Here are the steps as described on the EDRM site:

  • Define Risk: Risk is initially identified by an organization by stakeholders who can quantify the specific risks a particular class or type of data may pose. For example, risky data may include personally identifiable information (PII) such as credit card numbers, attorney-client privileged communications or trade secrets.
  • Identify Available Data: Locations and types of risky data should be identified. Possible locations may include email repositories, backups, email and data archives, file shares, individual workstations and laptops, and portable storage devices. The quantity and type should also be specified.
  • Create Filters: Search methods and filters are created to ‘catch’ risky data. They may include keyword, data range, file type, subject line etc.
  • Run Filters: The filters are executed and the results evaluated for accuracy.
  • Verify Output: The data identified or captured by the filters is compared against the anticipated output. If the filters did not catch all the expected risky data, additional filters can be created or existing filters can be refined and the process run again. Additionally, the output from the filters may identify additional risky data or data sources in which case this new data should be subjected the risk reduction process.
  • Quarantine: After an acceptable amount of risky data has been identified through the process, it should be quarantined from the original data sets. This may be done through migration of non-risky data, or through extraction or deletion of the risky data from the original data set.

No EDRM model would be complete without a handy graphic to illustrate the process so, as you can see above, this model includes one that illustrates the steps as well as the risk-time continuum (not to be confused with the space-time continuum, relatively speaking)… 😉

Looks like a sound process, it will be interesting to see it in use.  Hopefully, it will enable the Data Set team to avoid some of the “controversy” experienced during the process of removing private data from the Enron data set.  Kudos to the Data Set team, including project co-leaders Michael Lappin, director of archiving strategy at Nuix, and Eric Robi, president of Elluma Discovery!

So, what do you think?  What do you think of the process?   Please share any comments you might have or if you’d like to know more about a particular topic.

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

eDiscovery Daily is Three Years Old!

We’ve always been free, now we are three!

It’s hard to believe that it has been three years ago today since we launched the eDiscoveryDaily blog.  We’re past the “terrible twos” and heading towards pre-school.  Before you know it, we’ll be ready to take our driver’s test!

We have seen traffic on our site (from our first three months of existence to our most recent three months) grow an amazing 575%!  Our subscriber base has grown over 50% in the last year alone!  Back in June, we hit over 200,000 visits on the site and now we have over 236,000!

We continue to appreciate the interest you’ve shown in the topics and will do our best to continue to provide interesting and useful posts about eDiscovery trends, best practices and case law.  That’s what this blog is all about.  And, in each post, we like to ask for you to “please share any comments you might have or if you’d like to know more about a particular topic”, so we encourage you to do so to make this blog even more useful.

We also want to thank the blogs and publications that have linked to our posts and raised our public awareness, including Pinhawk, Ride the Lightning, Litigation Support Guru, Complex Discovery, Bryan College, The Electronic Discovery Reading Room, Litigation Support Today, Alltop, ABA Journal, Litigation Support Blog.com, Litigation Support Technology & News, InfoGovernance Engagement Area, EDD Blog Online, eDiscovery Journal, Learn About E-Discovery, e-Discovery Team ® and any other publication that has picked up at least one of our posts for reference (sorry if I missed any!).  We really appreciate it!

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

Rodney Dangerfield might put it this way – “I Tell Ya, Information Governance Gets No Respect”

Is it Time to Ditch the Per Hour Model for Document Review?  Here’s some food for thought.

Is it Possible for a File to be Modified Before it is Created?  Maybe, but here are some mechanisms for avoiding that scenario (here, here, here, here, here and here).  Best of all, they’re free.

Did you know changes to the Federal eDiscovery Rules are coming?  Here’s some more information.

Count Minnesota and Kansas among the states that are also making changes to support eDiscovery.

By the way, since the Electronic Discovery Reference Model (EDRM) annual meeting back in May, several EDRM projects (Metrics, Jobs, Data Set and the new Native Files project) have already announced new deliverables and/or requested feedback.

When it comes to electronically stored information (ESI), ensuring proper chain of custody tracking is an important part of handling that ESI through the eDiscovery process.

Do you self-collect?  Don’t Forget to Check for Image Only Files!

The Files are Already Electronic, How Hard Can They Be to Load?  A sound process makes it easier.

When you remove a virus from your collection, does it violate your discovery agreement?

Do you think that you’ve read everything there is to read on Technology Assisted Review?  If you missed anything, it’s probably here.

Consider using a “SWOT” analysis or Decision Tree for better eDiscovery planning.

If you’re an eDiscovery professional, here is what you need to know about litigation.

BTW, eDiscovery Daily has had 242 posts related to eDiscovery Case Law since the blog began!  Forty-four of them have been in the last six months.

Our battle cry for next September?  “Four more years!”  🙂

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.