<?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>Practical Ediscovery &#187; Accessibility</title>
	<atom:link href="http://blog.hinshawlaw.com/practicalediscovery/category/accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hinshawlaw.com/practicalediscovery</link>
	<description>Analysis of emerging electronic discovery trends</description>
	<lastBuildDate>Wed, 09 Nov 2011 16:22:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Identifying inaccessible sources of ESI just got a little easier</title>
		<link>http://blog.hinshawlaw.com/practicalediscovery/2010/01/08/identifying-inaccessible-sources-of-esi-just-got-a-little-easier/</link>
		<comments>http://blog.hinshawlaw.com/practicalediscovery/2010/01/08/identifying-inaccessible-sources-of-esi-just-got-a-little-easier/#comments</comments>
		<pubDate>Fri, 08 Jan 2010 20:30:47 +0000</pubDate>
		<dc:creator>Steve Puiszis</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Cost]]></category>
		<category><![CDATA[Preservation]]></category>
		<category><![CDATA[reasonably accessible electronically stored information]]></category>
		<category><![CDATA[rule 26]]></category>

		<guid isPermaLink="false">http://blog.hinshawlaw.com/practicalediscovery/?p=658</guid>
		<description><![CDATA[Fed.R.Civ.P. 26(b)(2)(B) explains that a party need not produce electronically stored information (“ESI”) from sources that are not reasonably accessible because of undue burden or cost. Parties are expected to produce relevant, non-privileged information from sources that are “reasonably accessible” subject to Rule 26(b)(2)(C)’s limitations that apply to all discovery under the federal rules. This [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.law.cornell.edu/rules/frcp/Rule26.htm">Fed.R.Civ.P. 26(b)(2)(B)</a> explains that a party need not produce electronically stored information (“ESI”) from sources that are not reasonably accessible because of undue burden or cost. Parties are expected to produce relevant, non-privileged information from sources that are “reasonably accessible” subject to Rule 26(b)(2)(C)’s limitations that apply to all discovery under the federal rules. This “two-tier” approach to ediscovery is easy to recite but can be very difficult to apply in practice. At what point does a source of ESI cross the threshold from reasonable accessibility to inaccessibility under the Rule? Are there sources of information that parties can readily agree are not reasonably accessible? Alas, neither Rule 26(b)(2)(B) nor its accompanying committee note provide any helpful insight. Indeed, the 2006 Advisory Committee Note states “[i]t is not possible to define in a rule the different types of technological features that may affect the burdens and costs of accessing electronically stored information.”</p>
<p><a href="http://blog.hinshawlaw.com/practicalediscovery/wp-content/uploads/2010/01/old_computers.jpg"><img src="http://blog.hinshawlaw.com/practicalediscovery/wp-content/uploads/2010/01/old_computers.jpg" alt="" title="old_computers" width="240" height="180" class="alignleft size-full wp-image-660" /></a></p>
<p>The Report of the Judicial Conference Committee on Rules of Practice and Procedure (“Standing Committee Report”) which predated the enactment of the 2006 ediscovery amendments to the federal rules provided some insight. The Standing Committee Report did note that the features of an information system that make it burdensome or costly to access ESI can vary from system to system and will change over time. However, it provided several examples of “current technology” that do not generally fit under the rubric of reasonable accessibility. Those examples included “deleted information, information kept on some backup-tape systems for disaster recovery purposes, and legacy data remaining from systems no longer in use.” See THE NEW E-DISCOVERY RULES, Dahlstrom Legal Publishing, Inc. (2006) at p. 15. Unfortunately, that guidance was not carried over into the 2006 Advisory Committee Note to Rule 26(b)(2)(B).</p>
<p><span id="more-658"></span></p>
<p>The difficulty identifying and then proving that a particular source of information was inaccessible under the Rule has resulted in decisions such as <em>Starbucks Corp. v. ADT Sec. Services, Inc.</em>, 2009 WL 4730798 *6 (W.D.Wash. April 30, 2009), where one court concluded: </p>
<blockquote><p>The Court cannot relieve Defendant of its duty to produce those documents merely because Defendant has chosen a means to preserve the evidence which makes ultimate production of relevant documents expensive…. To permit a party to ‘reap the business benefits of such technology and simultaneously use technology as a shield in litigation would lead to incongruous and unfair results.
</p></blockquote>
<p>All is not lost, help has arrived. The task of identifying sources of ESI that are inaccessible has been streamlined by one of the principles promulgated in the Seventh Circuit’s Electronic Discovery Pilot Program. One of our <a href="http://blog.hinshawlaw.com/practicalediscovery/2009/10/06/seventh-circuits-electronic-discovery-pilot-program/">prior blog posts</a> highlighted the main features of the Seventh Circuit’s Pilot Program [<a href="http://www.ca7.uscourts.gov/7thCircuit_ElectronicDiscovery.pdf">Info about the program - PDF</a>] which was developed in response to comments by the business community and practicing attorneys that the civil justice system’s pretrial discovery process is in need of reform. The purpose of the Seventh Circuit’s Pilot Program is to assist courts in the administration of Fed.R.Civ.P. 1 and secure “the just, speedy, and inexpensive determination” of every civil case.</p>
<p>A series of ediscovery principles were developed and codified into a standing order that is used as part of the Seventh Circuit’s Pilot Program. Principle 2.04(d) addresses the scope of preservation and identifies categories of ESI that are generally not discoverable in most cases. Those categories  of ESI are: </p>
<ul>
<li>“Deleted,” “slack,” “fragmented,” or “unallocated” data on hard drives;</li>
<li>Random access memory (RAM) or other ephemeral data;</li>
<li>On-line access data such as temporary internet files, history, cache, cookies, etc.;</li>
<li>Data in metadata fields that are frequently updated automatically, such as last-opened dates; and</li>
<li>Backup data that is substantially duplicative of data that is more accessible elsewhere;</li>
<li>Other forms of ESI whose preservation requires extraordinary affirmative measures that are not utilized in the ordinary course of business.</li>
</ul>
<p>Principle 2.04(d) further provides that if any party intends to request the “preservation or production of these categories” of ESI, then that should be discussed at the party’s initial meet and confer conference or as soon thereafter as practicable. Obviously, Principle 2.04(D) streamlines the process of identifying inaccessible sources of information. While it does not categorically prohibit discovery of ESI from those sources, it suggests that discovery from them will not be permitted unless a good reason or compelling need is shown.</p>
<p>While this principle will primarily benefit those attorneys practicing in district courts within the Seventh Circuit’s boundaries, attorneys practicing outside of the Seventh Circuit’s “friendly confines” should be aware of principle and consider raising it as persuasive authority when resisting attempts to obtain discovery from those sources of ESI identified in Principle 2.04(d).</p>
<p>Please remember however, that identifying a source of ESI as inaccessible under Rule 26(b)(2)(B) does not obviate the client’s need to preserve that information. The Advisory Committee Note to Rule 26(b)(2)(B) highlights that conundrum by explaining: “whether a responding party is required to preserve unsearched sources of potentially responsive information that it believes are not reasonably accessible depends on the circumstances of each case.” Thus, the need to continue to preserve ESI from inaccessible sources should be another topic of potential discussion with opposing counsel at </p>
<p><strong><em>Photo courtesy <a href="http://www.flickr.com/photos/eurleif/255241547/">Flickr user eurleif</a> under <a href="http://creativecommons.org/licenses/by-sa/2.0/deed.en">this Creative Commons license</a>.</em></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.hinshawlaw.com/practicalediscovery/2010/01/08/identifying-inaccessible-sources-of-esi-just-got-a-little-easier/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Seventh Circuit&#8217;s Electronic Discovery Pilot Program</title>
		<link>http://blog.hinshawlaw.com/practicalediscovery/2009/10/06/seventh-circuits-electronic-discovery-pilot-program/</link>
		<comments>http://blog.hinshawlaw.com/practicalediscovery/2009/10/06/seventh-circuits-electronic-discovery-pilot-program/#comments</comments>
		<pubDate>Tue, 06 Oct 2009 19:13:26 +0000</pubDate>
		<dc:creator>Steve Puiszis</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Cost]]></category>
		<category><![CDATA[electronic data]]></category>
		<category><![CDATA[Litigation Hold]]></category>
		<category><![CDATA[Metadata]]></category>
		<category><![CDATA[Preservation]]></category>
		<category><![CDATA[Production]]></category>
		<category><![CDATA[Review]]></category>
		<category><![CDATA[Sanctions]]></category>
		<category><![CDATA[cost shifting]]></category>
		<category><![CDATA[keyword]]></category>
		<category><![CDATA[keyword searching]]></category>
		<category><![CDATA[not reasonably accessible]]></category>
		<category><![CDATA[ocr]]></category>
		<category><![CDATA[searching]]></category>
		<category><![CDATA[work product doctrine]]></category>

		<guid isPermaLink="false">http://blog.hinshawlaw.com/practicalediscovery/?p=524</guid>
		<description><![CDATA[Recently, the Seventh Circuit announced its Electronic Discovery Pilot Program. The program was developed in response to continuing comments by the business community and practicing attorneys about the need to reform the civil pretrial discovery process. It is an attempt to reduce the cost and burden of ediscovery in litigation. What makes the Seventh Circuit’s [...]]]></description>
			<content:encoded><![CDATA[<p>Recently, the Seventh Circuit announced its <a href="http://www.7thcircuitbar.org/associations/1507/files/Statement1.pdf" target="_blank">Electronic Discovery Pilot Program</a>. The program was developed in response to continuing comments by the business community and practicing attorneys about the need to reform the civil pretrial discovery process. It is an attempt to reduce the cost and burden of ediscovery in litigation. What makes the Seventh Circuit’s pilot program unique is that its results will be reviewed and analyzed during the program’s phases.</p>
<p>A series of Principles Relating to the Discovery of Electronically Stored Information (“ESI”) were developed and codified in a standing order. These principles are intended to serve as supplemental procedural ediscovery guidelines for the parties in selected cases. Individual district court, magistrate, and bankruptcy judges in the Seventh Circuit have agreed to adopt the principles and implement them in selected cases during Phase I of the program, which runs through May 1, 2010.</p>
<p><img class="reflect alignleft" src="http://farm4.static.flickr.com/3633/3365986241_f1c8341a4c.jpg" alt="Pilot for a Day program by UNC - CFC - USFK." width="250" height="186" />Kenneth J. Winters, the Managing Director of the Sedona Conference®, and former Colorado Supreme Court Judge Rebecca Kourlis, the Executive Director of the Institute for Advancement of the American Legal System (“IAALS”) at the University of Denver, assisted in the development and review of these principles.</p>
<p>IAALS is developing questionnaires to assess the efficacy of the principles. The questionnaires will be completed by the judges and lawyers participating in Phase I of the program. The results of the IAALS’ questionnaires will be presented to the Seventh Circuit at its annual meeting in May, 2010. At that time, the program’s ediscovery principles will be reviewed and refined as needed. Phase II of the program is scheduled to proceed from June, 2010 through May, 2011. It is contemplated that in May, 2011, Phase II findings will be presented and the Seventh Circuit’s final ediscovery principles announced.</p>
<p>Among other things, the principles require in the event of a dispute during the meet and confer process, the appointment of an ediscovery liaison who should be prepared to participate in ediscovery dispute resolution. These principles also recognize that that Rule 26(b)(2)(C)’s proportionality principles should be applied when formulating a discovery plan; provide that sanctions can be imposed for the failure to cooperate and participate in good faith in the meet and confer process; identify categories of ESI, which are generally not discoverable in most cases; and provides that if a party intends to request the preservation or production of these categories of ESI, that such a request be discussed at the parties’ initial meet and confer session or as soon thereafter as practicable.</p>
<p><span id="more-524"></span></p>
<p>Some of the other noteworthy aspects of the Seventh Circuit’s principles include:</p>
<ul>
<li>Acknowledging Fed. R. Civ. P. 1’s forgotten role in ediscovery by providing the purpose of these principles is to assist courts in the administration of the Rule’s requirement of securing “the just, speedy, and inexpensive determination of every action and proceeding.”</li>
<li>Recognizing that an attorney’s ethical duty of zealous representation is not compromised by conducting discovery in a cooperative manner.</li>
<li>Specifying that Rule 26(b)(2)(C)’s proportionality standard should be applied when formulating a discovery plan, meaning that requests for production and responses thereto “should be reasonably targeted, clear and as specific as practicable.”</li>
<li>Noting that ESI disputes will be resolved more efficiently if before the initial conference with opposing counsel, the attorneys for each party review and understand how their client’s data is stored and retrieved in order to determine what issues must be addressed during their initial meet and confer discussions.</li>
<li>Authorizing a court to require additional discussions prior to the commencement of discovery and/or to impose sanctions where appropriate on any party or counsel that fails to cooperate and participate in good faith in the meet and confer process.</li>
<li>Requiring in the event of a dispute concerning the preservation or production of ESI, the designation of an ediscovery liaison for the purposes of meeting, conferring, and attending court hearings.</li>
<li>Providing the ediscovery liaison may be an in-house or outside counsel, a third-party consultant, or an employee of a party.</li>
<li>Specifying the ediscovery liaison must be prepared to participate in ediscovery dispute resolution; know the parties’ ediscovery efforts; and have access to those who are familiar with the parties’ electronic systems and capabilities in order to explain those systems and answer relevant questions. The ediscovery liaison must also have reasonable access to those who are knowledgeable about technical aspects of ediscovery.</li>
<li>Providing that vague and overly broad preservation orders should not be sought or entered and noting that the information sought to be preserved through a preservation letter or court order should be reasonable in scope and mindful of Rule 26(b)(2)(C)’s proportionality factors.</li>
<li>Explaining that if the recipient of a preservation letter chooses to respond, the response should provide useful information regarding the preservation efforts undertaken by the responding party. Examples of useful and specific information for such a response include the information a responding party is willing to preserve, the steps taken in response to any preservation letter, any disagreements with the preservation request, and any further preservation issues that were not raised.</li>
<li>Mandating that every party and its counsel are responsible for taking reasonable and proportionate steps to preserve relevant and discoverable ESI within its possession, custody, and control.</li>
<li>Recognizing that discovery concerning another party’s preservation and collection efforts may be appropriate, but noting that if used inadvisably, can cause unnecessary expense, delay, and may unnecessarily implicate work product and attorney-client privilege. Requires that prior to initiating such discovery, the parties are expected to meet and confer concerning its need and the suitability of alternative means for obtaining that information. Acknowledges this requirement does not preclude deponents addressing the merits of the case from answering questions concerning the steps taken to preserve and collect ESI.</li>
<li>Specifying that certain categories of ESI are considered generally “not discoverable” in most cases and requiring a party that intends to request the preservation of production of those categories of ESI, discuss that discovery request at the parties’ initial meet and confer session, or as soon as practical thereafter.</li>
<li>Identifying categories of ESI that are generally not discoverable to include: (a) deleted, fragmented, unallocated data, or data found in the slack space of computer hard drives; (b) random access memory (RAM) or other ephemeral data; (c) temporary internet files, history, cache, cookies, and other forms of on-line access data; (d) data in metadata fields that are frequently updated automatically such as last-open dates; (e) backup data that is substantially duplicative of data that is more accessible elsewhere; and (f) other forms of ESI whose preservation requires extraordinary affirmative measures that are not utilized in the ordinary course of business.</li>
<li>Requiring in the event of a dispute concerning the scope of a party’s preservation efforts that counsel meet and confer and fully explain their reasons for believing that additional efforts are not reasonable or appropriate.</li>
<li>Encouraging parties, at their initial Rule 26(f) conference, to discuss ways to eliminate duplicative ESI, including horizontal or vertical deduplication, the filtering of data by date ranges, file types, custodians as well as the use of search terms, keyword searching, concept clustering, or other advanced methodologies.</li>
<li>Providing that ESI or other tangible or hard copy documents, which are not text searchable, need not be made text searchable when produced.</li>
<li>Recognizing the requesting party is responsible for the incremental cost of creating its copy of any requested information.</li>
<li>Encouraging parties to discuss cost sharing for optical character recognition (OCR) or other upgrades of paper documents or other forms of non-text-searchable ESI.</li>
<li>Noting that ESI stored in a database or a database management system can be produced by querying the database for discoverable information resulting in a report or a reasonably useable exportable electronic file for review by the requesting party or its counsel.</li>
</ul>
<p>Several years ago, in an article to the members of the Illinois Association of Defense Trial Counsel, I wrote that if left unchecked, the cost of electronic discovery will prove to be the biggest single threat to our civil jury trial system. Only time will tell whether these steps will fulfill their purpose of streamlining ediscovery and reducing the cost of federal-court litigation or whether a more “radical” step such as some form of mandatory cost as under the Texas rules will be required.</p>
<p>Pilot photo courtesy of Flickr user <a href="http://www.flickr.com/photos/unc-cfc-usfk/" target="_self">UNC &#8211; CFC &#8211; USFK</a> under <a href="http://creativecommons.org/licenses/by/2.0/deed.en">this Creative Commons license</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.hinshawlaw.com/practicalediscovery/2009/10/06/seventh-circuits-electronic-discovery-pilot-program/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OCR cost shifting rejected</title>
		<link>http://blog.hinshawlaw.com/practicalediscovery/2009/03/02/ocr-cost-shifting-rejected/</link>
		<comments>http://blog.hinshawlaw.com/practicalediscovery/2009/03/02/ocr-cost-shifting-rejected/#comments</comments>
		<pubDate>Mon, 02 Mar 2009 19:17:28 +0000</pubDate>
		<dc:creator>Steve Puiszis</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Cost]]></category>
		<category><![CDATA[cost shifting]]></category>
		<category><![CDATA[costs]]></category>
		<category><![CDATA[native format]]></category>
		<category><![CDATA[not reasonably accessible]]></category>
		<category><![CDATA[ocr]]></category>
		<category><![CDATA[strategy]]></category>
		<category><![CDATA[zubulake]]></category>

		<guid isPermaLink="false">http://blog.hinshawlaw.com/practicalediscovery/?p=226</guid>
		<description><![CDATA[Proctor &#038; Gamble Co. v. S.C. Johnson &#038; Son, Inc., 2009 WL 440543 (E.D. Tex., Feb. 19, 2009) Given today’s economic climate, shifting the costs of electronic discovery is a strategy that should be considered whenever possible. In Proctor &#038; Gamble, the district court rejected the defendant’s attempt to shift the costs of applying optical [...]]]></description>
			<content:encoded><![CDATA[<p><strong><em>Proctor &#038; Gamble Co. v. S.C. Johnson &#038; Son, Inc.</em>, 2009 WL 440543 (E.D. Tex., Feb. 19, 2009)</strong></p>
<p>Given today’s economic climate, shifting the costs of electronic discovery is a strategy that should be considered whenever possible. In <em>Proctor &#038; Gamble</em>, the district court rejected the defendant’s attempt to shift the costs of applying optical character recognition (&#8220;OCR&#8221;) to documents it had agreed to produce in a tagged image file format (&#8220;TIFF&#8221;).  The application of OCR to the TIFF images would make the imaged documents electronically searchable. </p>
<p><img src="http://blog.hinshawlaw.com/practicalediscovery/wp-content/uploads/2009/03/chess1.jpg" alt="chess" title="chess" width="250" height="154" class="alignleft size-full wp-image-228" /> </p>
<p>While the district court recognized that the application of OCR to the imaged documents was &#8220;not absolutely necessary to [the] litigation,&#8221; it rejected the defendant’s attempt to shift the cost of OCR processing because the defendant failed to provide any support for its cost estimate, and no valid legal argument to support its claim that the cost burden should be shifted. The defendant advised the court that it did not intend to use the OCR process, and argued that it should not be forced to bear the added OCR expense solely for the plaintiff’s convenience. That argument failed to carry the day in <em>Proctor &#038; Gamble</em>.</p>
<p>Any cost-shifting strategy requires careful advanced planning, and a thorough knowledge of the client’s information systems. While the district court’s ruling in <em>Proctor &#038; Gamble</em> appears relatively straightforward, there are a number of issues that are relevant to any cost-shifting strategy that must be carefully analyzed before a party should even begin to evaluate cost-shifting factors outlined in <em>Zubulake</em>, which was the focus of the district court’s opinion in <em>Proctor &#038; Gamble</em>.    </p>
<p><span id="more-226"></span></p>
<p><strong>Evaluate the accessibility of the data.</strong></p>
<p>A number of district courts have concluded that cost-shifting should not be considered absent a showing of inaccessibility. See, e.g., <em>Peskoff v. Farber</em>, 240 F.R.D. 26, 31 (D.D.C. 2007) (“cost-shifting does not even become a possibility unless there is first a showing of inaccessibility”); <em>Quinby v. WestLB AG</em>, 245 F.R.D. 94, 104 (S.D.N.Y. 2006)(“Cost-shifting is appropriate only where electronic discovery imposes and undue burden or expense”); <em>Zubulake v.UBS Warburg, LLC</em>, 217 F.R.D. 309, 323 (S.D.N.Y. 2003)(“A court should consider cost-shifting only when the electronic data is relatively inaccessible, such as in backup tapes). The burden of proof is placed on the party asserting inaccessibility.</p>
<p>While information stored on backup tapes, on legacy systems, and fragmented data on hard drives may generally be considered inaccessible sources, there is no clear dividing line between accessible and inaccessible data sources. Under <a href="http://www.law.cornell.edu/rules/frcp/Rule26.htm">Rule 26(b)(2)(B)</a>, the inaccessibility of a data source is determined by how burdensome and costly the preservation and production of that data is, which will vary from client to client, and case to case. The information about the cost and burden of producing data from various sources can only come from the client. Thus, the client’s IT staff will play a key role in any attempt to establish that certain forms or sources of data are inaccessible, which is one of the first issues to address in any cost-shifting analysis.</p>
<p><strong>Evaluate the proportionality of the discovery being sought.</strong></p>
<p>The fact that the data to be produced is from an accessible source should not be the end of your cost-shifting analysis. “The ready accessibility of information, whether electronically stored or not, does not in itself require the production of that information.” <em>Peskoff v. Farber</em>, 244 F.3d 54, 59 (D.D.C. 2007).  Rule 26(b)(2)(C)’s proportionality factors are a relevant consideration for any discovery being sought, even accessible electronic data. Under Rule 26(b)(2)(C)’s proportionality principles, one factor that a court can consider in limiting discovery that would otherwise be allowed is whether:</p>
<blockquote><p>the burden or expense of the proposed discovery outweighs its likely benefit, considering the needs of the case, the amount in controversy, the parties’ resources, the importance of the issues at stake in the action, and the importance of the discovery in resolving the issues.</p></blockquote>
<p>When a party can demonstrate that the burden of producing the requested data is out of proportion to the amount in controversy or is not justified, on balance, by its potential relevancy to the issues at stake in the litigation, then a court may limit the requested discovery or condition its production upon a payment of some or all of its cost by the requesting party. Remember however, that courts require evidence of the burden involved, and as the <em>Proctor &#038; Gamble</em> decision teaches, courts will not shift the cost of ediscovery based on a mere assertion that the requested discovery is unduly burdensome or disproportionate.</p>
<p><strong>Evaluate the discovery your opponent requested.</strong></p>
<p>It seems fundamental, but don’t overlook the fact that courts generally won’t compel discovery that has not been sought. See <em>D’Onofrio v. SFX Sports Group, Inc.</em>, 247 F.R.D. 43, 48 (D.D.C. 2008). Carefully review the discovery your opponent has requested. If the requesting party has not sought production of electronic data in its native state with accompanying metadata fields, or in the case of TIFF or PDF images, has not requested OCR be added to the images, there is no need to necessarily produce the data with those features. </p>
<p><strong>Evaluate whether the data is created in a unique or unusual format.</strong></p>
<p>Data that is created and stored in unique or unusual formats can complicate how that data is produced, and your cost-shifting analysis. When electronic data is produced in its native state, to simply view the data, the party receiving it usually needs the same software application used to create the data. That is why the federal ediscovery rules provide that data may be produced in the format in which it is ordinarily maintained or in a reasonably useable form. Unless the party possessing data in a unique or unusual format can demonstrate that the cost of translating the requested data into a reasonably useable form is out of proportion with the amount at issue in the case, or that the relevancy of the data is marginal, that party will likely be forced to incur the cost of translating the data into another reasonably useable form.  </p>
<p><strong>Evaluate whether the data is electronically searchable in its “native state.”</strong></p>
<p>The 2006 <a href="http://www.law.cornell.edu/rules/frcp/ACRule34.htm">Advisory Committee Note to Rule 34(b)</a> specifies: “If the responding party ordinarily maintains the information it is producing in a way that makes it searchable by electronic means, the information should not be produced in a form that removes or significantly degrades this feature.” Generally speaking, the electronic data generated by many of today’s applications is electronically searchable at some level within the application. However, that point should always be confirmed. How easily native data can be searched depends on the particular application, and the volume of information involved.</p>
<p>However, producing data in its native state has several perceived disadvantages.  Application and system metadata, as well as any embedded comments or track changes accompany documents or data when produced in their native state. Moreover, electronic documents cannot be Bates stamped, and privileged or confidential information cannot be redacted from documents produced in their native state. Documents can also be altered after production has occurred in their native state.</p>
<p>These factors have led many parties to produce electronic data in an imaged (PDF or TIFF) format. However, without the addition of OCR, the imaged documents are not electronically searchable. The application of OCR to documents once they have been imaged permits them to be searched on a common platform. When different forms of data are produced natively, they generally have to be searched within their respective applications. Thus, the inclusion of OCR to imaged documents adds to the convenience of the search process as the defendant claimed in <em>Proctor &#038; Gamble</em>. Nonetheless, if a particular data set was electronically searchable in its native state, compliance with the Advisory Committee Note to Rule 34(b) may require that OCR be added when that data is produced in an imaged format.</p>
<p><strong>Evaluate Zubulake’s cost-shifting factors.</strong></p>
<p>Once the various issues noted above have been carefully considered, the cost-shifting factors outlined in <em>Zubulake</em> should be analyzed. Those factors, in order of their relative importance are:</p>
<ul>
<li>The extent to which the request is tailored to discover relevant information; </li>
<li>The availability of such information from other sources;</li>
<li>The total cost of production, compared to the amount in controversy;</li>
<li>The total cost of production, compared to the resources available to each party;</li>
<li>The relative ability of each party to control costs, and their incentive to do so;</li>
<li>The importance of the issues at stake in the litigation; and</li>
<li>The relative benefits to the parties of obtaining the information.</li>
</ul>
<p>The defendant in <em>Proctor &#038; Gamble</em> merely argued that plaintiff’s discovery requests were overbroad without any further explanation. That argument fell woefully short of meeting any of <em>Zubulake’s </em>cost-shifting factors in the court’s view. </p>
<p><strong>Other Relevant Considerations.</strong></p>
<p>Courts are unlikely to entertain any cost-shifting arguments where the producing party failed to adequately preserve the data from an accessible source. One district court, in responding to such an argument explained: “It reminds me of Leo Kosten’s definition of chutzpah: ‘that quality enshrined in a man who, after having killed his mother and father, throws himself on the mercy of the court because he is an orphan.” <em>Disability Rights Counsel of Greater Washington v. Washington Metro. Transit Authority</em>, 242 F.R.D. 139, 148 (D.D.C. 2007). </p>
<p>Finally, while this point may also seem fundamental, any cost-shifting argument should be brought before production occurs. Post production cost-shifting arguments are untimely, and will be rejected. See, e.g., <em>Cason-Medina v. Detroit Medical Center</em>, 2008 WL 2714239 (E.D. Mich. July 7, 2008). </p>
<p>As can be seen from this brief discussion of ediscovery cost-shifting, the factors to consider are numerous and varied. However, given the expense of electronic discovery, the analysis required is well worth the effort.  </p>
<p><em>Chess photo courtesy Flickr user <a href="http://flickr.com/photos/bootbearwdc/20109566/">dbking</a> under  <a href="http://creativecommons.org/licenses/by/2.0/deed.en">this Creative Commons license</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.hinshawlaw.com/practicalediscovery/2009/03/02/ocr-cost-shifting-rejected/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Email Routes and Locations</title>
		<link>http://blog.hinshawlaw.com/practicalediscovery/2009/02/20/email-routes-and-locations/</link>
		<comments>http://blog.hinshawlaw.com/practicalediscovery/2009/02/20/email-routes-and-locations/#comments</comments>
		<pubDate>Fri, 20 Feb 2009 22:26:23 +0000</pubDate>
		<dc:creator>Steve Puiszis</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[electronic data]]></category>
		<category><![CDATA[Preservation]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[locations]]></category>
		<category><![CDATA[routes]]></category>
		<category><![CDATA[storage]]></category>

		<guid isPermaLink="false">http://blog.hinshawlaw.com/practicalediscovery/?p=213</guid>
		<description><![CDATA[When we provide training on ediscovery, one of the issues we address is the various places where emails can be found, and the routes which they can take to get to those repositories. Because a picture is worth a thousand words, we worked with the head of our firm’s IT department to develop a PowerPoint [...]]]></description>
			<content:encoded><![CDATA[<p>When we provide training on ediscovery, one of the issues we address is  the various places where emails can be found, and the routes which they can take to get to those repositories. Because a picture is worth a thousand words, we worked with the head of our firm’s IT department to develop a PowerPoint slide that visually depicts this information which we now use in our training sessions.</p>
<p>We have attached our slide below, and if you click on the image, it will enlarge for your ease of reference. Admittedly, not every email system will have all of the various features shown on our slide, and there can be other repositories in some systems that we did not include, but our slide does provide a fairly comprehensive overview of the various “nooks and crannies” where emails can be found. </p>
<p>While it is not as complex as a map of New Orleans, our slide shows that the world wide web is not exactly an information superhighway. Rather, it’s more like a medieval European city where you can easily get lost if you can’t read the signs or know where you are going. Hopefully our slide will prevent you from getting lost, and will help you find what you are looking for.  </p>
<p><strong>[Click image to enlarge]</strong><br />
<a href="http://blog.hinshawlaw.com/practicalediscovery/wp-content/uploads/2009/02/potentialemailroutes.jpg"><img src="http://blog.hinshawlaw.com/practicalediscovery/wp-content/uploads/2009/02/potentialemailroutes.jpg" alt="Email routes image" width="600" height="450"></a></p>
<p>If you want to use this slide for any reason, just drop <a href="http://www.hinshawlaw.com/spuiszis">Steve</a> or <a href="http://www.hinshawlaw.com/ebrown">Evan</a> a note.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.hinshawlaw.com/practicalediscovery/2009/02/20/email-routes-and-locations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

