<?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>ediscoveryinfo &#187; Metadata</title>
	<atom:link href="http://www.ediscoveryinfo.com/category/metadata/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ediscoveryinfo.com</link>
	<description>Electronic Discovery in the News</description>
	<lastBuildDate>Wed, 16 Jun 2010 20:20:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Mastering Metadata</title>
		<link>http://www.ediscoveryinfo.com/2009/02/28/mastering-metadata/</link>
		<comments>http://www.ediscoveryinfo.com/2009/02/28/mastering-metadata/#comments</comments>
		<pubDate>Sat, 28 Feb 2009 06:50:25 +0000</pubDate>
		<dc:creator>Brett Burney</dc:creator>
				<category><![CDATA[Metadata]]></category>

		<guid isPermaLink="false">http://www.ediscoveryinfo.com/2009/02/28/mastering-metadata/</guid>
		<description><![CDATA[I&#8217;m happy to report that my article &#8220;Meaning in Metadata&#8221; was posted to InsideCounsel.com a few days ago.
If my article isn&#8217;t meaty enough for you, then you should absolutely read Browning Marean&#8217;s &#8220;Dealing with Confidential Metadata&#8221; that appeared on Law.com yesterday (originally published in Law Technology News). Browning does an excellent job of providing some [...]]]></description>
			<content:encoded><![CDATA[<p style="clear: both">I&#8217;m happy to report that my article &#8220;<a href="http://www.insidecounsel.com/Issues/2009/February%202009/Pages/Meaning-in-Metadata.aspx">Meaning in Metadata</a>&#8221; was posted to <a href="http://www.insidecounsel.com">InsideCounsel.com</a> a few days ago.</p>
<p style="clear: both">If my article isn&#8217;t meaty enough for you, then you should absolutely read Browning Marean&#8217;s &#8220;<a href="http://www.law.com/jsp/legaltechnology/pubArticleLT.jsp?id=1202428587901">Dealing with Confidential Metadata</a>&#8221; that appeared on <a href="http://www.law.com">Law.com</a> yesterday (originally <a href="http://www.lawtechnews.com/r5/showkiosk.asp?listing_id=3051816">published</a> in Law Technology News). Browning does an excellent job of providing some recent case law to suggest how best to deal with metadata. </p>
<p style="clear: both">I&#8217;m also happy to report that I will be co-presenting &#8220;A Project Management Approach to E-Discovery&#8221; with Browning at this year&#8217;s <a href="http://www.abanet.org/techshow/">ABA TECHSHOW</a> (<a href="http://www.abanet.org/techshow/register/">register</a> by Feb. 28 for early bird pricing!!). </p>
<p><br class="final-break" style="clear: both" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.ediscoveryinfo.com/2009/02/28/mastering-metadata/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Be &quot;Purposely Sluggish&quot; in E-Discovery&#8230;</title>
		<link>http://www.ediscoveryinfo.com/2008/08/25/purposely-sluggish/</link>
		<comments>http://www.ediscoveryinfo.com/2008/08/25/purposely-sluggish/#comments</comments>
		<pubDate>Mon, 25 Aug 2008 04:58:31 +0000</pubDate>
		<dc:creator>Brett Burney</dc:creator>
				<category><![CDATA[Case Law]]></category>
		<category><![CDATA[Ethics]]></category>
		<category><![CDATA[Federal]]></category>
		<category><![CDATA[Litigation Hold]]></category>
		<category><![CDATA[Metadata]]></category>
		<category><![CDATA[Preservation]]></category>
		<category><![CDATA[Production]]></category>
		<category><![CDATA[Sanctions]]></category>

		<guid isPermaLink="false">http://www.ediscoveryinfo.com/2008/08/25/purposely-sluggish/</guid>
		<description><![CDATA[I was reading over Cliff Shnier&#8217;s June 2008 column on InsideCounsel.com entitled &#34;A time to reap, a time to cull.&#34; It is an excellent, concise overview of the workflow required for a successful e-discovery project, sprinkled with several doses of common sense on collecting and processing ESI. 
Toward the end, Cliff discusses the perils of [...]]]></description>
			<content:encoded><![CDATA[<p>I was reading over <a href="http://www.cliffshnier.com/">Cliff Shnier&#8217;s</a> June 2008 column on <a href="http://www.indsidecounsel.com">InsideCounsel.com</a> entitled &quot;<a href="http://www.insidecounsel.com/section/ediscovery/1779">A time to reap, a time to cull</a>.&quot; It is an excellent, concise overview of the workflow required for a successful e-discovery project, sprinkled with several doses of common sense on collecting and processing ESI. </p>
<p>Toward the end, Cliff discusses the perils of too-hastily concocting a list of keywords used for filtering and culling electronic data. He points readers to <em><a href="http://electronicdiscoveryblog.com/cases/seroquel.pdf">In Re Seroquel Products Liability Litigation</a>, </em>244 F.R.D. 650 (D. Fla. 2007) (generously hosted on the <a href="http://www.electronicdiscoveryblog.com/">Electronic Discovery Blog</a>; good cases summaries located <a href="http://www.ediscoverylaw.com/2007/09/articles/case-summaries/sanctions-warranted-for-defendants-purposefully-sluggish-discovery-efforts-and-failure-to-produce-usable-or-reasonably-accessible-documents/">here</a> and <a href="http://ediscovery.renewdata.com/2007/09/articles/another-category/seroquel-products-liability-litigation/">here</a>).</p>
<p><img class="left" height="162" alt="sluggish e-discovery" src="http://ediscoveryinfo.bburney.net/wp-content/uploads/2008/08/j0315455.jpg" width="240" align="left" /> I dug a little deeper into the case, and discovered a fascinating litany of delinquent behavior surrounding basic principles of e-discovery. The Court was not happy.</p>
<p>First, the Court lists the shortcomings of defendant&#8217;s production:</p>
<blockquote><p><font color="#000000">&quot;&#8230; although [Defendant] has a system to deliver voicemail, faxes, and video into Outlook inboxes, none has been produced; there are few emails from some custodians, and email boxes are missing from alternative email boxes. Plaintiffs also contend that many relevant emails and documents were not identified and produced because [Defendant] performed an unreasonable key word search.&quot;</font></p>
</blockquote>
<p>And in a footnote, the Court provides some examples of words and phrases that were omitted from the &quot;unreasonable key word search:&quot;</p>
<blockquote><p>&quot;Seroquel&#8217;s generic name [(The case involves a slew of cases over the anti-psychotic drug Seroquel)], acronyms for diabetes, hyperglycaemia spelled the British way; and endocrine. The search method apparently failed to include common misspellings or the singular forms of words and failed to make allowance for spaces or dashes.&quot;</p></blockquote>
<p>The Court doesn&#8217;t let the issue rest:</p>
<blockquote><p>&quot;The key word search was plainly inadequate. &#8230; While key word searching is a recognized method to winnow relevant documents from large repositories, use of this technique must be a cooperative and informed process. rather than working with Plaintiffs from the outset to reach agreement on appropriate and comprehensive search terms and methods, [Defendant] undertook the task in secret.&quot;</p>
</blockquote>
<p>As you can imagine, the Court would have rather the parties agreed on a set of key words together. I especially like how the court ever-so-gingerly emphasized the importance of having technical expertise at these meetings:</p>
<blockquote><p><font color="#000000">&quot;Many of the other technical problems identified by Mr. Martin and Mr. Jaffe [e-discovery specialists for the plaintiff] likely could have been resolved far sooner and less expensively had [Defendant] cooperated by fostering consultation between the technical staffs responsible for production. Instead, [Defendant] shielded its third party technical contractor from all contact with Plaintiffs. This approach is antithetical to the Sedona Principles and is not an indicium of good faith.&quot;</font></p>
</blockquote>
<p>After dismissing other arguments from the Defendant, and recognizing that many of the disagreements could have easily been worked out in a more efficient manner, the Court provides a strong conclusion:</p>
<blockquote><p>&quot;The Court finds that [Defendant] has been <strong>&#8216;purposely sluggish&#8217;</strong> in making effective production to Plaintiffs. &#8230; It is undisputed that the [completed production] &#8230; had load file, metadata, page break and key word search problems, making the 10 million pages of documents <strong>unaccessible</strong>, <strong>unsearchable</strong>, and <strong>unusable</strong> as contemplated under the Rules.&quot;</p>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.ediscoveryinfo.com/2008/08/25/purposely-sluggish/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
