<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	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/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Law Blog 2.0 &#187; FRCP Rule 26(f) &#8211; Reasonably Useable Format</title>
	<atom:link href="http://law2point0.com/wordpress/topics/e-discovery/frcp-rule-26f-reasonably-useable-format/feed/" rel="self" type="application/rss+xml" />
	<link>http://law2point0.com/wordpress</link>
	<description>This blog covers privacy, security, health information technology and e-discovery related topics. The primary goal of this blog is to raise public awareness of legal issues pertaining to the use of law and technology.</description>
	<lastBuildDate>Sat, 12 Jun 2010 02:39:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>California Electronic Discovery Act Signed Into Law &#8212; Takes Effect Immediately</title>
		<link>http://law2point0.com/wordpress/2009/07/07/california-electronic-discovery-act-signed-into-law-takes-effect-immediately/</link>
		<comments>http://law2point0.com/wordpress/2009/07/07/california-electronic-discovery-act-signed-into-law-takes-effect-immediately/#comments</comments>
		<pubDate>Tue, 07 Jul 2009 05:30:07 +0000</pubDate>
		<dc:creator>Robert Hudock</dc:creator>
				<category><![CDATA[Attorney-Client Privilege]]></category>
		<category><![CDATA[Discovery Plan]]></category>
		<category><![CDATA[E-Discovery]]></category>
		<category><![CDATA[FRCP 26(b)(2)(B) "Not Reasonably Accessible"]]></category>
		<category><![CDATA[FRCP 26(b)(5)(B) or FRE 502]]></category>
		<category><![CDATA[FRCP 37(e) Safe Harbor]]></category>
		<category><![CDATA[FRCP Rule 26(f) - Reasonably Useable Format]]></category>
		<category><![CDATA[Law and Technology]]></category>
		<category><![CDATA[Local Court Rule, Form or Guideline]]></category>
		<category><![CDATA[California]]></category>
		<category><![CDATA[EDiscovery]]></category>
		<category><![CDATA[ESI]]></category>

		<guid isPermaLink="false">http://law2point0.com/wordpress/?p=789</guid>
		<description><![CDATA[The California E-Discovery Act(“the Act”) establishing procedures for a party to obtain electronically stored information (ESI), similar to the Federal Rules of E-Discovery (December, 2006), was signed into law on June 29 by Governor Arnold Schwarzenegger.  The Act implements new rules for electronic discovery in California civil cases.  The Act tracks the 2006 amendments to the Federal Rules of Civil Procedure. [...]]]></description>
			<content:encoded><![CDATA[<div class="mceTemp"><a href="http://law2point0.com/wordpress/wp-content/uploads/2009/07/ab_5_bill_20090629_chaptered.pdf"  >The California E-Discovery Act</a> (“the Act”) establishing procedures for a party to obtain electronically stored information (ESI), similar to the Federal Rules of E-Discovery (December, 2006), was signed into law on June 29 by Governor Arnold Schwarzenegger.  The Act implements new rules for electronic discovery in California civil cases.  The Act tracks the 2006 amendments to the Federal Rules of Civil Procedure.</div>
<div class="mceTemp">
Key similarities between the Federal Rules and the California Act include: (i) the definition of “electronically stored information” as “information that is stored in an electronic medium” including “technology having electrical, digital, magnetic, wireless, optical, electromagnetic, or similar capabilities”; (ii) a Safe Harbor for good faith document destruction resulting in the loss of ESI; (iii) unreasonable e-discovery requests are prohibited; (iv) a party should produce records as normally kept in the ordinary course of business or in a reasonable useable format (note exception where a specific format is requested discussed below).</div>
<p>Key differences under the California Act include: (i) the right of a party to request production in a specific format; (ii) a responding party bears the burden of proving that data are inaccessible; and (iii) an explicit right to inspect, copy, test, and or sample ESI in the possession or control of a third party.</p>
<p>Limits on ESI Discovery can be appropriate where: (i) the information can be produced from a less-burdensome source, (ii) the discovery sought is unreasonably cumulative or duplicative, or (ii) the burden of producing the ESI outweighs the benefit.</p>
<p>ESI that “is from a source that is not reasonably accessible because of undue burden or expense” shall not be produced, provided the responding party provides written responses identifying data classified as inaccessible and the responding party takes affirmative action to seek a protective order and bear the burden of demonstrating that the ESI is in accessible.  If it is established that the electronically stored information is from a source that is not reasonably accessible because of undue burden or expense, the court may nevertheless order discovery if the opposing party shows good cause.</p>
<p>A party that inadvertently produces ESI that is subject to a claim of privilege or attorney work product protection may seek the return of the ESI by notifying the receiving party.  Upon notice, the opposing party must sequester or return (and not use) the ESI until the claim of privilege is resolved.  The opposing party, where appropriate, may file a motion within 30 days to contest the producing party’s claim of privilege.</p>
<div id="spreadx">&nbsp;<a target="_blank" href="http://digg.com/submit?phase=2&url=http://law2point0.com/wordpress/2009/07/07/california-electronic-discovery-act-signed-into-law-takes-effect-immediately/"  target="_new"><img src="http://law2point0.com/wordpress/wp-content/plugins/spreadx/images/digg.gif" alt="Digg" border="0" /></a>&nbsp;&nbsp;<a target="_blank" href="http://www.facebook.com/share.php?u=http://law2point0.com/wordpress/2009/07/07/california-electronic-discovery-act-signed-into-law-takes-effect-immediately/"  target="_new"><img src="http://law2point0.com/wordpress/wp-content/plugins/spreadx/images/facebook.gif" alt="Facebook" border="0" /></a>&nbsp;&nbsp;<a target="_blank" href="http://www.stumbleupon.com/submit?url=http://law2point0.com/wordpress/2009/07/07/california-electronic-discovery-act-signed-into-law-takes-effect-immediately/&title=California+Electronic+Discovery+Act+Signed+Into+Law+%26%238212%3B+Takes+Effect+Immediately"  target="_new"><img src="http://law2point0.com/wordpress/wp-content/plugins/spreadx/images/stumble.gif" alt="StumbleUpon" border="0" /></a>&nbsp;&nbsp;<a target="_blank" href="http://technorati.com/faves?add=http://law2point0.com/wordpress/2009/07/07/california-electronic-discovery-act-signed-into-law-takes-effect-immediately/"  target="_new"><img src="http://law2point0.com/wordpress/wp-content/plugins/spreadx/images/technorati.gif" alt="Technorati" border="0" /></a>&nbsp;&nbsp;<a target="_blank" href="http://del.icio.us/post?url=http://law2point0.com/wordpress/2009/07/07/california-electronic-discovery-act-signed-into-law-takes-effect-immediately/&title=California+Electronic+Discovery+Act+Signed+Into+Law+%26%238212%3B+Takes+Effect+Immediately"  target="_new"><img src="http://law2point0.com/wordpress/wp-content/plugins/spreadx/images/delicious.gif" alt="Deli.cio.us" border="0" /></a>&nbsp;</div><p><a href="http://law2point0.com/wordpress/2009/07/07/california-electronic-discovery-act-signed-into-law-takes-effect-immediately/" rel="bookmark">California Electronic Discovery Act Signed Into Law &#8212; Takes Effect Immediately</a> originally appeared on <a href="http://law2point0.com/wordpress">Law Blog 2.0</a> on July 7, 2009.</p>
]]></content:encoded>
			<wfw:commentRss>http://law2point0.com/wordpress/2009/07/07/california-electronic-discovery-act-signed-into-law-takes-effect-immediately/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Produce in a Reasonably Usable Format or in the Form in Which Data Are Stored in the Normal Course of Business or Risk Potential Sanctions and an Order to Compel the Production of Native Documents</title>
		<link>http://law2point0.com/wordpress/2008/07/24/produce-in-a-reasonably-usable-format-or-in-the-form-in-which-data-are-stored-in-the-normal-course-of-business-or-risk-potential-sanctions-and-an-order-to-compel-the-production-of-native-documents/</link>
		<comments>http://law2point0.com/wordpress/2008/07/24/produce-in-a-reasonably-usable-format-or-in-the-form-in-which-data-are-stored-in-the-normal-course-of-business-or-risk-potential-sanctions-and-an-order-to-compel-the-production-of-native-documents/#comments</comments>
		<pubDate>Thu, 24 Jul 2008 03:01:00 +0000</pubDate>
		<dc:creator>Robert Hudock</dc:creator>
				<category><![CDATA[E-Discovery]]></category>
		<category><![CDATA[FRCP Rule 26(f) - Reasonably Useable Format]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[meta-data]]></category>
		<category><![CDATA[Native Documents]]></category>
		<category><![CDATA[OCR]]></category>
		<category><![CDATA[Principle 12 of the Sedona Principles]]></category>
		<category><![CDATA[Reasonably Useable]]></category>
		<category><![CDATA[Rule 26(f)]]></category>
		<category><![CDATA[TIFF]]></category>

		<guid isPermaLink="false">http://d18e2e54-ab13-42fe-832f-3be0b272bd13</guid>
		<description><![CDATA[The general rule in discovery is whatever agreement is reached between opposing parties during a meet and confer (under Fed. R. Civ. P. Rule 26(f)) controls the form of production. See e.g., Williams v. Sprint/United Management Co.,230 F.R.D. 640 (D.Kan.2005)(finding that a producing party must produce electronic documents with meta-data, unless that the parties agree that meta-data should not be produced or the producing party seeks a protective order),   In the event the other side (with full knowledge) agrees to a production of TIFF images without OCR text without any meta-data -- this agreement would likely control, and such a production probably could not be successfully challenged.  However, as is more often the case, the parties do not address the issue of an acceptable production format and each party is thus left to determine how to produce documents in a reasonably usable format.  In this situation a producing party is free to produce the data as it was originally stored or in another format that is reasonably usable (which typically means that key elements of meta-data are left intact and the electronic data is [...]]]></description>
			<content:encoded><![CDATA[<p>The general rule in discovery is whatever agreement is reached between opposing parties during a meet and confer (under Fed. R. Civ. P. Rule 26(f)) controls the form of production. <em>See e.g., </em><span style="text-decoration: underline;">Williams v. Sprint/United Management Co.</span>,230 F.R.D. 640 (D.Kan.2005)(finding that a producing party must produce electronic documents with meta-data, unless that the parties agree that meta-data should not be produced or the producing party seeks a protective order),   In the event the other side (with full knowledge) agrees to a production of TIFF images without OCR text without any meta-data &#8212; this agreement would likely control, and such a production probably could not be successfully challenged.  However, as is more often the case, the parties do not address the issue of an acceptable production format and each party is thus left to determine how to produce documents in a reasonably usable format.  In this situation a producing party is free to produce the data as it was originally stored or in another format that is reasonably usable (which typically means that key elements of meta-data are left intact and the electronic data is search-able).</p>
<p>A TIFF production (along with a load-file containing agreed upon meta-data fields and OCR text) is the industry standard in many jurisdictions. (A few attorneys (and a lot of e-discovery vendors) more daring than I may attempt a native production but I do not recommend it.) TIFF is an abbreviation for “Tagged Image File Format”. A TIFF is an industry file format, which consists of the image and header information. In other words, a TIFF is simply a picture of a document. This picture contains no other data about the contents of the original file; when a native file is converted to a TIFF file, the text of the document and associated meta-data is lost. The use of a TIFF based production methodology is desirable due to the difficulties and risks in producing native files. Native files are virtually impossible to redact, bates-stamp, and review. (The very act of opening up the document will passively change attributes of the file being reviewed.)</p>
<p>The Federal Rules of Civil Procedure require that counsel produce documents in a reasonably usable format or the format that the documents are maintained by counsel’s client. In the situation where counsel produces native documents (in a native production) the production would be acceptable under the Federal Rules of Civil Procedure (even in some cases where the data may not be search-able as is often the case with legacy data).  Assuming we are dealing with legacy data, a production is not reasonably usable if counsel converts native files to TIFF images in lieu of producing the native files, but fails to produce the OCR text and reasonably necessary meta-data fields (e.g., for an email common meta-data fields include To, From, CC, BCC, Subject, Date, and Attachments).</p>
<p>Legal counsel, in order to make life more difficult for the opposing counsel, may try to produce only TIFF images (without OCR text and meta-data fields). One such case in the Eastern District of California, <span style="text-decoration: underline;">L.H. v. Schwarzenegger</span>, 2008 WL 2073958 (E.D. Cal. May 14, 2008), illustrates the situation and the consequences.  In this case the defendant’s counsel converted native documents from their original format, which was search-able into PDF files that were not search-able. (Note a PDF file that is not search-able, for purposes of our analysis, is the same as a TIFF image; however, the PDF file format is much more complex then the TIFF format and can potentially (and generally does) include search-able text and other data.)  The Court in the Eastern District of California, in the above case, found the production inconsistent with Rule 34 because the defendant’s counsel produced documents which were not search-able while the original (native) documents had been search-able. The Court in this case awarded the plaintiff monetary sanctions in light of defendant’s &#8220;purposeful foot dragging on discovery&#8221; and resulting prejudice to the plaintiff’s case.  Other jurisdictions have similarly recognized this same rule. <em>See</em> <span style="text-decoration: underline;">DE Technologies, Inc. v. Dell, Inc.</span>, No. Civ.A. 7:04CV00628 (W.D. Va. Jan. 12, 2007), (court found that counsel’s production was “reasonably usable” and thus in compliance with Rule 34 because the documents produced could be searched); <em>see also </em><span style="text-decoration: underline;">D&#8217;Onofrio v. SFX Sports Group, Inc.</span>, 247 F.R.D. 43 (D.D.C.2008)(court holding that Rule 34 does not require production of electronically stored information in the original format unless necessary for it to be reasonably usable).</p>
<p>Committee Note to Rule 34(b) (to the recently amended Federal Rules of Civil Procedures) states that “[i]f the responding party ordinarily maintains the information it is producing in a way that makes it search-able by electronic means, the information should not be produced in a form that removes or significantly degrades this feature.” A party who converts native documents to TIFF images without an accompanying load-file, without search-able text, and with a bare minimum of meta-data has not produced the data in a “reasonably usable” format.  &#8220;The option to produce in a reasonably<br />
usable form does not mean that a responding party is free to convert electronically stored information from the form in which it is ordinarily maintained to a different form that makes it more difficult or burdensome for the requesting party to use the information efficiently in the litigation.&#8221; <em> </em>(Committee Note to Rule 34(b)(as amended December 2006)).</p>
<p>Principle 12 of the Sedona Principles, Best Practices Recommendations &amp; Principles for Addressing Electronic Document Production (2d ed. June 2007) similarly states that:</p>
<p><em>Absent party agreement or court order specifying the form or forms of production, production should be made in the form or forms in which the information is ordinarily maintained or in a reasonably usable form, taking into account the need to produce reasonably accessible meta-data that will enable the receiving party to have the same ability to access, search, and display the information as the producing party where appropriate or necessary in light of the nature of the information and the needs of the case. </em></p>
<p>There are two cases often cited by those opposing the production of OCR text along with at least some meta-data.  These cases either predate<br />
the e-Discovery Amendments of December 2006 as is the case <span style="text-decoration: underline;">Wyeth</span>, or rely on precedent that predates the e-Discovery amendments as is the case in <span style="text-decoration: underline;">Pace</span>. <em>See</em> <span style="text-decoration: underline;">Pace v. International Mill Service, Inc.</span>, 2007 WL 1385385 (N.D. Ind. 5-7-2007); see also <span style="text-decoration: underline;">Wyeth v. Impax Laboratories, Inc.</span>,<br />
2006 WL 3091331 (D. Del. 10-26-2006)(The court in Pace relied on <span style="text-decoration: underline;">Williams v. Sprint/United Management Co.</span>, 230 F.R.D. 640<br />
(D. Kan. 2005), for the prpposition, &#8220;[a]bsent a special request for meta-data,&#8221; a production of documents in PDF or TIFF images&#8221;).</p>
<p>A production of TIFF Images that does include OCR text along with a minimum set of meta-data (in the view of many Courts especially those in California) may not be considered &#8220;reasonably usable&#8221; and counsel may risk sanctions.  However, an equally likely result may be a motion to compel the production of native documents (also undesirable).  Courts when confronted with this scenario frequently will order the production of the native documents where the TIFF production is limiting and prejudicial to opposing counsel. <em>See </em><span style="text-decoration: underline;">Nova Measuring Instruments Ltd. v. Nanometrics, Inc.</span>, 417 F. Supp.2d 1121 (N.D. Cal. 2006)(court granted motion to compel production of native file format, were original production format failed to include meta-data); <em>see also </em><span style="text-decoration: underline;">Lorraine v. Markel American Ins. Co</span>., 241 F.R.D. 534 (D. Md. 5-4-2007)(court finding meta-data essential aspect of an electronic evidence),</p>
<div id="spreadx">&nbsp;<a target="_blank" href="http://digg.com/submit?phase=2&url=http://law2point0.com/wordpress/2008/07/24/produce-in-a-reasonably-usable-format-or-in-the-form-in-which-data-are-stored-in-the-normal-course-of-business-or-risk-potential-sanctions-and-an-order-to-compel-the-production-of-native-documents/"  target="_new"><img src="http://law2point0.com/wordpress/wp-content/plugins/spreadx/images/digg.gif" alt="Digg" border="0" /></a>&nbsp;&nbsp;<a target="_blank" href="http://www.facebook.com/share.php?u=http://law2point0.com/wordpress/2008/07/24/produce-in-a-reasonably-usable-format-or-in-the-form-in-which-data-are-stored-in-the-normal-course-of-business-or-risk-potential-sanctions-and-an-order-to-compel-the-production-of-native-documents/"  target="_new"><img src="http://law2point0.com/wordpress/wp-content/plugins/spreadx/images/facebook.gif" alt="Facebook" border="0" /></a>&nbsp;&nbsp;<a target="_blank" href="http://www.stumbleupon.com/submit?url=http://law2point0.com/wordpress/2008/07/24/produce-in-a-reasonably-usable-format-or-in-the-form-in-which-data-are-stored-in-the-normal-course-of-business-or-risk-potential-sanctions-and-an-order-to-compel-the-production-of-native-documents/&title=Produce+in+a+Reasonably+Usable+Format+or+in+the+Form+in+Which+Data+Are+Stored+in+the+Normal+Course+of+Business+or+Risk+Potential+Sanctions+and+an+Order+to+Compel+the+Production+of+Native+Documents"  target="_new"><img src="http://law2point0.com/wordpress/wp-content/plugins/spreadx/images/stumble.gif" alt="StumbleUpon" border="0" /></a>&nbsp;&nbsp;<a target="_blank" href="http://technorati.com/faves?add=http://law2point0.com/wordpress/2008/07/24/produce-in-a-reasonably-usable-format-or-in-the-form-in-which-data-are-stored-in-the-normal-course-of-business-or-risk-potential-sanctions-and-an-order-to-compel-the-production-of-native-documents/"  target="_new"><img src="http://law2point0.com/wordpress/wp-content/plugins/spreadx/images/technorati.gif" alt="Technorati" border="0" /></a>&nbsp;&nbsp;<a target="_blank" href="http://del.icio.us/post?url=http://law2point0.com/wordpress/2008/07/24/produce-in-a-reasonably-usable-format-or-in-the-form-in-which-data-are-stored-in-the-normal-course-of-business-or-risk-potential-sanctions-and-an-order-to-compel-the-production-of-native-documents/&title=Produce+in+a+Reasonably+Usable+Format+or+in+the+Form+in+Which+Data+Are+Stored+in+the+Normal+Course+of+Business+or+Risk+Potential+Sanctions+and+an+Order+to+Compel+the+Production+of+Native+Documents"  target="_new"><img src="http://law2point0.com/wordpress/wp-content/plugins/spreadx/images/delicious.gif" alt="Deli.cio.us" border="0" /></a>&nbsp;</div><p><a href="http://law2point0.com/wordpress/2008/07/24/produce-in-a-reasonably-usable-format-or-in-the-form-in-which-data-are-stored-in-the-normal-course-of-business-or-risk-potential-sanctions-and-an-order-to-compel-the-production-of-native-documents/" rel="bookmark">Produce in a Reasonably Usable Format or in the Form in Which Data Are Stored in the Normal Course of Business or Risk Potential Sanctions and an Order to Compel the Production of Native Documents</a> originally appeared on <a href="http://law2point0.com/wordpress">Law Blog 2.0</a> on July 24, 2008.</p>
]]></content:encoded>
			<wfw:commentRss>http://law2point0.com/wordpress/2008/07/24/produce-in-a-reasonably-usable-format-or-in-the-form-in-which-data-are-stored-in-the-normal-course-of-business-or-risk-potential-sanctions-and-an-order-to-compel-the-production-of-native-documents/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
