<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.ciolaw.org/~d/styles/rss2full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.ciolaw.org/~d/styles/itemcontent.css" type="text/css" media="screen"?><!-- generator="wordpress/2.3.3" --><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">

<channel>
	<title>CIOLaw - Legal Insight for the IT Executive</title>
	<link>http://www.ciolaw.org</link>
	<description>CIOLaw.org offers the IT executive a centralized, practical, easy-to-follow guide through the rapidly evolving world of electronically stored information (ESI) and the legal system. It is written with the non-lawyer in mind.</description>
	<pubDate>Fri, 18 Apr 2008 10:20:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
	<language>en</language>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.ciolaw.org/ciolaw" type="application/rss+xml" /><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Ffeeds.ciolaw.org%2Fciolaw" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Ffeeds.ciolaw.org%2Fciolaw" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Ffeeds.ciolaw.org%2Fciolaw" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.bloglines.com/sub/http://feeds.ciolaw.org/ciolaw" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://fusion.google.com/add?feedurl=http%3A%2F%2Ffeeds.ciolaw.org%2Fciolaw" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.live.com/?add=http%3A%2F%2Ffeeds.ciolaw.org%2Fciolaw" src="http://tkfiles.storage.msn.com/x1piYkpqHC_35nIp1gLE68-wvzLZO8iXl_JMledmJQXP-XTBOLfmQv4zhj4MhcWEJh_GtoBIiAl1Mjh-ndp9k47If7hTaFno0mxW9_i3p_5qQw">Subscribe with Live.com</feedburner:feedFlare><item>
		<title>All Relevant Employee ESI Must Be Disclosed</title>
		<link>http://www.ciolaw.org/esi/all-relevant-employee-esi-must-be-disclosed/</link>
		<comments>http://www.ciolaw.org/esi/all-relevant-employee-esi-must-be-disclosed/#comments</comments>
		<pubDate>Fri, 18 Apr 2008 10:20:12 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Electronically Stored Information]]></category>

		<category><![CDATA[Federal Rules of Civil Procedure]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/esi/all-relevant-employee-esi-must-be-disclosed/</guid>
		<description><![CDATA[As recently discussed on CIOLaw.org , when a litigation hold is triggered, it affects not only the email of a CEO of a company, but also all of the email and other ESI for relevant employees.
This same principle holds true for initial disclosures of ESI at the forefront of litigation, as discussed in the 2007 case [...]]]></description>
			<content:encoded><![CDATA[<p>As <a target="_blank" href="http://www.ciolaw.org/litigation-holds/litigation-hold-impacts-all-relevant-employees-not-just-ceo-or-executives">recently discussed on CIOLaw.org </a>, when a litigation hold is triggered, it affects not only the email of a CEO of a company, but also all of the email and other ESI for relevant employees.</p>
<p>This same principle holds true for initial disclosures of ESI at the forefront of litigation, as discussed in the 2007 case of <em>Metro Wastewater Reclamation District v. Alfa Laval, Inc</em>.</p>
<p>In this case, Alfa wanted to see all of the electronic files related to the plaintiff’s employees who worked on a project related to the litigation. The plaintiff complained that the request was “irrelevant, overly broad, overly burdensome, and costly.” In other words, not every employees’ ESI was necessary.</p>
<p>The court disagreed and required the disclosure of all the employees’ ESI. The Federal Rules of Civil Procedure favor a broad discovery of information, the court noted.</p>
<p>Consequently, not only did the plaintiff have to disclose all of the employees’ ESI, it had to pay for its retrieval. This can be a costly venture for an ill-prepared company.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/272797406" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/esi/all-relevant-employee-esi-must-be-disclosed/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Law Firm Sanctioned For Email Spoliation</title>
		<link>http://www.ciolaw.org/spoliation/law-firm-sanctioned-for-email-spoliation/</link>
		<comments>http://www.ciolaw.org/spoliation/law-firm-sanctioned-for-email-spoliation/#comments</comments>
		<pubDate>Fri, 18 Apr 2008 10:19:15 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Spoliation]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/spoliation/law-firm-sanctioned-for-email-spoliation/</guid>
		<description><![CDATA[In a recent court opinion from a sexual harassment lawsuit in Illinois, a judge recently entered sanctions against a law firm for failing to preserve email from one its partners.
The case, Wells v. Berger, Newmark &#38; Fenchel, involved explicit email that one of the law firm’s partners allegedly sent to Wells, a paralegal at the firm. [...]]]></description>
			<content:encoded><![CDATA[<p>In a recent court opinion from a sexual harassment lawsuit in Illinois, a judge recently entered sanctions against a law firm for failing to preserve email from one its partners.</p>
<p>The case, <em>Wells v. Berger, Newmark &amp; Fenchel</em>, involved explicit email that one of the law firm’s partners allegedly sent to Wells, a paralegal at the firm. The email would have been relevant to Wells’ claims.</p>
<p>The firm was notified about Wells’ allegations in December 2005. However, the firm took no steps to preserve the partner’s computer – or any email sent from it – until the spring of 2007. Consequently, an unknown number of email messages were lost.</p>
<blockquote><p>[The law firm partner] testified that he deleted all emails with sexual images on them. When [the partner’s] hard drive was finally searched, it yielded very little, and [the] computer consultant attested he could not determine how many files were permanently lost.</p></blockquote>
<p>The law firm tried to argue it did not have a duty to preserve the email. The court flatly refuted this argument, noting the initial investigation of Wells’ allegations by the Illinois Department of Human Rights specifically made specific mention of the offensive email messages in 2005.</p>
<p>Consequently, the court said it will read a statement to the jury that the law firm failed to preserve the email. Moreover, the law firm will be prohibited at trial from arguing that the absence of explicit email supports its argument that there was no harassment.</p>
<p>Courts consider it a serious problem when parties fail to preserve ESI after a litigation hold is in place. As a result, sanctions are often forthcoming. CIOs should always discuss with legal counsel any issues that may arise about a duty to preserve in order to avoid sanctions in subsequent litigation.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/272791088" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/spoliation/law-firm-sanctioned-for-email-spoliation/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Carefully Choose Search Protocol In Litigation</title>
		<link>http://www.ciolaw.org/reasonably-accessible/carefully-choose-search-protocol-in-litigation/</link>
		<comments>http://www.ciolaw.org/reasonably-accessible/carefully-choose-search-protocol-in-litigation/#comments</comments>
		<pubDate>Wed, 16 Apr 2008 11:25:04 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Cost Allocation]]></category>

		<category><![CDATA[Reasonably Accessible Information]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/reasonably-accessible/carefully-choose-search-protocol-in-litigation/</guid>
		<description><![CDATA[A recent decision by an Illinois federal magistrate highlights the importance of carefully identifying keywords when searching through electronically stored information (“ESI”) for litigation.
In Autotech Technologies Ltd v. AutomationDirect.Com, Inc., ADC sought ESI related to customer communications from Autotech. After an initial dispute, the parties agreed ADC could use a third-party consultant to search the database. [...]]]></description>
			<content:encoded><![CDATA[<p>A recent decision by an Illinois federal magistrate highlights the importance of carefully identifying keywords when searching through electronically stored information (“ESI”) for litigation.</p>
<p>In <em>Autotech Technologies Ltd v. AutomationDirect.Com, Inc</em>., ADC sought ESI related to customer communications from Autotech. After an initial dispute, the parties agreed ADC could use a third-party consultant to search the database. ADC crafted the keyword protocol.</p>
<p>After this search, the results produced approximately 10,000 pages. Autotech wanted ADC to come to its headquarters to review the documents. ADC wanted Autotech to produce everything under a <a target="_blank" href="http://www.ciolaw.org/esi/without-effective-email-archiving-clawback-and-quick-peek-agreements-may-be-only-options">clawback agreement </a>– an agreement that provided Autotech could “clawback” any ESI it determined was not relevant after it was produced.</p>
<p>Unable to resolve the dispute, the parties went back to court. The magistrate ordered Autotech to disclose the 10,000 pages.</p>
<p>After the first review, ADC determined the 10,000 pages did not contain all of the information it wanted. For example, the information did not include the name of the Autotech representative who talked to each customer.</p>
<blockquote><p>So the parties are back in court, with ADC asking that its consultant be allowed another crack at Autotech’s database.</p></blockquote>
<p>Autotech countered that it followed ADC’s keyword protocol during the first search. Consequently, the results reflected what ADC asked for.</p>
<p>ADC wanted to sanction Autotech for failing to disclose all of the relevant ESI.</p>
<p>In a March 25 opinion, the magistrate determined that ADC’s consultant could redo the original search to determine if some documents were excluded; however, the consultant could not do a “free-ranging search of the database to determine whether a different protocol will yield the information that ADC now seeks.”</p>
<p>As a result, if ADC’s initial keyword searches were deficient, then they are stuck with the responses. During litigation, the CIO and e-Discovery team must ensure the search of another side’s ESI is comprehensive. As ADC may learn the hard way, if the first search fails, there may not be a second chance.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/271362707" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/reasonably-accessible/carefully-choose-search-protocol-in-litigation/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Court Orders Inspection Of Hard Drive After Delays In ESI Disclosures</title>
		<link>http://www.ciolaw.org/esi/court-orders-inspection-of-hard-drive-after-delays-in-esi-disclosures/</link>
		<comments>http://www.ciolaw.org/esi/court-orders-inspection-of-hard-drive-after-delays-in-esi-disclosures/#comments</comments>
		<pubDate>Mon, 14 Apr 2008 11:53:16 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Electronically Stored Information]]></category>

		<category><![CDATA[Federal Rules of Civil Procedure]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/esi/court-orders-inspection-of-hard-drive-after-delays-in-esi-disclosures/</guid>
		<description><![CDATA[In a March 26 opinion, a Florida federal magistrate ordered a plaintiff to open up the computer hard drives of various employees so that the defendant could search for responsive email and other electronically stored information (“ESI”).
The plaintiff was also ordered to pay the attorney fees for the various motions to compel that the defendant [...]]]></description>
			<content:encoded><![CDATA[<p>In a March 26 opinion, a Florida federal magistrate ordered a plaintiff to open up the computer hard drives of various employees so that the defendant could search for responsive email and other electronically stored information (“ESI”).</p>
<p>The plaintiff was also ordered to pay the attorney fees for the various motions to compel that the defendant had to file before being granted access to the hard drives.</p>
<p>Since this is a case where the court had to intervene and order the defendant to open up certain computer hard drives, this case will likely be one of the more important e-Discovery decisions of early 2008.</p>
<p>In <em>U&amp;I Corporation v. Advanced Medical Design</em>, Korean-based U&amp;I filed a breach of contract case in October 2006 against American Medical for failing to pay a balance due for medical equipment. As part of the litigation, both sides sought various ESI, including email sent by U&amp;I employees.</p>
<p>After some haggling over what ESI should be disclosed, U&amp;I belatedly acknowledged that it could not retrieve email from 2004. U&amp;I explained that a “failure of the hard drive caused the 2004 e-mail account to be ‘unloadable’ or unretrievable.” U&amp;I agreed to produce email from 2003, 2005, 2006 and 2007.</p>
<p>However, American Medical discovered that not all of the 2005 and 2006 email was produced because when American Medical subpoenaed a third-party company, that company disclosed various email messages from U&amp;I employees that U&amp;I never disclosed.</p>
<p>In short, American Medical argued that U&amp;I delayed in telling American Medical that its 2004 email was not recoverable, and it failed to disclose all of the email from 2005 and 2006. American Medical sought sanctions.</p>
<p>In response, U&amp;I argued that – despite another company’s production of some email that U&amp;I did not disclose – there was no evidence that U&amp;I deliberately withheld ESI. U&amp;I also noted it disclosed approximately 14,500 documents. In addition, U&amp;I threw out a host of other excuses for failing to disclose all of its ESI, including “language barriers of its employees” and “confusion.”</p>
<p>In weighing the arguments, the court sided with American Medical.</p>
<blockquote><p>U&amp;I’s assertion that the delay in providing documents to American Medical was caused by the international travel requirements of its employees, server and software problems, confusion, language barriers of its employees and the lack of understanding of the American legal system does not excuse U&amp;I’s tardy and incomplete responses. After all, U&amp;I was the party which filed this lawsuit…At the outset of the litigation, U&amp;I and its counsel had the responsibility to take affirmative steps to ensure that all sources of discoverable information were identified, searched, and reviewed so that complete and timely responses to discovery requests could be provided.</p></blockquote>
<blockquote><p>It is not the court’s role, nor that of opposing counsel, to drag a party kicking and screaming through the discovery process. U&amp;I has failed to show substantial justification for its failure and unwillingness to abide by discovery rules and the court’s prior orders…</p></blockquote>
<p>Consequently, the court ordered U&amp;I to pay American Medical’s attorney fees for bringing the motion to compel. Moreover, the court ordered that American Medical be allowed to inspect the hard drives of certain U&amp;I employees in search for responsive ESI. A forensic examiner would conduct the search.</p>
<p>U&amp;I highlights the importance of maintaining a strong archiving system. When doubts are raised about whether a company has disclosed all of the relevant ESI, then courts are likely to step in and let the opposing side take a look for themselves.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/269973087" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/esi/court-orders-inspection-of-hard-drive-after-delays-in-esi-disclosures/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Archiving The Internet – One Snapshot At A Time</title>
		<link>http://www.ciolaw.org/esi/archiving-the-internet-%e2%80%93-one-snapshot-at-a-time/</link>
		<comments>http://www.ciolaw.org/esi/archiving-the-internet-%e2%80%93-one-snapshot-at-a-time/#comments</comments>
		<pubDate>Fri, 11 Apr 2008 15:29:00 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Electronically Stored Information]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/esi/archiving-the-internet-%e2%80%93-one-snapshot-at-a-time/</guid>
		<description><![CDATA[CIOs undoubtedly have a difficult job – managing a companywide ESI archive in a demanding e-Discovery world.
Now imagine having to archive everything on the Internet. Of course, no one can do it. But a multiplicity of Websites around the world are trying the next best thing:
By virtue of its shear enormity and its warp-speed evolution, [...]]]></description>
			<content:encoded><![CDATA[<p>CIOs undoubtedly have a difficult job – managing a companywide ESI archive in a demanding e-Discovery world.</p>
<p>Now imagine having to archive everything on the Internet. Of course, no one can do it. But a multiplicity of Websites around the world are trying the next best thing:</p>
<blockquote><p>By virtue of its shear enormity and its warp-speed evolution, the task of archiving the internet in its entirety is clearly impossible, like trying to catalog every grain of sand on the world&#8217;s beaches. But as it is easy to take a photograph of a beach, it also is possible to grab snapshots of the internet, or specific portions of it, to preserve for future generations.<br />
And that&#8217;s exactly what researchers at the Internet Archive, the Library of Congress, the National Archives and libraries worldwide are working on.</p></blockquote>
<blockquote><p>There have been some remarkable strides already, starting with the Mountain View, Calif.-based Internet Archive and its Wayback Machine, where its creator hopes to build a sort of second coming of the Library of Alexandria, the long-ago destroyed institution that housed much of the ancient world&#8217;s recorded knowledge.</p></blockquote>
<blockquote><p>The project has archived some 85 billion web pages on computers that measure data in unfathomably large quantities called petabytes.</p></blockquote>
<p>One petabyte, by the way, is the equivalent of approximately 20,000 personal computers with 50-gigabyte hard drives. It’s a lot of stuff.</p>
<p>Read the rest of this fun article <a target="_blank" href="http://blog.nj.com/digitallife/2008/03/some_of_todays_internet_wont_b.html">here in <em>The Star Ledger</em></a>.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/268436633" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/esi/archiving-the-internet-%e2%80%93-one-snapshot-at-a-time/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Purposeful Email Deletion Results In Sanctions and Scolding</title>
		<link>http://www.ciolaw.org/litigation-holds/purposeful-email-deletion-results-in-sanctions-and-scolding/</link>
		<comments>http://www.ciolaw.org/litigation-holds/purposeful-email-deletion-results-in-sanctions-and-scolding/#comments</comments>
		<pubDate>Fri, 11 Apr 2008 15:28:26 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Litigation Holds / Duty To Preserve]]></category>

		<category><![CDATA[Spoliation]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/litigation-holds/purposeful-email-deletion-results-in-sanctions-and-scolding/</guid>
		<description><![CDATA[When email is subpoenaed under the Federal Rules of Civil Procedure, the last thing an individual should do is delete the email and hope the whole mess goes away.
Nevertheless, that’s apparently what a former Texas district attorney did when he was subpoenaed for email from his office. As a result, the court on March 28 [...]]]></description>
			<content:encoded><![CDATA[<p>When email is subpoenaed under the Federal Rules of Civil Procedure, the last thing an individual should do is delete the email and hope the whole mess goes away.</p>
<p>Nevertheless, that’s apparently what a former Texas district attorney did when he was subpoenaed for email from his office. As a result, the court on March 28 held the former DA in contempt, fining him and calling all of his excuses “implausible.”</p>
<p>The case, <em>In re Rosenthal</em>, stems from a civil rights lawsuit in Texas. As part of the case, the plaintiffs sought email communications from Harris County District Attorney Charles Rosenthal to the Harris County Sheriff, among other officials.</p>
<p>At first, the county officials said they “fully complied” with the email request, noting of the 12,785 email messages retrieved during a search, only 61 were relevant to the case.</p>
<p>After more wrangling over what should be disclosed, the plaintiffs argued that not only did the county delay in producing email, but that Rosenthal purposely deleted 2,500 email messages that could no longer be recovered. Astonishingly, Rosenthal acknowledged he did delete the email after he was on notice to preserve the messages:</p>
<blockquote><p>The respondents admit that Rosenthal deleted e-mails that were the subject of the October 31 subpoena. However, they argue that he did not delete or attempt to delete all e-mails responsive to that subpoena. Rosenthal also asserts that he did not act in concert with the other respondents or seek help from anyone in deleting his e-mails. He contends that at the time that he deleted his e-mails, he believed them to be available for an indefinite period of time on back-up tapes maintained by Harris County Information Systems personnel. Further, Rosenthal contends that he committed error by deleting the e-mails only because he assumed that his counsel…had also printed a hard copy of each email.</p></blockquote>
<p>The court almost seemed baffled by the blatant disregard of court rules.</p>
<blockquote><p>At the outset, it is important to note that Rosenthal was familiar with the rules governing the discovery process…Indeed, during the relevant period, he was the District Attorney of Harris County, Texas with more than 40 years of legal experience.</p></blockquote>
<p>Rosenthal offered a host of hollow excuses: (1) thought there were existing hard copies, (2) thought they were permanently stored in the network’s back-up tapes, (3) wanted to reduce the “large volume of email visible” on his desktop, (4) wanted to be more efficient at work, and (5) wanted to free up memory space.</p>
<p>The court responded:</p>
<blockquote><p>There is no evidence that Rosenthal’s computer memory space was threatened by additional e-mails or that, in fact, it was short of space. Hence, these reasons – all implausible inconsistencies – defy the law of common sense…This conduct reveals a man confident in his status, entrenched in his brand of law. He would not or could not acknowledge an authority beyond himself. And, like the County Attorneys who appeared earlier in this case, Rosenthal reposes in the idolatry of their own perverted wisdom.</p></blockquote>
<p>Ultimately, the court held Rosenthal in contempt and monetarily sanctioned him. The court also sanctioned Rosenthal’s attorney representing him in the lawsuit, describing the attorney’s conduct “unprincipled and dilatory, at best, constituting a deliberate indifference” to the court’s orders.</p>
<p><a target="_blank" href="http://www.ciolaw.org/spoliation/lightning-lie-results-in-sanctions-for-spoliation-of-esi">Time and again </a>on CIOLaw.org, we’ve highlighted the dumb ways individuals try to outsmart the court system by deleting – or similarly throwing away – ESI. It never works.</p>
<p>CIOs should ensure they have an archiving system that reliably and effectively stores email and other ESI. Moreover, the system has to preclude rogue activity by end-users who may think it is better to delete email messages that they should preserve. It always backfires, even against former district attorneys.</p>
<p>Read another short post about this case and the court order itself at the terrific <a target="_blank" href="http://ridethelightning.senseient.com/2008/04/taking-lawyers.html">“ride the lightning” blog.</a></p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/268436634" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/litigation-holds/purposeful-email-deletion-results-in-sanctions-and-scolding/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Finding ESI Search Efforts Unclear, Court Requires More Discovery</title>
		<link>http://www.ciolaw.org/reasonably-accessible/finding-esi-search-efforts-unclear-court-requires-more-discovery/</link>
		<comments>http://www.ciolaw.org/reasonably-accessible/finding-esi-search-efforts-unclear-court-requires-more-discovery/#comments</comments>
		<pubDate>Fri, 04 Apr 2008 10:14:18 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Federal Rules of Civil Procedure]]></category>

		<category><![CDATA[Reasonably Accessible Information]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/reasonably-accessible/finding-esi-search-efforts-unclear-court-requires-more-discovery/</guid>
		<description><![CDATA[Under the Federal Rules of Civil Procedure (“FRCP”), parties must disclose relevant electronically stored information (“ESI”) unless that ESI is not reasonably accessible. In order to take advantage of this exception, a party has to be able to document the search protocol it implemented and why some sources are not reasonably accessible.
In short, a court [...]]]></description>
			<content:encoded><![CDATA[<p>Under the Federal Rules of Civil Procedure (“FRCP”), parties must disclose relevant electronically stored information (“ESI”) unless that ESI is not reasonably accessible. In order to take advantage of this exception, a party has to be able to document the search protocol it implemented and why some sources are not reasonably accessible.</p>
<p>In short, a court has to know exactly what has been searched and what has not. Moreover, the court has to agree there are good reasons that the ESI is not reasonably accessible.</p>
<p>If any of ESI-search information is unclear, then the court will require further discovery, as a federal magistrate in New York recently did in <em>Baker v. Gerould</em>.</p>
<p>In a March 27 opinion, the court expressed frustration with the lack of information presented by defendants on the efforts to retrieve ESI:</p>
<blockquote><p>As noted by this Court during oral argument, insufficient information had been presented at that time to determine the adequacy of defendants’ search for the requested emails from accessible sources. Regrettably, the record is no more fully developed now than it was then. Although it is clear that some email communications have been turned over, the source or sources of those communications is not clear. For example, it is unknown whether those emails were recovered from existing hard drives, backup hard drives or traditional files used to maintain paper records. It is likewise unknown whether computer and/or paper files have been searched for all defendants, some of whom are no longer employed…but some of whom are.</p></blockquote>
<p>Consequently, the court ordered the defendants to identify in writing all of the people who conducted the search. Following those identifications, the plaintiff would be allowed to depose those individuals to investigate the search. After all of that, then the court could determine whether the defendants properly responded to the ESI requests or whether more ESI – including restoration of backup tapes – was necessary.</p>
<p>Equally important to cost-effective retrieval of ESI is the ability to document exactly the steps taken during an ESI search and to sufficiently offer valid reasons why some ESI is not reasonably accessible.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/263891789" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/reasonably-accessible/finding-esi-search-efforts-unclear-court-requires-more-discovery/feed/</wfw:commentRss>
		</item>
		<item>
		<title>New Article Explores Metadata</title>
		<link>http://www.ciolaw.org/metadata/new-article-explores-metadata/</link>
		<comments>http://www.ciolaw.org/metadata/new-article-explores-metadata/#comments</comments>
		<pubDate>Fri, 04 Apr 2008 10:11:31 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Metadata]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/metadata/new-article-explores-metadata/</guid>
		<description><![CDATA[A newly published article offers a comprehensive examination of metadata. The article offers insight into different types of metadata, and discusses case law about it used in court. The article even addresses the first important metadata case:
Perhaps the first case to appreciate the importance of metadata was [the 1993 case of] Armstrong v. Executive Office of the [...]]]></description>
			<content:encoded><![CDATA[<p>A newly published article offers a comprehensive examination of <a target="_blank" href="http://www.ciolaw.org/metadata/if-i-am-sued-do-i-have-disclose-my-metadata/">metadata</a>. The article offers insight into different types of metadata, and discusses case law about it used in court. The article even addresses the first important metadata case:</p>
<blockquote><p>Perhaps the first case to appreciate the importance of metadata was [the 1993 case of] Armstrong v. Executive Office of the President. In Armstrong, the court decided that paper copies of electronic mail did not qualify as an “extra copy” for purposes of the Federal Records Act, which would allow the originals to be destroyed, “because important information present in the email system, such as who sent a document, who received it, and when that person received it, will not always appear on the computer screen and so will not be preserved on the paper print-out.” Although not explicitly referring to this type of information as “metadata,” the Armstrong court clearly recognized that its value warranted preservation.</p></blockquote>
<p>Read the <a target="_blank" href="http://law.richmond.edu/jolt/v14i3/article10.pdf">entire article in the Richmond Journal of Law and Technology here</a>.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/263891791" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/metadata/new-article-explores-metadata/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Suspicious Email Results In Dismissal Of Employee’s Claims</title>
		<link>http://www.ciolaw.org/esi/suspicious-email-results-in-dismissal-of-employee%e2%80%99s-claims/</link>
		<comments>http://www.ciolaw.org/esi/suspicious-email-results-in-dismissal-of-employee%e2%80%99s-claims/#comments</comments>
		<pubDate>Thu, 03 Apr 2008 11:21:44 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Electronically Stored Information]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/esi/suspicious-email-results-in-dismissal-of-employee%e2%80%99s-claims/</guid>
		<description><![CDATA[In an employment discrimination lawsuit in New York, a printed-out copy of an alleged “smoking gun” email message took center stage when its authenticity was called into doubt.
The case, Bell v. Rochester Gas &#38; Electric Corp., involves Bell’s claim that he was illegally fired from the company Energetix because of his race. As part of [...]]]></description>
			<content:encoded><![CDATA[<p>In an employment discrimination lawsuit in New York, a printed-out copy of an alleged “smoking gun” email message took center stage when its authenticity was called into doubt.</p>
<p>The case, <em>Bell v. Rochester Gas &amp; Electric Corp</em>., involves Bell’s claim that he was illegally fired from the company Energetix because of his race. As part of his proof, Bell provided the court with an alleged hard copy of an email message. The hard copy was allegedly found either “weeks or months” after Bell’s termination by another employee within a stack of recently printed papers.</p>
<p>The email, purportedly written by Bell’s supervisor to another supervisor, contained racist statements about Bell’s firing. The supervisors denied ever writing or receiving the email. Energetix investigated the alleged email, as described in the March 26 court opinion:</p>
<blockquote><p>Energetix conducted an internal investigation to determine whether [the email] had originated there. After a search [of the supervisors’] hard drives gave no indication that the message had ever been sent, received, stored, deleted or printed from their e-mail files, Energetix retained the services [of an outside vendor] to restore backup tapes of its e-mail server and search for electronic copies of the message between April 2002 and December 2002.</p></blockquote>
<p>Again, nothing turned up. Energetix then hired another vendor to analyze the hard drives of the supervisors.</p>
<blockquote><p>Despite these efforts, neither Energetix nor the two outside firms were able to find any evidence that the purported e-mail was ever written, sent, received or printed…</p></blockquote>
<p>Bell argued that the email, which was marked as sent on May 21, 2002, was completely obliterated from the company’s servers before the implementation of backup tapes on June 2, 2002.</p>
<p>In a Sherlock Holmes-twist of logic, the court rejected Bell’s argument:</p>
<blockquote><p>[O]ne need not be an expert in the field of computer forensics to recognize that if the e-mail had been sent by [one supervisor] on May 21, 2002 but deleted and overwritten at some point within the next twelve days to eradicate any trace of its existence such that it would not appear on any of the named defendants’ hard drives or Energetix’s daily backup tape for June 2, 2002, it would have been impossible…to have printed it…weeks or months after May 21, 2002, when [the other employee] allegedly discovered it, commingled with papers she had just printed and removed from a copier the previous day.</p></blockquote>
<p>Taking all of the evidence as a whole, including evidence that Bell tampered with Energetix’s computer systems over billing, the court ruled there was sufficient evidence that Energetix fired Bell for non-discriminatory reasons. It dismissed Bell’s claims.</p>
<p>Although the court never directly called Bell’s email a fraud, it did note the ease with which email messages can be faked:</p>
<blockquote><p>It is undisputed that e-mail messages can be easily fabricated, and a host of websites offer software and instructions for creating and/or sending faux e-mails…As such, a practical understanding of the available technology, both with respect to the fabrication of e-mails, and their preservation through electronic data, dictates that authentication of a printout as the hardcopy of a bona fide e-mail message now requires something more than a bar conclusion that the printout ‘appears to be’ an e-mail message.</p></blockquote>
<p>Obviously, companies that have implemented effective and objective archiving systems have little fear of forged email messages since they can easily detect which email messages were sent or received within the system.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/263279813" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/esi/suspicious-email-results-in-dismissal-of-employee%e2%80%99s-claims/feed/</wfw:commentRss>
		</item>
		<item>
		<title>New Opinion Illustrates How Quickly ESI Issues May Proceed in Court</title>
		<link>http://www.ciolaw.org/esi/new-opinion-illustrates-how-quickly-esi-issues-may-proceed-in-court/</link>
		<comments>http://www.ciolaw.org/esi/new-opinion-illustrates-how-quickly-esi-issues-may-proceed-in-court/#comments</comments>
		<pubDate>Wed, 02 Apr 2008 10:48:18 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Electronically Stored Information]]></category>

		<category><![CDATA[Federal Rules of Civil Procedure]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/esi/new-opinion-illustrates-how-quickly-esi-issues-may-proceed-in-court/</guid>
		<description><![CDATA[In a court opinion from March, a federal magistrate ordered an expedited forensic imaging of computers relevant to the litigation. In fact, within two days of the March 17 order, the computer servers and other electronic storage devices, including one employee’s laptop, were to be made available to a forensic examiner to make mirror images of [...]]]></description>
			<content:encoded><![CDATA[<p>In a court opinion from March, a federal magistrate ordered an expedited forensic imaging of computers relevant to the litigation. In fact, within two days of the March 17 order, the computer servers and other electronic storage devices, including one employee’s laptop, were to be made available to a forensic examiner to make mirror images of the devices.</p>
<p>In the case, <em>XPEL Technologies Corp. v. American Filter Film Distributors</em>, XPEL worried that electronically stored information (“ESI”) could be altered or destroyed just by the day-to-day activities of the defendants’ computer use unless an expedited order permitted an immediate imaging of the computers. XPEL believes most of the relevant ESI was in metadata and other deleted – but still retrievable – files.</p>
<p>The court agreed to expedite the imaging, and it named a forensic examiner to move quickly to copy the servers. In addition, the court ordered that XPEL would pay for the costs of the forensic examiner, explaining:</p>
<blockquote><p>The forensic images shall be copied and retained by the Forensic Examiner until such time the court or both parties request the destruction of the forensic image files.</p></blockquote>
<blockquote><p>The Forensic Examiner will maintain all mirrored images and do so in the strictest confidence, and not disclose any information obtained to unauthorized persons.</p></blockquote>
<p>With this case as persuasive precedent, parties may more frequently seek to immediately make mirror images of opponents’ servers.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/262580028" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/esi/new-opinion-illustrates-how-quickly-esi-issues-may-proceed-in-court/feed/</wfw:commentRss>
		</item>
		<item>
		<title>DaimlerChrysler Faces Claims Of Spoliation Of ESI</title>
		<link>http://www.ciolaw.org/litigation-holds/daimlerchrysler-faces-claims-of-spoliation-of-esi/</link>
		<comments>http://www.ciolaw.org/litigation-holds/daimlerchrysler-faces-claims-of-spoliation-of-esi/#comments</comments>
		<pubDate>Tue, 01 Apr 2008 11:30:31 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Litigation Holds / Duty To Preserve]]></category>

		<category><![CDATA[Spoliation]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/litigation-holds/daimlerchrysler-faces-claims-of-spoliation-of-esi/</guid>
		<description><![CDATA[A federal judge ruled in March that a plaintiff may bring spoliation claims against DaimlerChrysler Motors Company since the giant automobile manufacturer failed to implement a legal hold.
The case, Schmidt Pontiac-GMC Truck, Inc. v. DaimlerChrysler Motors Company, involves a breach of contract case. Essentially, Schmidt claims DaimlerChrysler breached a settlement agreement to let Schmidt open [...]]]></description>
			<content:encoded><![CDATA[<p>A federal judge ruled in March that a plaintiff may bring spoliation claims against DaimlerChrysler Motors Company since the giant automobile manufacturer failed to implement a legal hold.</p>
<p>The case, <em>Schmidt Pontiac-GMC Truck, Inc. v. DaimlerChrysler Motors Company</em>, involves a breach of contract case. Essentially, Schmidt claims DaimlerChrysler breached a settlement agreement to let Schmidt open a Chrysler franchise.</p>
<p>Schmidt filed a lawsuit in 2004. At that time, DaimlerChrysler would have been under a duty to preserve all relevant electronically stored information (“ESI”).</p>
<p>During discovery of the litigation, Schmidt learned DaimlerChrysler had not preserved ESI. Schmidt filed a motion with the court to add a claim of spoliation against DaimlerChrysler. This is called a Motion To Amend. Schmidt alleged:</p>
<blockquote><p>DaimlerChrysler (1) failed to implement a litigation hold to prevent the destruction of evidence after the complaint was filed…and (2) intentionally destroyed evidence, including replacing employee hard drives.</p></blockquote>
<p>The court agreed with Schmidt, explaining that if DaimlerChrysler altered or replaced hard drives, then that would impact Schmidt’s ability to prove its case. Consequently, Schmidt is permitted to amend the initial complaint to add a claim for spoliation of evidence.</p>
<blockquote><p>There has been, and probably will continue to be, discovery as to the destruction of evidence for the purposes of the adverse inference instruction. Any evidence developed in that regard might become known to the jury as a predicate for an adverse inference instruction.</p></blockquote>
<p><a target="_blank" href="http://www.ciolaw.org/litigation-holds/be-ready-for-legal-holds">Legal holds </a>are crucial to avoid spoliation claims. CIOs must consult with legal counsel if ever any issues arise that might require preservation of ESI.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/261903843" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/litigation-holds/daimlerchrysler-faces-claims-of-spoliation-of-esi/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Court Sides With The Terminator In ESI Dispute</title>
		<link>http://www.ciolaw.org/esi/court-sides-with-the-terminator-in-esi-dispute/</link>
		<comments>http://www.ciolaw.org/esi/court-sides-with-the-terminator-in-esi-dispute/#comments</comments>
		<pubDate>Tue, 01 Apr 2008 11:27:40 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Electronically Stored Information]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/esi/court-sides-with-the-terminator-in-esi-dispute/</guid>
		<description><![CDATA[In a class action lawsuit involving California Gov. Arnold Schwarzenegger, a federal magistrate sided with Schwarzenegger in denying plaintiffs&#8217; request to observe computer databases.
The lawsuit, L.H. v. Schwarzenegger, is a class action involving juvenile parolees suing California over the parole revocation process. Schwarzenegger, as governor, is one of the named defendants.
The plaintiffs wanted the defendants to [...]]]></description>
			<content:encoded><![CDATA[<p>In a class action lawsuit involving California Gov. Arnold Schwarzenegger, a federal magistrate sided with Schwarzenegger in denying plaintiffs&#8217; request to observe computer databases.</p>
<p>The lawsuit, <em>L.H. v. Schwarzenegger</em>, is a class action involving juvenile parolees suing California over the parole revocation process. Schwarzenegger, as governor, is one of the named defendants.</p>
<p>The plaintiffs wanted the defendants to demonstrate the capabilities of the Ward Information Network (WIN) and the Offender Based Information Tracking System (OBITS), both of which are relevant to the litigation. Moreover, the plaintiffs wanted a list of scheduled trainings and to attend the trainings for the use of those two systems.</p>
<p>The magistrate on March 20 denied the request, explaining other means were available to obtain the same information. For example, the plaintiffs could ask an official from the state during a deposition about how the systems work.</p>
<p>Consequently, the defendants do not have to perform a demonstration of the systems. On hearing the news, Schwarzenegger reportedly said: “Hasta La Vista, Baby.”</p>
<p>Plaintiffs, however, did win a smaller ESI victory. The magistrate ordered certain electronically stored information in databases – such as ESI relating to appeals of parole revocation – to be disclosed to the extent the defendants had not already turned it over.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/261903844" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/esi/court-sides-with-the-terminator-in-esi-dispute/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Lightning Lie Results In Sanctions For Spoliation Of ESI</title>
		<link>http://www.ciolaw.org/spoliation/lightning-lie-results-in-sanctions-for-spoliation-of-esi/</link>
		<comments>http://www.ciolaw.org/spoliation/lightning-lie-results-in-sanctions-for-spoliation-of-esi/#comments</comments>
		<pubDate>Mon, 31 Mar 2008 10:25:05 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Spoliation]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/spoliation/lightning-lie-results-in-sanctions-for-spoliation-of-esi/</guid>
		<description><![CDATA[As noted here and here on CIOLaw.org, it is never a good idea to try to destroy ESI after a legal hold is triggered creating a duty to preserve the information. Here’s is another example of why:
In Great American Ins. Co. of New York v. Lowry Development, the insurance company Great American wanted to see the [...]]]></description>
			<content:encoded><![CDATA[<p>As noted <a target="_blank" href="http://www.ciolaw.org/spoliation/throwing-computer-in-dumpster-not-way-to-handle-e-discovery">here</a> and <a target="_blank" href="http://www.ciolaw.org/spoliation/hiding-smoking-gun-esi-worsens-impact">here</a> on CIOLaw.org, it is never a good idea to try to destroy ESI after a legal hold is triggered creating a duty to preserve the information. Here’s is another example of why:</p>
<p>In <em>Great American Ins. Co. of New York v. Lowry Development</em>, the insurance company Great American wanted to see the personal computer files of Danny Groves, who operated Groves &amp; Associates, which was a party in the litigation. Groves used his personal computer for business correspondence, including sending email, to the insurance company.</p>
<p>At first, Groves said lightning had damaged his computer and it was not repairable. As a result, he said, he just abandoned it with the technician.</p>
<p>Later, apparently forgetting his first response, Groves said he had the computer, but that the motherboard was damaged by lightning and a computer technician told him that all of the files were lost.</p>
<p>The insurance company did the obvious: it called the computer technician. The technician swore in an affidavit that he was able to fix the computer and none of the files were lost.</p>
<p>In response, Groves said what he really did was throw the computer away after it malfunctioned a second time following the repair from the lightning strike. Needless to say, the court had a hard time believing him:</p>
<blockquote><p>Groves offers no explanation for his untruthful testimony or for his inaccurate and incomplete response to Great American’s request for inspection…I am of the opinion that Great American has established, by clear and convincing evidence, that the destruction of this computer has deprived the parties and the Court of the benefit of any records that may have been contained in the computer hard drive.</p></blockquote>
<p>Consequently, the court said it would read an adverse inference instruction at trial and lower the burden of proof for Great American on one of its claims.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/261196090" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/spoliation/lightning-lie-results-in-sanctions-for-spoliation-of-esi/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Court Considering Sanctions Against USDA For ESI Spoliation</title>
		<link>http://www.ciolaw.org/spoliation/court-considering-sanctions-against-usda-for-esi-spoliation/</link>
		<comments>http://www.ciolaw.org/spoliation/court-considering-sanctions-against-usda-for-esi-spoliation/#comments</comments>
		<pubDate>Fri, 28 Mar 2008 12:07:45 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Spoliation]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/spoliation/court-considering-sanctions-against-usda-for-esi-spoliation/</guid>
		<description><![CDATA[In a decision this month, a district court has indicated it may sanction the U.S. Department of Agriculture for failing to preserve electronically stored information (“ESI”).
In Consumer Federation of America v. U.S. Dep’t of Agriculture, the CFA requested in 2004 copies of official calendars – including related ESI – maintained by certain USDA officials. The [...]]]></description>
			<content:encoded><![CDATA[<p>In a decision this month, a district court has indicated it may sanction the U.S. Department of Agriculture for failing to preserve electronically stored information (“ESI”).</p>
<p>In <em>Consumer Federation of America v. U.S. Dep’t of Agriculture</em>, the CFA requested in 2004 copies of official calendars – including related ESI – maintained by certain USDA officials. The USDA at first refused, but then was ordered to produce the information in 2006 by the Court of Appeals for the District of Columbia.</p>
<p>However, the USDA never implemented a legal hold until after the 2006 order. Consequently, ESI related to the request was never archived and it was overwritten before it could be produced to the CFA.</p>
<p>The court observed:</p>
<blockquote><p>In this case, it is clear that defendant’s initial searches were inadequate. Indeed, counsel for the defendant acknowledged during oral argument that the documents in this case were ‘not handled in the way they should have been…[However] the defendant has [subsequently] conducted – albeit belatedly – a search reasonably calculated to under all relevant documents…</p></blockquote>
<p>Nevertheless, it appears some ESI is irretrievably lost. As a result, the court is considering sanctions against the USDA:</p>
<blockquote><p>In view of defendant’s acknowledgement during oral argument that its search was not handled as well as it might have been, and in order to ensure that defendant carries out future FOIA searches responsibly from the outset, the Court directs defendant to file a supplemental declaration detailing: (1) the specific steps the agency will take when responding to a FOIA request, particularly one including electronic documents; and (2) the steps, if any, the agency has taken to correct the problems that led to the loss of responsive documents in this case.</p></blockquote>
<p>The USDA has until April 30 to file its supplemental pleading with the court.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/259600525" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/spoliation/court-considering-sanctions-against-usda-for-esi-spoliation/feed/</wfw:commentRss>
		</item>
		<item>
		<title>AMD v. Intel Part Three:  Costly Remediation In Restoring Lost Email And Other ESI</title>
		<link>http://www.ciolaw.org/spoliation/amd-v-intel-part-three-costly-remediation-in-restoring-lost-email-and-other-esi/</link>
		<comments>http://www.ciolaw.org/spoliation/amd-v-intel-part-three-costly-remediation-in-restoring-lost-email-and-other-esi/#comments</comments>
		<pubDate>Fri, 28 Mar 2008 12:04:34 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Spoliation]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/spoliation/amd-v-intel-part-three-costly-remediation-in-restoring-lost-email-and-other-esi/</guid>
		<description><![CDATA[Read Part One in this three-part series about the ongoing AMD v. Intel litigation.  
Read Part Two here.   
In this third part, we look at the ways Intel proposed to restore the missing ESI, including the multimillion dollar remediation plan.
By the time Intel filed it Remediation Plan to recover lost email, it estimated it had already [...]]]></description>
			<content:encoded><![CDATA[<p><em>Read </em><a target="_blank" href="http://www.ciolaw.org/litigation-holds/amd-v-intel-part-one-a-look-at-the-%e2%80%98largest-electronic-production-in-history%e2%80%99/"><em>Part One </em></a><em>in this three-part series about the ongoing AMD v. Intel litigation.  </em></p>
<p><em>Read </em><em><a target="_blank" href="http://www.ciolaw.org/litigation-holds/amd-v-intel-part-two-the-mistakes-made-and-the-data-lost/">Part Two </a></em><em><a target="_blank" href="http://www.ciolaw.org/litigation-holds/amd-v-intel-part-two-the-mistakes-made-and-the-data-lost/">here. </a>  </em></p>
<p><em>In this third part, we look at the ways Intel proposed to restore the missing ESI, including the multimillion dollar remediation plan.</em></p>
<p>By the time Intel filed it Remediation Plan to recover lost email, it estimated it had already spent approximately $3.3 million in outside vendor costs in its efforts to restore back-up tapes. Intel estimated it would spend “millions more” to complete all of the remediation.</p>
<p>According to Intel’s Remediation Plan:</p>
<blockquote><p>Intel is cataloging, indexing and, to the extent appropriate, restoring thousands of backup tapes. Intel is willing to undertake this massive effort because it regrets the lapse in its retention practices, wants to set them right, and wishes to get the case back on the path to being resolved on the merits.</p></blockquote>
<p>Intel is relying on “complaint freeze tapes” and “weekly backup tapes” in its efforts to restore as much of the data as possible. Intel concedes, however, that not all of the information lost due to the problems with the litigation hold will be retrieved.</p>
<p>In its efforts to avoid sanctions, Intel proposed the following remediation:</p>
<blockquote><p>It re-issued its litigation hold notice, and will send out reminders every six months</p></blockquote>
<blockquote><p>Intel is also calling by telephone all 1,023 custodians to verbally remind them of the litigation hold</p></blockquote>
<blockquote><p>The legal department will have the say-so over whether any laptops in the future can be scrubbed</p></blockquote>
<blockquote><p>Intel will harvest and re-harvest all ESI from custodians working for Intel</p></blockquote>
<blockquote><p>Intel utilized an email archive company to capture all of the email from the custodians as a way to retain all relevant email</p></blockquote>
<p>AMD has argued that Intel has not been forthright about the amount of data lost; however, AMD supported Intel’s decision to move ahead with its remediation plan.</p>
<p>No final cost is determined, but it will likely be in the tens of millions. Intel describes it as a “perhaps unprecedented” amount of resources to implement the Remediation Plan. AMD argues no matter how much Intel spends, that’s not an indicator of how much was lost because some data will be irretrievably gone.</p>
<p>AMD has said:  </p>
<blockquote><p>Any honest assessment of this fiasco requires Intel to acknowledge that it cannot remediate the irremediable.</p></blockquote>
<p>The court approved Intel’s plan on October 22, 2007.</p>
<p>Potential sanctions from the court – including a spoliation finding – still loom, despite Intel&#8217;s efforts to restore the data. In the court’s order approving the Remediation Plan, the court states:</p>
<blockquote><p>(A)lthough [plaintiffs] acknowledge that Intel’s Proposed Remediation Plan contains all elements that should reasonably be required of Intel under the circumstances to remediate its documents preservation lapses, Plaintiffs do not acknowledge or concede that Intel’s Proposed Remediation Plan, even if fully executed, will effectively or substantially remediate Intel’s lapses, and for which lapses Plaintiffs specifically reserve the right to seek sanction.</p></blockquote>
<p>In short, after discovery ends, AMD may – likely will – move for sanctions against Intel, including asking for an adverse inference instruction to be given to the jury. As has been forewarned by the <a target="_blank" href="http://www.ciolaw.org/spoliation/unwrapping-zubulake-%e2%80%93-part-i/"><em>Zubulake</em> case</a>, an adverse jury instruction could result in a multimillion dollar verdict. That remains to be seen for <em>AMD v. Intel</em>.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/259600527" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/spoliation/amd-v-intel-part-three-costly-remediation-in-restoring-lost-email-and-other-esi/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Sanctions For Failing To Disclose ‘Unstripped’ ESI, But Not For Deleting ‘Smoking Gun’ Email</title>
		<link>http://www.ciolaw.org/esi/sanctions-for-failing-to-disclose-%e2%80%98unstripped%e2%80%99-esi-but-not-for-deleting-%e2%80%98smoking-gun%e2%80%99-email/</link>
		<comments>http://www.ciolaw.org/esi/sanctions-for-failing-to-disclose-%e2%80%98unstripped%e2%80%99-esi-but-not-for-deleting-%e2%80%98smoking-gun%e2%80%99-email/#comments</comments>
		<pubDate>Thu, 27 Mar 2008 12:00:52 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Electronically Stored Information]]></category>

		<category><![CDATA[Spoliation]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/esi/sanctions-for-failing-to-disclose-%e2%80%98unstripped%e2%80%99-esi-but-not-for-deleting-%e2%80%98smoking-gun%e2%80%99-email/</guid>
		<description><![CDATA[In an ongoing intellectual property lawsuit between ClearOne Communications and WideBand Solutions, the judge was recently faced with two e-Discovery issues: (1) should he sanction WideBand for failing to disclose a “smoking gun” email, and (2) should he sanction WideBand for only disclosing a stripped version of a source code when ClearOne had requested another [...]]]></description>
			<content:encoded><![CDATA[<p>In an ongoing intellectual property lawsuit between ClearOne Communications and WideBand Solutions, the judge was recently faced with two e-Discovery issues: (1) should he sanction WideBand for failing to disclose a “smoking gun” email, and (2) should he sanction WideBand for only disclosing a stripped version of a source code when ClearOne had requested another version of source code with comments.</p>
<p>In the end, the court sanctioned WideBand for misrepresenting it did not have a source code with comments. The court ordered an adverse inference instruction.</p>
<p>The court did not sanction WideBand for failing to disclose the “smoking gun” email. The court reasoned that since the email was automatically deleted from the company’s “sent” folders as part of its routine retention policy, then sanctions were not warranted. However, the court did describe this type of retention policy as a “significant irregularity” and “questionable.”</p>
<p><strong>Here’s a more detailed rundown of the e-Discovery issues:</strong></p>
<p>First, ClearOne sought a sanction against WideBand for failing to disclose an email sent by WideBand’s founder that was relevant to the litigation. The email surfaced when the company that received it disclosed the email in litigation. WideBand said the email had been automatically deleted from its system as part of its policy not to retain any items in the “sent” folder.</p>
<p>The court found WideBand’s deletion policy unusual:</p>
<blockquote>
<p align="left">For any business this is a significant irregularity; almost unimaginable for a technology company; and even more unlikely for a person of [the founder’s] importance in such a company.</p>
</blockquote>
<p>However, since WideBand followed its routine policy in good faith, then the court opted not to sanction the company since it was not under a duty to preserve that email right after it was sent.</p>
<p>Second, ClearOne accused WideBand of stripping comments from source code that WideBand had provided to another party. The source code was at the heart of the infringement litigation.</p>
<p>ClearOne wanted “any and all versions, derivatives, and forms of the computer code.” WideBand only disclosed a stripped version of the code.</p>
<blockquote><p>Of course, as it was discovered at the end of May, there was another copy of the source code and it does contain comments. Very shortly after this discovery, the source code with comments was provided to ClearOne.</p></blockquote>
<p>During a deposition, a WideBand representative failed to disclose there existed a source code with comments, even though he was asked about it. As a result, the court ordered an adverse inference instruction against WideBand.</p>
<blockquote><p>This is a serious remedy for a serious situation. It is not dispositive or case-terminating remedy, but it is significant. Such a jury instruction will have a considerable impact on the jury.</p></blockquote>
<p>Read an <a target="_blank" href="http://www.ediscoverylaw.com/2008/03/articles/case-summaries/no-sanctions-warranted-for-failure-to-produce-smoking-gun-email-where-email-system-did-not-retain-any-sent-emails">analysis of the case and the court’s opinion here</a>.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/258935652" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/esi/sanctions-for-failing-to-disclose-%e2%80%98unstripped%e2%80%99-esi-but-not-for-deleting-%e2%80%98smoking-gun%e2%80%99-email/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Court Rules ESI Records Kept Past Statute Of Limitations Still Have To Be Disclosed</title>
		<link>http://www.ciolaw.org/esi/court-rules-esi-records-kept-past-statute-of-limitations-still-have-to-be-disclosed/</link>
		<comments>http://www.ciolaw.org/esi/court-rules-esi-records-kept-past-statute-of-limitations-still-have-to-be-disclosed/#comments</comments>
		<pubDate>Wed, 26 Mar 2008 11:39:34 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Electronically Stored Information]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/esi/court-rules-esi-records-kept-past-statute-of-limitations-still-have-to-be-disclosed/</guid>
		<description><![CDATA[A court recently ordered a company to disclose old employee records even though the statute of limitations – a time period in which a lawsuit may be filed related to those records – had expired.
This is an illustrative case that shows if a company has records – including ESI – within its possession, and those records [...]]]></description>
			<content:encoded><![CDATA[<p>A court recently ordered a company to disclose old employee records even though the statute of limitations – a time period in which a lawsuit may be filed related to those records – had expired.</p>
<p>This is an illustrative case that shows if a company has records – including ESI – within its possession, and those records are relevant to litigation, then the records will have to be disclosed even if the law would have permitted destroying those records earlier.</p>
<p>In <em>Thong v. Andre Chreky Salon</em>, a Fair Labor Standards Act (FLSA) lawsuit filed in 2006, the employee wanted time cards, work schedules, notes and any other reports dating back to 1998. The employer, who had disclosed payroll records, objected to going back for the other records. The employer argued that going back to 1998 was too far. The statute of limitations to bring a claim under the FLSA is three years. Essentially, the employer said it should not have to provide documents past 2003.</p>
<p>The court disagreed in an opinion rendered earlier this year:</p>
<blockquote><p>This Court finds that the request is reasonably calculated to lead to admissible evidence related to matters other than the alleged FLSA violations, including plaintiff’s claim that Mr. Chreky reduced plaintiff’s work schedule as a form of punishment for resisting his alleged sexual advances.<br />
…<br />
To the extent that defendants have within their possession, custody or control documents – other than payroll records and time cards previously produced – evidencing hours worked, this Court shall order defendants to provide such documents to plaintiff. If, in fact, defendants have no additional documents responsive to Request No. 19, this Court shall require defendants to provide an amended, verified discovery response stating that fact.</p></blockquote>
<p>In short, even though the company could have destroyed those documents and deleted ESI under the law, when it decided to retain the information, then that information became open for disclosure in litigation. CIOs should consider the implications about unnecessarily retaining ESI for too long.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/258260499" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/esi/court-rules-esi-records-kept-past-statute-of-limitations-still-have-to-be-disclosed/feed/</wfw:commentRss>
		</item>
		<item>
		<title>If Relevance Of ESI On Backup Tapes Is Unclear, Court May Adopt Phased Restoration</title>
		<link>http://www.ciolaw.org/reasonably-accessible/if-relevance-of-esi-on-backup-tapes-is-unclear-court-may-adopt-phased-restoration/</link>
		<comments>http://www.ciolaw.org/reasonably-accessible/if-relevance-of-esi-on-backup-tapes-is-unclear-court-may-adopt-phased-restoration/#comments</comments>
		<pubDate>Tue, 25 Mar 2008 11:29:21 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Reasonably Accessible Information]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/reasonably-accessible/if-relevance-of-esi-on-backup-tapes-is-unclear-court-may-adopt-phased-restoration/</guid>
		<description><![CDATA[Companies that have archived electronically stored information (“ESI”) on backup tapes may face the costly consequence of having to restore those tapes if needed for litigation.
Generally, under the Federal Rules of Civil Procedure, ESI that is not “reasonably accessible” does not have to be restored and disclosed unless the other side can show good cause.
A [...]]]></description>
			<content:encoded><![CDATA[<p>Companies that have archived electronically stored information (“ESI”) on backup tapes may face the costly consequence of having to restore those tapes if needed for litigation.</p>
<p>Generally, under the Federal Rules of Civil Procedure, ESI that is not “reasonably accessible” does not have to be restored and disclosed unless the other side can show good cause.</p>
<p>A problem emerges when it is unclear exactly what ESI is stored on the backup tapes. Neither side wants to pay for a full restoration only to discover the email on the backup tapes has no bearing on the litigation. On the flip side, if there is relevant ESI and it should be disclosed, then the court will want those backup tapes restored.</p>
<p>One solution courts have implemented is a phased restoration of certain tapes. This happened in <em>AAB Joint Venture v. United States</em> last year.</p>
<p>In this case, involving a contractor suing the Government, the contractor wanted the Government to restore email from backup tapes that were believed to be relevant to the litigation. During the course of the legal discovery, it was unclear whether the government improperly allowed some email to be deleted that should have been preserved.</p>
<p>The Government acknowledged some relevant email may be on the backup tapes. However, the Government complained the restoration was too costly compared to the benefits of any email retrieved.</p>
<p>The court was faced with two questions: (1) should the tapes be restored? and (2) who pays for it if they should?</p>
<p>In the end, the court decided a sample of the backup tapes – picked out by the contractor – should be restored. If those tapes proved relevant, they could restore more.</p>
<blockquote><p>A phased approach will allow the Court to engage in a more meaningful benefit-burden analysis before determining whether to require cost-shifting or cost-sharing…The Court believes that restoration of one-fourth of the total back-up tapes is warranted.</p></blockquote>
<p>The Government had to pay for the initial restoration. Once those tapes were restored, the parties could argue if more tapes were necessary and whether the Government would have to pay for more restoration, or if the contractor would have to split the costs.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/257623901" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/reasonably-accessible/if-relevance-of-esi-on-backup-tapes-is-unclear-court-may-adopt-phased-restoration/feed/</wfw:commentRss>
		</item>
		<item>
		<title>‘Safe Harbor’ Protection Gives Way To ‘Legal Hold’</title>
		<link>http://www.ciolaw.org/litigation-holds/safe-harbor-protection-gives-way-to-legal-hold/</link>
		<comments>http://www.ciolaw.org/litigation-holds/safe-harbor-protection-gives-way-to-legal-hold/#comments</comments>
		<pubDate>Mon, 24 Mar 2008 11:54:53 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Litigation Holds / Duty To Preserve]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/litigation-holds/safe-harbor-protection-gives-way-to-legal-hold/</guid>
		<description><![CDATA[One of the more interesting e-Discovery rules to the Federal Rules of Civil Procedure is Rule 37(e). 
This rule provides that as long as a company follows in good faith its regular document retention policy, then it cannot be sanctioned if electronically stored information (“ESI”) is destroyed, even if that ESI may have been useful in [...]]]></description>
			<content:encoded><![CDATA[<p>One of the more interesting e-Discovery rules to the Federal Rules of Civil Procedure is <a target="_blank" href="http://www.law.cornell.edu/rules/frcp/Rule37.htm">Rule 37(e)</a>. </p>
<p>This rule provides that as long as a company follows in good faith its regular document retention policy, then it cannot be sanctioned if electronically stored information (“ESI”) is destroyed, even if that ESI may have been useful in subsequent litigation.  This rule is often called the “safe harbor” rule.</p>
<p>Importantly, however, the “safe harbor” offers no protection if a company allows ESI to be deleted subsequent to a “duty to preserve” – or “<a target="_blank" href="http://www.ciolaw.org/litigation-holds/be-ready-for-legal-holds">litigation hold</a>.” A duty to preserve kicks in when a company reasonably anticipates litigation.</p>
<p>An illustrative way to understand how these two concepts work together is through the case of <em>Doe v. Norwalk Community College</em>.</p>
<p>In <em>Doe</em>, the plaintiff (who was referred to as “Jane Doe” in the lawsuit) sued the college in 2004 after a professor sexually assaulted her. As part of the litigation, the plaintiff wanted to inspect the professor’s computer hard drive.</p>
<p>Before her inspection, the college “wiped” the professor’s hard drive.  Consequently, the plaintiff asked the court to sanction the college.  Specifically, the plaintiff wanted an “adverse inference instruction” in which the court told the jury it could consider the lost ESI in the worst possible light against the college.</p>
<p>In its defense, the college argued the “safe harbor” provision precluded sanctions.  The college argued that the hard drive was wiped as part of the college’s routine deletion practices and it could not be sanctioned for failing to have it on hand.</p>
<p>The court disagreed with the college for two reasons.</p>
<p>First, the college never implemented a legal hold.  The college wiped the hard drive after the plaintiff’s lawyer had sent a demand letter in September 2004.  The demand letter had put the college on notice of the impending lawsuit.  The college should have preserved relevant ESI, including the professor’s hard drive.  As a result, even if the college had a routine deletion practice, a legal hold would have taken priority.</p>
<p>Second, the college failed to routinely follow its own retention policy.  Some email had been backed up for a year, some six months.  The dean acknowledged the college did not follow its retention policy as it relates to hard drives.  Since the college did not have a consistent policy, it could not rely on the safe harbor as a defense.</p>
<p>Litigation holds trump the safe harbor provision.  When a duty to preserve relevant ESI attaches, a company must modify its retention policy to accommodate the change.  Blindly allowing ESI to be deleted after a duty to preserve kicks in is an unacceptable practice.  As the college learned, courts will find spoliation and enter sanctions.</p>
<p>Moreover, once a company has a policy, follow it. It does no good to have a retention policy in writing but actually delete on a different schedule. There is no “safe harbor” protection if a company does not follow in good faith a routine policy.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/256999406" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/litigation-holds/safe-harbor-protection-gives-way-to-legal-hold/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Court Recently Ordered Third-Party Company To Disclose ESI</title>
		<link>http://www.ciolaw.org/esi/court-recently-ordered-third-party-company-to-disclose-esi/</link>
		<comments>http://www.ciolaw.org/esi/court-recently-ordered-third-party-company-to-disclose-esi/#comments</comments>
		<pubDate>Mon, 24 Mar 2008 11:53:50 +0000</pubDate>
		<dc:creator>Gregg Mayer</dc:creator>
		
		<category><![CDATA[Electronically Stored Information]]></category>

		<guid isPermaLink="false">http://www.ciolaw.org/esi/court-recently-ordered-third-party-company-to-disclose-esi/</guid>
		<description><![CDATA[As CIOLaw.org recently discussed , courts have the authority to require businesses to retrieve and disclose electronically stored information (“ESI”) even if those businesses are not named in a lawsuit. This occurred in a recent case this year.
Taubman Centers, Inc., a company in Michigan, was on the receiving end of a third-party subpoena recently as [...]]]></description>
			<content:encoded><![CDATA[<p>As CIOLaw.org <a target="_blank" href="http://www.ciolaw.org/reasonably-accessible/even-non-parties-to-lawsuits-may-have-to-retrieve-and-disclose-esi">recently discussed </a>, courts have the authority to require businesses to retrieve and disclose electronically stored information (“ESI”) even if those businesses are not named in a lawsuit. This occurred in a recent case this year.</p>
<p>Taubman Centers, Inc., a company in Michigan, was on the receiving end of a third-party subpoena recently as part of a lawsuit in Nevada. Taubman was not a named party in the lawsuit.</p>
<p>The subpoena sought 20 categories of ESI going back to 2001. After a preliminary review of the subpoena, Taubman determined it would take three employees working full time for four weeks to retrieve and review all of the 250,000 files at issue. Taubman argued this rendered the subpoena “unduly burdensome.”</p>
<p>The court disagreed, although the judge told the parties to work in good faith to reduce the scope of the subpoena, such as by shortening the time frame or changing key word searches.</p>
<blockquote><p>Discovery of electronic files…is commonplace in business litigation. The Court believes that the parties should be able to narrow the scope of this subpoena so that it does not generate an overly burdensome amount of documents.</p></blockquote>
<p>Regardless of the amount, the non-party company still has to bear the costs of disclosing the ESI. The case highlights the importance of companies being ready to retrieve and respond to subpoenas in the most cost-efficient way possible.</p>
<p>Read more <a target="_blank" href="http://www.lexology.com/library/detail.aspx?g=3556cbcc-c30e-4306-9540-a94db87ce489">about the case here</a>.</p>
<img src="http://feeds.ciolaw.org/~r/ciolaw/~4/256999407" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.ciolaw.org/esi/court-recently-ordered-third-party-company-to-disclose-esi/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
