<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.lexblog.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
   <channel>
      <title>E-Discovery Law Review</title>
      <link>http://www.ediscoverylawreview.com/</link>
      <description>Electronic Discovery Lawyers &amp; Attorneys : Cozen O'Connor Law Firm : Data Preservation &amp; E-Discovery Disputes</description>
      <language>en</language>
      <copyright>Copyright 2012</copyright>
      <lastBuildDate>Wed, 11 Jan 2012 12:42:48 -0800</lastBuildDate>
      <pubDate>Wed, 11 Jan 2012 12:42:48 -0800</pubDate>
      <generator>http://www.movabletype.org</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <feedburner:info uri="e-discoverylawreview" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://www.ediscoverylawreview.com/index.xml" /><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" 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 href="http://www.bloglines.com/sub/http://www.ediscoverylawreview.com/index.xml" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><feedburner:feedFlare href="http://www.plusmo.com/add?url=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://plusmo.com/res/graphics/fbplusmo.gif">Subscribe with Plusmo</feedburner:feedFlare><feedburner:feedFlare href="http://www.thefreedictionary.com/_/hp/AddRSS.aspx?http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://img.tfd.com/hp/addToTheFreeDictionary.gif">Subscribe with The Free Dictionary</feedburner:feedFlare><feedburner:feedFlare href="http://www.bitty.com/manual/?contenttype=rssfeed&amp;contentvalue=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://www.bitty.com/img/bittychicklet_91x17.gif">Subscribe with Bitty Browser</feedburner:feedFlare><feedburner:feedFlare href="http://www.live.com/?add=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://tkfiles.storage.msn.com/x1piYkpqHC_35nIp1gLE68-wvzLZO8iXl_JMledmJQXP-XTBOLfmQv4zhj4MhcWEJh_GtoBIiAl1Mjh-ndp9k47If7hTaFno0mxW9_i3p_5qQw">Subscribe with Live.com</feedburner:feedFlare><feedburner:feedFlare href="http://mix.excite.eu/add?feedurl=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://image.excite.co.uk/mix/addtomix.gif">Subscribe with Excite MIX</feedburner:feedFlare><feedburner:feedFlare href="http://www.webwag.com/wwgthis.php?url=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://www.webwag.com/images/wwgthis.gif">Subscribe with Webwag</feedburner:feedFlare><feedburner:feedFlare href="http://www.podcastready.com/oneclick_bookmark.php?url=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://www.podcastready.com/images/podcastready_button.gif">Subscribe with Podcast Ready</feedburner:feedFlare><feedburner:feedFlare href="http://www.wikio.com/subscribe?url=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://www.wikio.com/shared/img/add2wikio.gif">Subscribe with Wikio</feedburner:feedFlare><feedburner:feedFlare href="http://www.dailyrotation.com/index.php?feed=http%3A%2F%2Fwww.ediscoverylawreview.com%2Findex.xml" src="http://www.dailyrotation.com/rss-dr2.gif">Subscribe with Daily Rotation</feedburner:feedFlare><item>
         <title>Score One for Plaintiffs in Battle Over Discoverability of Facebook</title>
         <description>&lt;p&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;o:OfficeDocumentSettings&gt;
&lt;o:AllowPNG /&gt;
&lt;/o:OfficeDocumentSettings&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;w:WordDocument&gt;
&lt;w:View&gt;Normal&lt;/w:View&gt;
&lt;w:Zoom&gt;0&lt;/w:Zoom&gt;
&lt;w:TrackMoves /&gt;
&lt;w:TrackFormatting /&gt;
&lt;w:PunctuationKerning /&gt;
&lt;w:ValidateAgainstSchemas /&gt;
&lt;w:SaveIfXMLInvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;
&lt;w:IgnoreMixedContent&gt;false&lt;/w:IgnoreMixedContent&gt;
&lt;w:AlwaysShowPlaceholderText&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;
&lt;w:DoNotPromoteQF /&gt;
&lt;w:LidThemeOther&gt;EN-US&lt;/w:LidThemeOther&gt;
&lt;w:LidThemeAsian&gt;X-NONE&lt;/w:LidThemeAsian&gt;
&lt;w:LidThemeComplexScript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;
&lt;w:Compatibility&gt;
&lt;w:BreakWrappedTables /&gt;
&lt;w:SnapToGridInCell /&gt;
&lt;w:WrapTextWithPunct /&gt;
&lt;w:UseAsianBreakRules /&gt;
&lt;w:DontGrowAutofit /&gt;
&lt;w:SplitPgBreakAndParaMark /&gt;
&lt;w:EnableOpenTypeKerning /&gt;
&lt;w:DontFlipMirrorIndents /&gt;
&lt;w:OverrideTableStyleHps /&gt;
&lt;/w:Compatibility&gt;
&lt;m:mathPr&gt;
&lt;m:mathFont m:val="Cambria Math" /&gt;
&lt;m:brkBin m:val="before" /&gt;
&lt;m:brkBinSub m:val="&amp;#45;-" /&gt;
&lt;m:smallFrac m:val="off" /&gt;
&lt;m:dispDef /&gt;
&lt;m:lMargin m:val="0" /&gt;
&lt;m:rMargin m:val="0" /&gt;
&lt;m:defJc m:val="centerGroup" /&gt;
&lt;m:wrapIndent m:val="1440" /&gt;
&lt;m:intLim m:val="subSup" /&gt;
&lt;m:naryLim m:val="undOvr" /&gt;
&lt;/m:mathPr&gt;&lt;/w:WordDocument&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
DefSemiHidden="true" DefQFormat="false" LatentStyleCount="267"&gt;
&lt;w:LsdException Locked="false" SemiHidden="false" UnhideWhenUsed="false"
QFormat="true" Name="Normal" /&gt;
&lt;w:LsdException Locked="false" SemiHidden="false" UnhideWhenUsed="false"
QFormat="true" Name="heading 1" /&gt;
&lt;w:LsdException Locked="false" QFormat="true" Name="heading 2" /&gt;
&lt;w:LsdException Locked="false" QFormat="true" Name="heading 3" /&gt;
&lt;w:LsdException Locked="false" QFormat="true" Name="heading 4" /&gt;
&lt;w:LsdException Locked="false" QFormat="true" Name="heading 5" /&gt;
&lt;w:LsdException Locked="false" QFormat="true" Name="heading 6" /&gt;
&lt;w:LsdException Locked="false" QFormat="true" Name="heading 7" /&gt;
&lt;w:LsdException Locked="false" QFormat="true" Name="heading 8" /&gt;
&lt;w:LsdException Locked="false" QFormat="true" Name="heading 9" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="header" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="footer" /&gt;
&lt;w:LsdException Locked="false" QFormat="true" Name="caption" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="line number" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="page number" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="endnote reference" /&gt;
&lt;w:LsdException Locked="false" SemiHidden="false" UnhideWhenUsed="false"
QFormat="true" Name="Title" /&gt;
&lt;w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /&gt;
&lt;w:LsdException Locked="false" SemiHidden="false" UnhideWhenUsed="false"
QFormat="true" Name="Subtitle" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="FollowedHyperlink" /&gt;
&lt;w:LsdException Locked="false" Priority="22" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Strong" /&gt;
&lt;w:LsdException Locked="false" SemiHidden="false" UnhideWhenUsed="false"
QFormat="true" Name="Emphasis" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="HTML Top of Form" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="HTML Bottom of Form" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="HTML Acronym" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="HTML Cite" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="HTML Code" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="HTML Definition" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="HTML Keyboard" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="HTML Sample" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="HTML Typewriter" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="HTML Variable" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Normal Table" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Outline List 1" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Outline List 2" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Outline List 3" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Simple 1" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Simple 2" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Simple 3" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Classic 1" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Classic 2" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Classic 3" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Classic 4" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Colorful 1" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Colorful 2" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Colorful 3" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Columns 1" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Columns 2" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Columns 3" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Columns 4" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Columns 5" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Grid 1" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Grid 2" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Grid 3" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Grid 4" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Grid 5" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Grid 6" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Grid 7" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Grid 8" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table List 1" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table List 2" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table List 3" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table List 4" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table List 5" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table List 6" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table List 7" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table List 8" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table 3D effects 1" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table 3D effects 2" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table 3D effects 3" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Contemporary" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Elegant" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Professional" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Subtle 1" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Subtle 2" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Web 1" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Web 2" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Web 3" /&gt;
&lt;w:LsdException Locked="false" SemiHidden="false" UnhideWhenUsed="false"
Name="Table Grid" /&gt;
&lt;w:LsdException Locked="false" Priority="99" Name="Table Theme" /&gt;
&lt;w:LsdException Locked="false" Priority="99" UnhideWhenUsed="false"
Name="Placeholder Text" /&gt;
&lt;w:LsdException Locked="false" Priority="1" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="99" UnhideWhenUsed="false"
Name="Revision" /&gt;
&lt;w:LsdException Locked="false" SemiHidden="false" UnhideWhenUsed="false"
QFormat="true" Name="List Paragraph" /&gt;
&lt;w:LsdException Locked="false" Priority="29" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Quote" /&gt;
&lt;w:LsdException Locked="false" Priority="30" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="19" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /&gt;
&lt;w:LsdException Locked="false" Priority="21" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /&gt;
&lt;w:LsdException Locked="false" Priority="31" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /&gt;
&lt;w:LsdException Locked="false" Priority="32" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /&gt;
&lt;w:LsdException Locked="false" Priority="33" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Book Title" /&gt;
&lt;w:LsdException Locked="false" Priority="37" Name="Bibliography" /&gt;
&lt;w:LsdException Locked="false" QFormat="true" Name="TOC Heading" /&gt;
&lt;/w:LatentStyles&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
&lt;/style&gt;
&lt;![endif]--&gt;&lt;img hspace="10" align="left" vspace="10" alt="" style="width: 131px; height: 118px;" src="http://www.ediscoverylawreview.com/uploads/image/facebook-privacy1.png" /&gt;In the most recent decision to come out of Pennsylvania regarding the discoverability of social media, a Philadelphia judge denied a defendant&amp;rsquo;s request to gain access to a plaintiff&amp;rsquo;s Facebook page.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;In &lt;i style="mso-bidi-font-style:normal"&gt;Martin v. Allstate Fire and Casualty Co&lt;/i&gt;., Case No. 110402438 (C.P. Phila. Dec. 13, 2011), the plaintiff, a pedestrian, was hit by a vehicle driven by a third-party tortfeasor.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;The plaintiff collected the policy limit from the third-party&amp;rsquo;s insurer and then demanded the Uninsured Motorist coverage from her own insurer, the defendant.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;During her deposition in October, defense counsel asked the plaintiff if she used Facebook, to which she responded that she did.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Upon asking for her password, defense counsel was met with an immediate objection.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;In return, defense counsel filed a Motion to Compel such information.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Counsel for the plaintiff responded in opposition, arguing that any information on the plaintiff&amp;rsquo;s Facebook is not relevant to her claims or injuries and does not contradict her claims.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;In a one-page, single-line Order, Judge Manfredi agreed and denied defendant&amp;rsquo;s Motion.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;This decision follows a November ruling from Judge Walsh, who determined that information posted on the plaintiff&amp;rsquo;s Facebook page was relevant and not privileged, and therefore discoverable.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;i style="mso-bidi-font-style:normal"&gt;See Largent v. Reed&lt;/i&gt;, Case No. 2009-1823 (C.P. Franklin Nov. 8, 2011); &lt;i style="mso-bidi-font-style:normal"&gt;see also&lt;/i&gt; &lt;a href="http://www.ediscoverylawreview.com/2011/12/articles/opinions/post-at-your-own-risk-pennsylvania-court-permits-discovery-of-information-on-personal-facebook-profile/"&gt;www.ediscoverylawreview.com/2011/12/articles/opinions/post-at-your-own-risk-pennsylvania-court-permits-discovery-of-information-on-personal-facebook-profile/&lt;/a&gt;.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Largent, along with two other defense-friendly decisions, &lt;i style="mso-bidi-font-style:normal"&gt;Zimmerman v. Weis Markets Inc., &lt;/i&gt;Case No. CV-09-1535 (C.P. Northumberland May 19, 2011) and &lt;i style="mso-bidi-font-style:
normal"&gt;McMillen v. Hummingbird Speedway Inc.,&lt;/i&gt; Case No. 113-2010CD (C.P. Jefferson Sept. 9, 2010)&lt;i style="mso-bidi-font-style:normal"&gt; &lt;/i&gt;got the defense bar out to a 3-0 lead on the discoverability of information posted on Facebook.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;While the &lt;i style="mso-bidi-font-style:
normal"&gt;Martin&lt;/i&gt; decision scores a big point for plaintiffs, it demonstrates that there is still a lot of uncertainty in the law surrounding the recent phenomenon of social media and its relevance to civil litigation.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/ybxOd1driB0" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/ybxOd1driB0/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2012/01/articles/score-one-for-plaintiffs-in-battle-over-discoverability-of-facebook/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/tags">Facebook</category><category domain="http://www.ediscoverylawreview.com/tags">Social Media</category><category domain="http://www.ediscoverylawreview.com/tags">discovery</category><category domain="http://www.ediscoverylawreview.com/tags">discovery of social media in lawsuits</category><category domain="http://www.ediscoverylawreview.com/tags">discovery of social networking sites</category><category domain="http://www.ediscoverylawreview.com/tags">social media and disclosure of confidential information</category>
         <pubDate>Wed, 11 Jan 2012 12:31:13 -0800</pubDate>
         <dc:creator>Calli Varner</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2012/01/articles/score-one-for-plaintiffs-in-battle-over-discoverability-of-facebook/</feedburner:origLink></item>
            <item>
         <title>Top Ten E-Discovery Lessons For 2011</title>
         <description>&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; As we bid adieu to 2011, the news and entertainment world is a flurry with the year&amp;rsquo;s greatest hits and most memorable, or un-memorable, moments.&amp;nbsp;In the spirit of the season, and with homage to the great David Letterman, here are our Top Ten E-Discovery Lessons as addressed by the courts &amp;ndash; and this Blog &amp;ndash; this past year:&lt;/p&gt;
&lt;p&gt;&lt;b&gt;10.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Know Your Responsibilities&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; In-house and outside counsel have a duty to ensure that their clients comply with e-discovery obligations.&amp;nbsp;In- house counsel&amp;rsquo;s failure to give notice to preserve documents; provide criteria as to what should be saved; review documents being discarded; and failure to review existing document retention policies led to e-discovery sanctions.&amp;nbsp;&lt;i&gt;See &lt;/i&gt;&amp;ldquo;&lt;b&gt;&lt;i&gt;I&amp;rsquo;m Responsible To Do What?&amp;rdquo;&lt;/i&gt;&lt;/b&gt; posted On Aug. 18, 2011.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;&lt;b&gt;9.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Know When The Duty To Preserve Arises&lt;/b&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; The duty to preserve electronic evidence arises once a party &amp;ldquo;reasonably anticipates litigation.&amp;rdquo;&amp;nbsp;Whether and when a party reasonably anticipates litigation depends on many factors, including but not limited to, who within the defendant organization anticipates the litigation, the clarity of the threat, and when privileged documents are created and labeled as such.&amp;nbsp;&lt;i&gt;See&lt;/i&gt; &lt;b&gt;&lt;i&gt;&amp;ldquo;When Does The Duty To Preserve Electronic Evidence Arise,&amp;rdquo; &lt;/i&gt;&lt;/b&gt;posted on Aug. 10, 2011.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;&lt;b&gt;8.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Know When To Issue A Litigation Hold&lt;/b&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; A litigation hold should be issued when a party is reasonably aware that it will be a party to litigation.&amp;nbsp;For a plaintiff, triggers could include filing a complaint, seeking advice of counsel, or sending a cease and desist letter.&amp;nbsp;For a defendant, triggers could include receiving a summons or complaint, receiving official notice of a government investigation, or receiving notice of an accident,&amp;nbsp;or receiving discovery requests.&amp;nbsp;&lt;i&gt;See &lt;b&gt;&amp;ldquo;Litigation Holds, Take 1,&amp;rdquo; &lt;/b&gt;&lt;/i&gt;posted on Aug. 12, 2011.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;&lt;b&gt;7.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Know What A Litigation Hold Should Cover&lt;/b&gt;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/b&gt;A Litigation Hold should describe the litigation in general terms with understandable language, and avoid legal terms at all costs.&amp;nbsp; It should broadly state where relevant data and information could be located and it should provide instructions on how to preserve relevant information.&amp;nbsp;The consequences of non-compliance and the importance of not destroying or altering relevant information should be discussed.&amp;nbsp; &lt;i&gt;See &lt;b&gt;&amp;ldquo;Litigation Holds, Take 2,&amp;rdquo; &lt;/b&gt;&lt;/i&gt;posted on Aug. 16, 2011.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;&lt;b&gt;6.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Know Your Sources Of Potentially Relevant Information&lt;/b&gt;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Explore all types of data.&amp;nbsp;For example, this year, courts in Pennsylvania ruled that text messages and Facebook posts are discoverable.&amp;nbsp;&lt;i&gt;See &lt;b&gt;&amp;ldquo;When Are Text Messages Admissible,&amp;rdquo; &lt;/b&gt;&lt;/i&gt;posted on Oct. 7, 2011; &amp;ldquo;&lt;b&gt;&lt;i&gt;Post At Your Own Risk,&amp;rdquo; &lt;/i&gt;&lt;/b&gt;posted on Dec. 5, 2011.&amp;nbsp;&lt;i&gt;See also&lt;/i&gt; &lt;b&gt;&lt;i&gt;When An Employee Tweets,&lt;/i&gt;&lt;/b&gt; posted on Sept. 7, 2011.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;&lt;b&gt;5.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Know The Standards Governing Production And How They Are Applied&lt;/b&gt;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Courts have applied the proportionality standard with much variation in 2011.&amp;nbsp;For example, in &lt;i&gt;Pippins v. KPMG, &lt;/i&gt;the court ordered the defense, who had already spent over $1,500,000 in preservation costs, to preserve the hard drives of over 7500 potential class members.&amp;nbsp;The court reasoned that there were too many unknowns, such as the ultimate length and cost of preservation, the relevance of the information on the hard drives, and the outcome of the motion for class certification to allow the hard drives to be destroyed.&amp;nbsp;&lt;i&gt;See&lt;/i&gt; &lt;b&gt;&lt;i&gt;&amp;ldquo;Weighing Burdens And Benefits In Hard Drive Preservation Dispute,&amp;rdquo; &lt;/i&gt;&lt;/b&gt;posted on Oct. 31, 2011.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; In &lt;i&gt;I-Med Pharma Inc v. Biomatrix, Inc., &lt;/i&gt;by contrast, the court did not require the plaintiff to produce documents from &amp;ldquo;unallocated space&amp;rdquo; (&lt;i&gt;i.e., &lt;/i&gt;the area where deleted files and temporary data are stored) because of the overwhelming cost in terms of time and money to do so and because the requesting party failed to show a likelihood that relevant and non-duplicative information would be recovered. &amp;nbsp;&lt;i&gt;See&lt;/i&gt;&lt;b&gt; &lt;i&gt;&amp;ldquo;The Importance Of Negotiating With Your Adversaries,&amp;rdquo; &lt;/i&gt;&lt;/b&gt;posted on Dec. 23, 2011.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;&lt;b&gt;4.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Know The Consequences Of Non-Compliance&lt;/b&gt;&lt;/p&gt;
&lt;p style="text-indent: 0.5in; margin: 12pt 0in 0pt"&gt;Sanctions in the form of adverse inferences, admitted facts, default judgment and fines continued to be levied in 2011.&amp;nbsp;For example, the deliberate destruction of evidence despite knowledge of a Litigation Hold provided grounds for a default judgment.&amp;nbsp;&lt;i&gt;See &lt;b&gt;&amp;ldquo;Document Preservation: Spoliation And The Ultimate Sanction,&amp;rdquo; &lt;/b&gt;&lt;/i&gt;posted on Nov. 14, 2011.&lt;/p&gt;
&lt;p style="text-indent: 0.5in; margin: 12pt 0in 0pt"&gt;Another court, faced with defendants who were &amp;ldquo;unsophisticated in the requirements of litigation and preservation&amp;rdquo; rather than willfully destructive and who produced 7 computers, 10 hard drives, and 23 CDs of documents, concluded that the plaintiff had &amp;ldquo;plenty of information upon which to pursue their claims&amp;rdquo; and&amp;nbsp;required a stronger showing of bad faith before granting a default judgment.&amp;nbsp;&lt;i&gt;See &lt;b&gt;&amp;ldquo;Document Preservation: Spoliation And The Ultimate Sanction,&amp;rdquo; &lt;/b&gt;&lt;/i&gt;posted on Nov. 14, 2011.&lt;/p&gt;
&lt;p style="text-indent: 0.5in; margin: 12pt 0in 0pt"&gt;A defendant&amp;rsquo;s refusal to disseminate a Court Order to preserve electronic evidence led to an adverse inference and a presumption of relevance when electronic discovery is willfully destroyed.&amp;nbsp;&lt;i&gt;See&lt;/i&gt; &lt;b&gt;&lt;i&gt;&amp;ldquo;E-Discovery Abuses Result In Permissive Adverse Inference Instruction,&amp;rdquo; &lt;/i&gt;&lt;/b&gt;posted on Dec. 23, 2011.&lt;/p&gt;
&lt;p style="text-indent: 0.5in; margin: 12pt 0in 0pt"&gt;A defendant who failed to: issue a litigation hold; conduct any email search; or seek its IT department&amp;rsquo;s assistance; and, instead, instructed employees to delete electronic documents at least ten times during the litigation was fined and ordered to file a copy of the court&amp;rsquo;s memorandum and order with its first pleading or filing in every case in which the defendant was involved for the next five years.&amp;nbsp;&lt;i&gt;See &lt;b&gt;&amp;ldquo;Ensuring Discovery Compliance: Sanctions Relating To Past, Present And Future Adverse Parties,&amp;rdquo; &lt;/b&gt;&lt;/i&gt;posted on Sept. 22, 2011.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;&lt;b&gt;3.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Know The Electronic Discovery Obligations of Non-Parties&lt;/b&gt;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; In &lt;em&gt;Tender v. Cremer&lt;/em&gt;, New York&amp;rsquo;s Appellate Division ruled that while a non-party need not&amp;nbsp;provide discovery of ESI from sources that are not reasonably accessible because of undue burden or cost except upon a showing of good cause, such good cause exists when the information at issue goes directly to the plaintiff&amp;rsquo;s claim. Under &lt;em&gt;Tender&lt;/em&gt;, nonparties served with subpoenas for deleted ESI may not rely on the fact that the data has been deleted in the course of its normal business as a means for avoiding the costs of complying with the subpoena. Instead, the nonparty should undertake an active investigation into whether the data can be retrieved, the difficulty of such retrieval and the concomitant costs. &lt;em&gt;See&lt;/em&gt;&lt;strong&gt;&lt;em&gt; &amp;ldquo;Cost-Benefit Analysis Adopted By The New York Supreme Court For Determining When A Nonparty Must Undertake The Burden And Expense Of Recovering Deleted ESI,&amp;rdquo; &lt;/em&gt;&lt;/strong&gt;posted on Sept. 27, 2011.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Know When Electronic Discovery Costs Can Be Recovered&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Over $500,000 in costs related to processing native files, restoring back-up tape files, hosting and storing documents in electronic databases, scanning hard copy documents, de-duplicating documents, and filtering documents to capture the documents containing the agreed-upon search terms were awarded to prevailing defendants. &lt;em&gt;See&lt;/em&gt; &lt;strong&gt;&lt;em&gt;&amp;ldquo;Prevailing Parties May Recover E-Discovery Costs Under The Federal Rules&lt;/em&gt;&lt;/strong&gt;,&amp;rdquo; posted on Aug. 30, 2011.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Under 35 U.S.C. &amp;sect; 285 (which allows the court to award a prevailing party in a patent dispute reasonable attorney&amp;rsquo;s fees in &amp;ldquo;exceptional cases&amp;rdquo;), a plaintiff was sanctioned nearly $500,000 for litigation misconduct after adopting a policy that it would not retain relevant documents.&lt;em&gt; See &lt;/em&gt;&lt;strong&gt;&lt;em&gt;&amp;ldquo;Cost Recovery Toolbox: Exceptional Cases under 35 U.S.C. &amp;sect; 285,&amp;rdquo; &lt;/em&gt;&lt;/strong&gt;posted on Aug. 19, 2011.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 28 U.S.C. &amp;sect; 1920, similarly, was used to reimburse successful defendants for over $367,000 in e-discovery costs. These costs included those incurred by third-party vendors to produce the requested electronic documents. The court deemed these services to be &amp;ldquo;an indispensable part of the discovery process&amp;rdquo; and their costs to be recoverable. &lt;em&gt;See&lt;/em&gt; &lt;strong&gt;&lt;em&gt;&amp;ldquo;Recovering E-Discovery Costs In Federal Court,&amp;rdquo; &lt;/em&gt;&lt;/strong&gt;posted on June 16, 2011.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Know Thyself&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Know the rules, your obligations, and when they are triggered. Know your company and the types of ESI you produce and store. Know how to be flexible and transparent with the E-Discovery process to comply with the rules in a manner that is reasonable, proportional, and cost effective.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; It has been our pleasure to bring you this E-Discovery Law Review this year and we look forward to continuing to keep you up to date in 2012. Please accept our best wishes for a happy and healthy New Year and, as always, Happy Reading!&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;p style="margin: 12pt 0in 0pt"&gt;&lt;span style="font-family: Symbol"&gt;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/eXgk_OEpIac" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/eXgk_OEpIac/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/12/articles/top-ten-ediscovery-lessons-for-2011/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category>
         <pubDate>Thu, 29 Dec 2011 12:28:19 -0800</pubDate>
         <dc:creator>MaryTeresa Soltis</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/12/articles/top-ten-ediscovery-lessons-for-2011/</feedburner:origLink></item>
            <item>
         <title>The Importance of Negotiating with Your Adversaries:  New Jersey Federal Court Spares Plaintiff a Large-Scale Document Review</title>
         <description>&lt;p&gt;&lt;img alt="" align="left" width="170" height="244" src="http://www.ediscoverylawreview.com/uploads/image/shutterstock_83550541.jpg" /&gt;&amp;nbsp;&lt;/p&gt;
&lt;p style="line-height: 200%; margin: 12pt 0in 0pt"&gt;We live in a digital world where smartphones are the norm and email access is seemingly as important as food and water.&amp;nbsp;This increase in usage of email and the amount of electronic data requires companies to develop ways to collect and store a significant amount of data.&amp;nbsp;Inevitably, this data will have to be searched, reviewed, and produced to opposing parties in the event of litigation and often at great cost to the producing party.&amp;nbsp;Fortunately for one plaintiff, however, this is a cost that it will not have to incur.&lt;/p&gt;
&lt;p style="line-height: 200%; text-indent: 0.5in; margin: 12pt 0in 0pt"&gt;In &lt;i&gt;I-Med Pharma Inc. v. Biomatrix, Inc.&lt;/i&gt;, 2011 U.S. Dist. LEXIS 141614 (D. N.J. Dec. 9, 2011), Judge Debevoise was asked to consider whether the plaintiff was required to produce documents from so-called &amp;ldquo;unallocated space&amp;rdquo; areas on its computers, namely, the area of the computer where deleted files and temporary data are stored.&amp;nbsp;The parties stipulated that the defendants would hire an expert to conduct a &amp;ldquo;forensic investigation&amp;rdquo; and keyword search of the plaintiff&amp;rsquo;s entire computer system, using over 50 search terms.&amp;nbsp;This search was not limited to specific custodians or time periods and, in the unallocated space alone, the search terms yielded an estimated 65 million &amp;ldquo;hits,&amp;rdquo; or 95 million pages of files.&amp;nbsp;In light of this, the Magistrate Judge modified a previous order, which required the plaintiff to produce the results of the forensic investigation and allowed the plaintiff to exclude data from the unallocated space.&lt;/p&gt;
&lt;p style="line-height: 200%; text-indent: 0.5in; margin: 12pt 0in 0pt"&gt;In reviewing the Magistrate Judge&amp;rsquo;s modification, the Court acknowledged the overwhelming burden to the plaintiff if it had to review the documents from the unallocated space.&amp;nbsp;The Court further explained that a &amp;ldquo;privilege review of 65 million documents is no small undertaking&amp;rdquo; and that &amp;ldquo;[e]ven if junior attorneys are engaged, heavily discounted rates are negotiated, and all parties work diligently and efficiently, even a cursory review of that many documents will consume large amounts of attorney time and cost millions of dollars.&amp;rdquo;&lt;/p&gt;
&lt;p style="line-height: 200%; text-indent: 0.5in; margin: 12pt 0in 0pt"&gt;The Court also recognized that the defendants did not show the likelihood that relevant and non-duplicative information was stored in the unallocated space.&amp;nbsp;Additionally, the Court found that the money the defendants spent to obtain the data &amp;ldquo;pale[d] in comparison&amp;rdquo; to the cost the plaintiff would incur to review the data.&lt;/p&gt;
&lt;p style="line-height: 200%; text-indent: 0.5in; margin: 12pt 0in 0pt"&gt;Finally, the Court addressed the proposed search terms and discussed five factors to consider when analyzing whether those terms were reasonable: &amp;ldquo;(1) the scope of documents searched and whether the search is restricted to specific computers, file systems, or document custodians; (2) any date restrictions imposed on the search; (3) whether the search terms contain proper names, uncommon abbreviations, or other terms unlikely to occur in irrelevant documents; (4) whether operators such as &amp;lsquo;and&amp;rsquo;, &amp;lsquo;not&amp;rsquo;, or &amp;lsquo;near&amp;rsquo; are used to restrict the universe of possible results; [and] (5) whether the number of results obtained could be practically reviewed given the economics of the case and the amount of money at issue.&amp;rdquo;&amp;nbsp;The Court examined all of these factors and stated that although the plaintiff should have &amp;ldquo;known better than to agree to the search terms . . . the interest of justice and basic fairness are little served by forcing Plaintiff to undertake an enormously expensive privilege review of material that is unlikely to contain non-duplicative evidence.&amp;rdquo;&lt;/p&gt;
&lt;p style="line-height: 200%; text-indent: 0.5in; margin: 12pt 0in 0pt"&gt;The plaintiff in &lt;i&gt;I-Med Pharma Inc.&lt;/i&gt; was fortunate in that the Court did not force it to review and produce all of the data in the unallocated space.&amp;nbsp;Not all parties, however, will always be as fortunate.&amp;nbsp;When negotiating with the adverse party regarding the search terms to be utilized for a document production, the following steps may avoid situations similar to those facing the parties in &lt;i&gt;I-Med Pharma Inc.&lt;/i&gt;:&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 0.75in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;b&gt;&lt;i&gt;Know your client&amp;rsquo;s data system.&lt;/i&gt;&lt;/b&gt;&amp;nbsp;This may be the most obvious, but most important, advice.&amp;nbsp;To negotiate effectively, you must know certain aspects of the data storage system, such as how much data is contained there, how many potential custodians exist, how long is data retained, and where potentially duplicative data resides.&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 0.75in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;b&gt;&lt;i&gt;Negotiate for the use of restricting terms.&lt;/i&gt;&lt;/b&gt;&amp;nbsp;This is especially true with frequently used words.&amp;nbsp;For example, in &lt;i&gt;I-Med Pharma Inc.&lt;/i&gt;, one of the search terms was the word &amp;ldquo;return.&amp;rdquo;&amp;nbsp;Negotiate for the use of search operators, such as &amp;ldquo;and,&amp;rdquo; &amp;ldquo;not,&amp;rdquo; or &amp;ldquo;near&amp;rdquo; in an attempt to further limit your results.&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 0.75in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;b&gt;&lt;i&gt;Do a sampling first.&lt;/i&gt;&lt;/b&gt;&amp;nbsp;If possible, run a search with proposed terms to determine what types of &amp;ldquo;false positives&amp;rdquo; may result.&amp;nbsp;This will enable the parties to further analyze the negotiated search terms and their effectiveness.&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 0.75in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;b&gt;&lt;i&gt;Determine relevant time periods and custodians.&lt;/i&gt;&amp;nbsp;&lt;/b&gt;Limit searches to only those individuals who had a role in the subject matter of the litigation and to only that time period in which relevant documents may exist.&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 0.75in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;b&gt;&lt;i&gt;Be willing to seek the Court&amp;rsquo;s assistance.&lt;/i&gt;&lt;/b&gt;&amp;nbsp;&lt;i&gt;I-Med Pharma&lt;/i&gt; demonstrates the efficacy of seeking the Court&amp;rsquo;s involvement early on to limit the costs associated with e-discovery.&amp;nbsp;When doing so, however, make sure you have done your proverbial homework and are able to educate the Court as to your client&amp;rsquo;s data systems and what the search proposed by the opposing side truly entails.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/yIbj9I68G_w" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/yIbj9I68G_w/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/12/articles/the-importance-of-negotiating-with-your-adversaries-new-jersey-federal-court-spares-plaintiff-a-largescale-document-review/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/tags">ESI</category><category domain="http://www.ediscoverylawreview.com/tags">Modification</category><category domain="http://www.ediscoverylawreview.com/tags">agreement</category><category domain="http://www.ediscoverylawreview.com/tags">courts</category><category domain="http://www.ediscoverylawreview.com/tags">discovery</category><category domain="http://www.ediscoverylawreview.com/tags">e-discovery</category><category domain="http://www.ediscoverylawreview.com/tags">negotiations</category><category domain="http://www.ediscoverylawreview.com/tags">search</category><category domain="http://www.ediscoverylawreview.com/tags">terms</category>
         <pubDate>Fri, 23 Dec 2011 12:04:24 -0800</pubDate>
         <dc:creator>F Brenden Coller</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/12/articles/the-importance-of-negotiating-with-your-adversaries-new-jersey-federal-court-spares-plaintiff-a-largescale-document-review/</feedburner:origLink></item>
            <item>
         <title>E-Discovery Abuses Result in Permissive Adverse Inference Instruction</title>
         <description>&lt;p&gt;&lt;img width="100" vspace="0" border="0" align="left" hspace="10" height="55" src="http://www.ediscoverylawreview.com/uploads/image/deleteButton(1).jpg" alt="Delete Button" /&gt;At 3:40 on the morning of April 3, 2003, Tamara Greene, an exotic dancer, was shot multiple times and killed while sitting in a car at the intersection of Roselawn and West Outer Drive in Detroit.&amp;nbsp;According to the complaint filed by Greene&amp;rsquo;s next of kin in &lt;i&gt;Flagg v. City of Detroit and Kwame Kilpatrick&lt;/i&gt;, (E.D. Mi. Nov. 7, 2005), the head of the Internal Affairs Department of the Detroit Police Department was fired a mere nine days following Ms. Greene&amp;rsquo;s murder.&amp;nbsp;It is alleged he was dismissed for investigating a party at the Mayor&amp;rsquo;s mansion, known as the Manoogian Mansion, during which exotic dancers, including Ms. Greene, performed.&amp;nbsp;As a result of this firing, the &lt;i&gt;Flagg&lt;/i&gt; complaint alleged that members of the Detroit Homicide Department refused to investigate the Greene murder case for fear of losing their jobs.&amp;nbsp;The &lt;i&gt;Flagg&lt;/i&gt; complaint further alleged that the case was labeled &amp;ldquo;cold&amp;rdquo; only eleven months following the crime, which falls well short of the two-year period typically required by the cold case squad. &amp;nbsp;Most shockingly, plaintiffs contend that the Police Department deliberately avoided sending the spent casings and bullets collected from the crime scene to the appropriate agency to determine if they came from the gun of a Detroit Police Officer.&amp;nbsp;Against this backdrop, we examine the decision rendered by Chief Judge Rosen in this case on October 5, 2011 in which he finds that the defendants deliberately deleted relevant emails in bad faith and failed to disseminate a Court Order to preserve evidence to the appropriate city departments.&amp;nbsp;2011 U.S. Dist. LEXIS 114772 (E.D. Mi. Oct. 5, 2011).&amp;nbsp;Judge Rosen&amp;rsquo;s searing opinion highlights several key electronic discovery issues, including the presumption of relevance that will attach where discovery is destroyed willfully and the parameters of the permissive adverse inference sanction.&lt;/p&gt;
&lt;p&gt;Judge Rosen initially adopted the Report and Recommendation of Magistrate Judge R. Steven Whalen recommending that the Court give a &lt;i&gt;permissive adverse inference&lt;/i&gt; instruction at any eventual trial to sanction the electronic discovery abuses of defendants, including the destruction of incoming and outgoing emails to and from the accounts of former Mayor Kwame Kilpatrick, his Chief of Staff, former &amp;ldquo;corporation counsel&amp;rdquo; and the former Chief of Police.&amp;nbsp;The Report also found that the City failed to advise the appropriate City Departments of the Court&amp;rsquo;s Order to preserve relevant evidence.&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt; at *5.&amp;nbsp;Both Plaintiffs and Defendants objected to the Report.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Defendants &amp;ldquo;express[ed] confusion&amp;rdquo; as to the basis for the Magistrate&amp;rsquo;s conclusion that the lost emails were relevant &amp;ndash; a finding necessary for an adverse inference instruction &amp;ndash; given that the four individuals whose accounts were deleted testified that they did not send any emails concerning the homicide investigation.&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt; at *6.&amp;nbsp;Judge Rosen agreed with the Magistrate that &amp;ldquo;the law expressly dictates a finding of relevance where, as here, it is determined that evidence has been &amp;lsquo;destroyed in bad faith (i.e. intentionally or willfully&amp;rdquo;).&amp;rdquo; &amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Next Defendants argued that the evidence did not support the Magistrate&amp;rsquo;s finding that the City and its counsel failed to take action to disseminate to the appropriate City Departments the Court&amp;rsquo;s March 5, 2008 Order to preserve evidence.&amp;nbsp;Defendants pointed to the Chief of Staff&amp;rsquo;s knowledge of the Order as evidence that the Order was distributed.&amp;nbsp;The Court concluded, however, that there was nothing to suggest her knowledge was a result of any action by the City or its in-house counsel.&amp;nbsp;Defendants also relied on the testimony of the former Police Chief that she was advised of the Order and prepared a memo to the Detroit Police Department advising them of it.&amp;nbsp;The Court, however, discredited the Chief&amp;rsquo;s testimony given that she was unable to recall the date of the memo and whether it was actually based on the March 5, 2008 preservation Order.&amp;nbsp;The Court also found suspect the fact that the Chief testified that her outside counsel was involved in preparation of the memo despite the fact that he did not enter an appearance on her behalf until April 7, 2008.&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt; at 9.&lt;/p&gt;
&lt;p&gt;The City argued its &amp;ldquo;corporation counsel&amp;rdquo; disseminated the March 5, 2008 Order with the assistance of an outside law firm that was acting as its co-counsel at the time.&amp;nbsp;However, the testimony of the &amp;ldquo;corporation counsel&amp;rdquo; contradicted this argument.&amp;nbsp;He testified that he never discussed the order with the Mayor, did not communicate with outside counsel regarding the Plaintiffs&amp;rsquo; motion to preserve evidence, believed that the outside law firm would have been responsible for handling the requirement to preserve, and that he did not know what the City might have done in response to the Order.&amp;nbsp;According to the Court, this testimony &amp;ldquo;disproves&amp;rdquo; the position that the March 5&lt;sup&gt;th&lt;/sup&gt; Order was disseminated by its corporation counsel.&lt;/p&gt;
&lt;p&gt;The City then attempted to prove that the March 5&lt;sup&gt;th&lt;/sup&gt; Order was disseminated because it was able to produce some emails from the Police Chief and two police officers.&amp;nbsp;The Court held that &amp;ldquo;if the City&amp;rsquo;s in-house attorneys stood idly by as emails were deliberately destroyed in contravention of this Court&amp;rsquo;s express order &amp;ndash; to say nothing of the more general duty of all parties to preserve evidence that is relevant to pending litigation &amp;ndash; they should hardly pat themselves on the back for any emails that were overlooked or otherwise survived this effort.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt; at 14.&lt;/p&gt;
&lt;p&gt;Next, the City challenged the appropriateness of the imposition of a permissive adverse inference instruction, essentially claiming the punishment did not fit the crime.&amp;nbsp;The City argued that the sanction was too steep given that the reason for the lost emails was unknown.&amp;nbsp;The Court reasoned that the &amp;ldquo;short answer to this, as Plaintiffs recognize, is that the City, through its attorney Mr. Schapka, filed papers in this case affirmatively stating that &amp;lsquo;upon their resignations during February of 2008, Beatty and Kilpatrick&amp;rsquo;s email accounts and collected emails whether in-coming or out going, were deleted and purged from the electronic storage system.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;Thus, the finding of willfulness and bad faith of the defendants was based on the evidence.&amp;nbsp;The Court reasoned that &amp;ldquo;it is difficult to read the City&amp;rsquo;s present objections as anything other than a continuation of the persistent effort by the City and its in-house counsel to avoid taking responsibility for egregious conduct that has seriously undermined the truth-seeking mission of civil litigation.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt; at 18.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Plaintiffs similarly objected to the adverse inference instruction claiming that a more severe &amp;nbsp;sanction, such as entry of a default judgment or a mandatory adverse inference instruction, were warranted.&amp;nbsp;But the Court agreed with the Magistrate&amp;rsquo;s conclusion that these sanctions would &amp;ldquo;give the Plaintiffs an undeserved evidentiary windfall.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;It further reasoned that, given the lengthy discovery period and the voluminous records produced therein, it would be difficult to conclude that the deleted emails from the 10 month period at issue were likely to provide information not otherwise available. &lt;i&gt;Id.&lt;/i&gt; at 27.&lt;/p&gt;
&lt;p&gt;In connection with the adverse inference instruction, the City further complained that a permissive adverse inference instruction will permit a jury to engage in &amp;ldquo;speculation and conjecture.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt; at 18.&amp;nbsp;While the Court acknowledged that it prefers that factual findings made by a trier of fact be based on the record, it reasoned that the City&amp;rsquo;s destruction of the emails &amp;ldquo;thwarted this goal.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;It reminded the City that the permissive adverse inference instruction allowed the City to argue that the &amp;ldquo;inferences proposed by Plaintiffs are implausible and should be rejected.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In sum, this opinion offers guidance concerning the imposition of the adverse inference instruction as a sanction for the deliberate destruction of electronic discovery and the refusal to properly disseminate a Court Order to preserve evidence.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/BeoORdd6vI8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/BeoORdd6vI8/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/12/articles/opinions/ediscovery-abuses-result-in-permissive-adverse-inference-instruction/</guid>
         <category domain="http://www.ediscoverylawreview.com/tags">Adverse</category><category domain="http://www.ediscoverylawreview.com/tags">Destruction</category><category domain="http://www.ediscoverylawreview.com/tags">Emails</category><category domain="http://www.ediscoverylawreview.com/tags">Inference</category><category domain="http://www.ediscoverylawreview.com/tags">Instruction</category><category domain="http://www.ediscoverylawreview.com/articles">Opinions</category><category domain="http://www.ediscoverylawreview.com/tags">Permissive</category><category domain="http://www.ediscoverylawreview.com/tags">of</category>
         <pubDate>Fri, 23 Dec 2011 07:07:59 -0800</pubDate>
         <dc:creator>Catherine Hamilton</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/12/articles/opinions/ediscovery-abuses-result-in-permissive-adverse-inference-instruction/</feedburner:origLink></item>
            <item>
         <title>Federal Court Gives Metadata Experts a Break</title>
         <description>&lt;p&gt;&lt;img hspace="15" align="right" width="233" height="177" alt="" src="http://www.ediscoverylawreview.com/uploads/image/sh_profile7[1](2).gif" /&gt;New technologies have meant new crimes and new civil liability.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;Although forgeries, forensic analysis, and criminal cover-ups are as familiar as Sherlock Holmes, electronic data has created an entirely new means of falsifying evidence and necessitated specialized investigative methods. &lt;span style="mso-spacerun: yes"&gt;&amp;nbsp;&lt;/span&gt;In response, government agencies have started entirely new investigative divisions and companies involved in their own private investigations or litigation have been forced to hire special experts.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The United States District Court for the Southern District of Florida recently ruled on the reliability of a digital forensic expert&amp;rsquo;s report.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;In &lt;i style="mso-bidi-font-style: normal"&gt;&lt;a href="http://docs.justia.com/cases/federal/district-courts/florida/flsdce/0:2010cv60786/357408/527/"&gt;Coqina Investments v. Rothstein and TD Bank&lt;/a&gt;&lt;/i&gt;, 2011 U.S. Dist. LEXIS 120267 (S.D. Fla. Oct. 18, 2011),&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;the court was presented with allegations of electronic forgery in a civil case.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;As part of the litigation, the court was asked to rule on several traditional Daubert motions seeking to exclude the testimony of various traditional types of experts, rendering opinions on financial damages and accounting practices.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;The plaintiff also sought to exclude a new type of expert, who was offering an opinion in support of defendants&amp;rsquo; claims that certain electronic documents were e-forgeries.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p class="MsoNormal" style="margin: 0in 0in 0pt"&gt;Plaintiff argued that defendants&amp;rsquo; expert&amp;rsquo;s opinion was unreliable and should be excluded because the expert reviewed only&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp;&lt;/span&gt;a sample of plaintiff&amp;rsquo;s data set. After reviewing the expert&amp;rsquo;s methodology and report, the &lt;em&gt;Coquina&lt;/em&gt; Court ruled that defendants&amp;rsquo; expert had &amp;ldquo;employed a sound metadata analysis&amp;rdquo; and, therefore, would be permitted to testify about the emails that he identified as forgeries.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;The fact that the metadata expert did not review every document in the large dataset went to the weight of the evidence and did not undermine the reliability of the expert&amp;rsquo;s conclusion that the emails that he analyzed were e-forgeries.&lt;/p&gt;
&lt;p class="MsoNormal" style="margin: 0in 0in 0pt"&gt;The &lt;em&gt;Coquina&lt;/em&gt; Court&amp;rsquo;s commonsense approach to this complex issue sets an important precedent in metadata analysis.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;Electronic discovery and document productions often easily encompass hundreds of thousands, if not millions, of documents.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;Metadata analysis is a very complex area of science, requiring experts to interpret facts for fact-finders.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;Requiring a metadata expert to analyze every document is not only unnecessary, it would be paralyzing.&lt;span style="mso-spacerun: yes"&gt;&amp;nbsp; &lt;/span&gt;Allowing metadata experts to testify based on their analysis of a sample of documents strikes an appropriate balance in allowing the expert to assist the trier of fact while also allowing the opposing party to question the weight to be given to that expert&amp;rsquo;s testimony.&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/8bPWF0bDH80" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/8bPWF0bDH80/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/12/articles/opinions/federal-court-gives-metadata-experts-a-break/</guid>
         <category domain="http://www.ediscoverylawreview.com/articles">Opinions</category>
         <pubDate>Tue, 06 Dec 2011 13:27:10 -0800</pubDate>
         <dc:creator>Lisa Myers</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/12/articles/opinions/federal-court-gives-metadata-experts-a-break/</feedburner:origLink></item>
            <item>
         <title>Post at Your Own Risk: Pennsylvania Court Permits Discovery of Information on Personal Facebook Profile</title>
         <description>&lt;p&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;o:OfficeDocumentSettings&gt;
&lt;o:AllowPNG /&gt;
&lt;/o:OfficeDocumentSettings&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;w:WordDocument&gt;
&lt;w:View&gt;Normal&lt;/w:View&gt;
&lt;w:Zoom&gt;0&lt;/w:Zoom&gt;
&lt;w:TrackMoves /&gt;
&lt;w:TrackFormatting /&gt;
&lt;w:PunctuationKerning /&gt;
&lt;w:ValidateAgainstSchemas /&gt;
&lt;w:SaveIfXMLInvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;
&lt;w:IgnoreMixedContent&gt;false&lt;/w:IgnoreMixedContent&gt;
&lt;w:AlwaysShowPlaceholderText&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;
&lt;w:DoNotPromoteQF /&gt;
&lt;w:LidThemeOther&gt;EN-US&lt;/w:LidThemeOther&gt;
&lt;w:LidThemeAsian&gt;X-NONE&lt;/w:LidThemeAsian&gt;
&lt;w:LidThemeComplexScript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;
&lt;w:Compatibility&gt;
&lt;w:BreakWrappedTables /&gt;
&lt;w:SnapToGridInCell /&gt;
&lt;w:WrapTextWithPunct /&gt;
&lt;w:UseAsianBreakRules /&gt;
&lt;w:DontGrowAutofit /&gt;
&lt;w:SplitPgBreakAndParaMark /&gt;
&lt;w:EnableOpenTypeKerning /&gt;
&lt;w:DontFlipMirrorIndents /&gt;
&lt;w:OverrideTableStyleHps /&gt;
&lt;/w:Compatibility&gt;
&lt;m:mathPr&gt;
&lt;m:mathFont m:val="Cambria Math" /&gt;
&lt;m:brkBin m:val="before" /&gt;
&lt;m:brkBinSub m:val="&amp;#45;-" /&gt;
&lt;m:smallFrac m:val="off" /&gt;
&lt;m:dispDef /&gt;
&lt;m:lMargin m:val="0" /&gt;
&lt;m:rMargin m:val="0" /&gt;
&lt;m:defJc m:val="centerGroup" /&gt;
&lt;m:wrapIndent m:val="1440" /&gt;
&lt;m:intLim m:val="subSup" /&gt;
&lt;m:naryLim m:val="undOvr" /&gt;
&lt;/m:mathPr&gt;&lt;/w:WordDocument&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
DefSemiHidden="true" DefQFormat="false" DefPriority="99"
LatentStyleCount="267"&gt;
&lt;w:LsdException Locked="false" Priority="0" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Normal" /&gt;
&lt;w:LsdException Locked="false" Priority="9" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="heading 1" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 1" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 2" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 3" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 4" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 5" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 6" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 7" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 8" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 9" /&gt;
&lt;w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /&gt;
&lt;w:LsdException Locked="false" Priority="10" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Title" /&gt;
&lt;w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /&gt;
&lt;w:LsdException Locked="false" Priority="0" Name="Body Text" /&gt;
&lt;w:LsdException Locked="false" Priority="11" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /&gt;
&lt;w:LsdException Locked="false" Priority="22" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Strong" /&gt;
&lt;w:LsdException Locked="false" Priority="20" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /&gt;
&lt;w:LsdException Locked="false" Priority="59" SemiHidden="false"
UnhideWhenUsed="false" Name="Table Grid" /&gt;
&lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /&gt;
&lt;w:LsdException Locked="false" Priority="1" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /&gt;
&lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /&gt;
&lt;w:LsdException Locked="false" Priority="34" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /&gt;
&lt;w:LsdException Locked="false" Priority="29" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Quote" /&gt;
&lt;w:LsdException Locked="false" Priority="30" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="19" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /&gt;
&lt;w:LsdException Locked="false" Priority="21" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /&gt;
&lt;w:LsdException Locked="false" Priority="31" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /&gt;
&lt;w:LsdException Locked="false" Priority="32" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /&gt;
&lt;w:LsdException Locked="false" Priority="33" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Book Title" /&gt;
&lt;w:LsdException Locked="false" Priority="37" Name="Bibliography" /&gt;
&lt;w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /&gt;
&lt;/w:LatentStyles&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
&lt;/style&gt;
&lt;![endif]--&gt;&lt;img align="left" width="150" vspace="10" hspace="10" height="150" alt="" src="http://www.ediscoverylawreview.com/uploads/image/FB pic(1).png" /&gt;A Pennsylvania court recently decided that information posted by a party on their personal Facebook page is discoverable.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;i style="mso-bidi-font-style:normal"&gt;Largent v. Reed&lt;/i&gt;, Case No. 2009-1823 (C.P. Franklin Nov. 8, 2011) arose out of a chain-reaction automobile accident in which the plaintiffs, who were riding a motorcycle, were hit by a minivan that was hit by the defendant.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Plaintiffs claimed serious and permanent physical and mental injuries, pain, and suffering as a result of the accident.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;During the deposition of one of the plaintiffs, defense counsel discovered that the&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;plaintiff/deponent had a Facebook profile that she regularly accessed.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;The defendant then accessed Plaintiff&amp;rsquo;s public profile and saw posts that contradicted her claims of serious injury.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Specifically, Defendant claimed that Plaintiff posted several photographs that showed her enjoying life with her family and a status update about going to the gym.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Defense counsel requested access to Plaintiff&amp;rsquo;s Facebook page, but Plaintiff refused to voluntarily disclose any information about her profile.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;In response, Defendant moved to compel Plaintiff to disclose her Facebook username and password.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Plaintiff&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;opposed the Motion, arguing that the information sought was irrelevant, did not meet the threshold under Pennsylvania Rule of Civil Procedure 4003.1, and that access to her information would cause unreasonable embarrassment and annoyance.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Court of Common Pleas Judge Richard J. Walsh began his opinion with a lengthy description of Facebook as the site that &amp;ldquo;helps you connect and share with the people in your life.&amp;rdquo;&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Judge Walsh pointed out that the site has more than 800 million active users, 50% of whom are active on the site daily.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Although he acknowledged that Facebook has privacy settings, Judge Walsh emphasized that users must take &amp;ldquo;affirmative steps&amp;rdquo; in order to prevent their information from being shared with the public.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The Court then turned to the issue at hand - whether and to what extent such &amp;ldquo;private&amp;rdquo; information is discoverable in a civil case.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;With respect to relevancy, the Court pointed out that Pennsylvania has a &amp;ldquo;slight&amp;rdquo; relevancy threshold pursuant to Pennsylvania Rule of Civil Procedure 4003.1.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Under this standard, the photographs depicting Plaintiff with her family and status updates about exercising at the gym are &amp;ldquo;clearly relevant&amp;rdquo; because they might prove that Plaintiff&amp;rsquo;s injuries do not exist or that they are exaggerated.&lt;/p&gt;
&lt;p&gt;The Court found that Plaintiff&amp;rsquo;s Facebook information is not privileged.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Information on Facebook is shared with third parties and, thus, there is no reasonable expectation of privacy in such information.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;In addition, Pennsylvania law does not recognize a confidential social networking privilege.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;As Judge Walsh explained, &amp;ldquo;[o]nly the uninitiated or foolish could believe that Facebook is an online lockbox of secrets.&amp;rdquo;&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Further, Plaintiff&amp;rsquo;s information was not protected by the Stored Communications Act, which prevents the government from compelling Internet Service Providers (ISP) from disclosing information about their users because the information was sought directly from Plaintiff, who is not an ISP.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Finally, the Court concluded that Defendant&amp;rsquo;s request was not unreasonably embarrassing or annoying and disagreed with the claim that Defendant&amp;rsquo;s request is akin to asking Plaintiff to produce all of her personal mail.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Since Plaintiff&amp;rsquo;s postings were never truly private, there could not be any unreasonable embarrassment in producing the postings in litigation.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;The Court also determined that the request would not cause unreasonable annoyance, because Defendant would bear the entire cost of investigating Plaintiff&amp;rsquo;s Facebook information.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;As Judge Walsh points out, social networking is a recent phenomenon and these issues are just beginning to infiltrate the courts.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Although relatively few courts have spoken on this issue, the standard is becoming clear: Post at your own risk.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/o2hPEKbQQlo" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/o2hPEKbQQlo/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/12/articles/opinions/post-at-your-own-risk-pennsylvania-court-permits-discovery-of-information-on-personal-facebook-profile/</guid>
         <category domain="http://www.ediscoverylawreview.com/tags">Facebook</category><category domain="http://www.ediscoverylawreview.com/articles">Opinions</category><category domain="http://www.ediscoverylawreview.com/tags">discovery</category><category domain="http://www.ediscoverylawreview.com/tags">discovery of social media in lawsuits</category><category domain="http://www.ediscoverylawreview.com/tags">discovery of social networking sites</category>
         <pubDate>Mon, 05 Dec 2011 11:46:48 -0800</pubDate>
         <dc:creator>Calli Varner</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/12/articles/opinions/post-at-your-own-risk-pennsylvania-court-permits-discovery-of-information-on-personal-facebook-profile/</feedburner:origLink></item>
            <item>
         <title>ESI in the Criminal Context: A Call for Clarification</title>
         <description>&lt;p&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;o:OfficeDocumentSettings&gt;
&lt;o:AllowPNG /&gt;
&lt;/o:OfficeDocumentSettings&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;w:WordDocument&gt;
&lt;w:View&gt;Normal&lt;/w:View&gt;
&lt;w:Zoom&gt;0&lt;/w:Zoom&gt;
&lt;w:TrackMoves /&gt;
&lt;w:TrackFormatting /&gt;
&lt;w:PunctuationKerning /&gt;
&lt;w:ValidateAgainstSchemas /&gt;
&lt;w:SaveIfXMLInvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;
&lt;w:IgnoreMixedContent&gt;false&lt;/w:IgnoreMixedContent&gt;
&lt;w:AlwaysShowPlaceholderText&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;
&lt;w:DoNotPromoteQF /&gt;
&lt;w:LidThemeOther&gt;EN-US&lt;/w:LidThemeOther&gt;
&lt;w:LidThemeAsian&gt;X-NONE&lt;/w:LidThemeAsian&gt;
&lt;w:LidThemeComplexScript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;
&lt;w:Compatibility&gt;
&lt;w:BreakWrappedTables /&gt;
&lt;w:SnapToGridInCell /&gt;
&lt;w:WrapTextWithPunct /&gt;
&lt;w:UseAsianBreakRules /&gt;
&lt;w:DontGrowAutofit /&gt;
&lt;w:SplitPgBreakAndParaMark /&gt;
&lt;w:EnableOpenTypeKerning /&gt;
&lt;w:DontFlipMirrorIndents /&gt;
&lt;w:OverrideTableStyleHps /&gt;
&lt;/w:Compatibility&gt;
&lt;m:mathPr&gt;
&lt;m:mathFont m:val="Cambria Math" /&gt;
&lt;m:brkBin m:val="before" /&gt;
&lt;m:brkBinSub m:val="&amp;#45;-" /&gt;
&lt;m:smallFrac m:val="off" /&gt;
&lt;m:dispDef /&gt;
&lt;m:lMargin m:val="0" /&gt;
&lt;m:rMargin m:val="0" /&gt;
&lt;m:defJc m:val="centerGroup" /&gt;
&lt;m:wrapIndent m:val="1440" /&gt;
&lt;m:intLim m:val="subSup" /&gt;
&lt;m:naryLim m:val="undOvr" /&gt;
&lt;/m:mathPr&gt;&lt;/w:WordDocument&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
DefSemiHidden="true" DefQFormat="false" DefPriority="99"
LatentStyleCount="267"&gt;
&lt;w:LsdException Locked="false" Priority="0" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Normal" /&gt;
&lt;w:LsdException Locked="false" Priority="9" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="heading 1" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 1" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 2" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 3" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 4" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 5" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 6" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 7" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 8" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 9" /&gt;
&lt;w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /&gt;
&lt;w:LsdException Locked="false" Priority="10" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Title" /&gt;
&lt;w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /&gt;
&lt;w:LsdException Locked="false" Priority="0" Name="Body Text" /&gt;
&lt;w:LsdException Locked="false" Priority="11" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /&gt;
&lt;w:LsdException Locked="false" Priority="22" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Strong" /&gt;
&lt;w:LsdException Locked="false" Priority="20" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /&gt;
&lt;w:LsdException Locked="false" Priority="59" SemiHidden="false"
UnhideWhenUsed="false" Name="Table Grid" /&gt;
&lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /&gt;
&lt;w:LsdException Locked="false" Priority="1" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /&gt;
&lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /&gt;
&lt;w:LsdException Locked="false" Priority="34" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /&gt;
&lt;w:LsdException Locked="false" Priority="29" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Quote" /&gt;
&lt;w:LsdException Locked="false" Priority="30" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="19" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /&gt;
&lt;w:LsdException Locked="false" Priority="21" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /&gt;
&lt;w:LsdException Locked="false" Priority="31" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /&gt;
&lt;w:LsdException Locked="false" Priority="32" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /&gt;
&lt;w:LsdException Locked="false" Priority="33" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Book Title" /&gt;
&lt;w:LsdException Locked="false" Priority="37" Name="Bibliography" /&gt;
&lt;w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /&gt;
&lt;/w:LatentStyles&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
&lt;/style&gt;
&lt;![endif]--&gt;&lt;img align="left" width="250" vspace="5" hspace="5" height="250" alt="" src="http://www.ediscoverylawreview.com/uploads/image/prisoners-may-lose-their-cell-phone-privileges-if-congress-has-its-way_1(3).jpg" /&gt;Although the Federal Rules of Civil Procedure set the stage for electronic discovery in civil cases, there is no such express regime in the criminal context.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The absence of such a standard became evident in a recent case in the Western District of New York.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;In &lt;i style="mso-bidi-font-style:normal"&gt;United States v. Briggs&lt;/i&gt;, 2011 WL 4017886 (W.D.N.Y. Sept. 8, 2011), defendants were charged with several counts related to the distribution of cocaine.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;The criminal investigation leading to these charges involved court-authorized interceptions of cellular telephone communications indicating that the defendants were allegedly engaged in drug trafficking.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;In its voluntary discovery, the Government furnished defense counsel with disks containing thousands of pages of documents relating to these communications using the IPRO program routinely used by the U.S. Attorney&amp;rsquo;s Office in cases involving multiple defendants.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Defendants claimed this reported data had problems with omissions and inaccuracies resulting from the collection and management system used. The defendants also objected to the Government&amp;rsquo;s failure to provide the data in the &amp;ldquo;most useful form that is readily available&amp;rdquo; and claimed the &amp;ldquo;.tiff&amp;rdquo; files received could not be sorted or searched.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;The appropriate format, according to the defendants, was either the &amp;ldquo;.pdf&amp;rdquo; or native format.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;The Government, in response, refused to provide the files in these formats arguing that the cost of reproduction was prohibitive, that it had already produced the particular data requested by defendants, and that it should not bear the burden of reproduction merely because it would be more helpful or useful to the defendants.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Examining this issue, the court began by pointing out the absence of a standard in criminal cases for the production of ESI. &lt;span style="mso-spacerun:yes"&gt;&amp;nbsp;&lt;/span&gt;While Rule 16(d)(1) of the Federal Rules of Criminal Procedure, the general authority ordering the manner of production in criminal cases, provides that, &amp;ldquo;[a]t any time the court may, for good cause, deny, restrict, or defer discovery or inspection, or grant other appropriate relief,&amp;rdquo; &lt;span style="mso-spacerun:yes"&gt;&amp;nbsp;&lt;/span&gt;it does not specify the manner in which such production should be made.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;The court, therefore, turned to two other jurisdictions addressing criminal prosecutions involving extensive document production.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;In &lt;i style="mso-bidi-font-style:
normal"&gt;United States v. O&amp;rsquo;Keefe&lt;/i&gt;, 537 F. Supp. 2d 14 (D.D.C. 2008), the United States District Court of the District of Columbia, conceded that there was no &lt;span style="mso-spacerun:yes"&gt;&amp;nbsp;&lt;/span&gt;criminal equivalent to, and, thus, applied, Federal Rule of Civil Procedure 34.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;In &lt;i style="mso-bidi-font-style:normal"&gt;United States v. Warshak&lt;/i&gt;, 631 F.3d 266 (6th Cir. 2010), the Sixth Circuit refused to require the Government to reproduce electronic materials in the format requested by the defendant because the defendants had ready access to the information and documents as they were kept in the usual course of business.&lt;/p&gt;
&lt;p&gt;Applying these rules, the court determined that the Government was the party &amp;ldquo;better able to bear the burden of organizing these records for over twenty defendants in a manner useful to all.&amp;rdquo;&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;The court mandated that the Government must reproduce its disclosure in a searchable format (PDF), or in the native format.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;The court based its decision on the rationale that the Government is in the better position to organize the mass of information in a manner that is searchable by the defense because: (1) the Government already compiled this electronic information from its various native forms into a common electronic database and; (2) rather than have each defendant compile the data involving that party or repeat the expense of reproducing the entire Government production, the Government should bear this burden.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;In making this decision, the court made it clear that it was not adopting Rule 34 of the Federal Rules of Civil Procedure in all criminal cases, as in &lt;i style="mso-bidi-font-style:
normal"&gt;O&amp;rsquo;Keefe&lt;/i&gt;, rather it was applying it in only this case.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;i style=""&gt;Briggs&lt;/i&gt; is a clear example of the need for a more uniform regime for ESI in criminal cases.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;According to the court, the Justice Department appears to have at least one working group considering the &amp;ldquo;best practices&amp;rdquo; for ESI in criminal cases.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Until then, each court faced with a motion to compel criminal discovery with ESI data will have to devise its own scheme for ESI discovery based on the limited rules governing the criminal context at this time.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Defendants, then, are best advised to be prepared and willing to seek the court&amp;rsquo;s involvement early on to ensure that the production of ESI is reasonable, proportionate, and manageable so as not to cripple their efforts in defending against criminal liability.&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/HdiHXwLBSP0" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/HdiHXwLBSP0/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/11/articles/esi-in-the-criminal-context-a-call-for-clarification/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/tags">criminal</category><category domain="http://www.ediscoverylawreview.com/tags">disclosure</category><category domain="http://www.ediscoverylawreview.com/tags">discovery</category><category domain="http://www.ediscoverylawreview.com/tags">electronic</category><category domain="http://www.ediscoverylawreview.com/tags">electronic communication</category>
         <pubDate>Wed, 16 Nov 2011 06:46:15 -0800</pubDate>
         <dc:creator>Calli Varner</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/11/articles/esi-in-the-criminal-context-a-call-for-clarification/</feedburner:origLink></item>
            <item>
         <title>Document Preservation: Spoliation and the "Ultimate Sanction"</title>
         <description>&lt;p style="margin: 12pt 0in 0pt"&gt;The proper preservation of electronic data for discovery has become an increasing source of contention between parties.&amp;nbsp;Two recent cases illustrate the importance of mindfully preserving elect&lt;img alt="" align="left" width="196" height="178" src="http://www.ediscoverylawreview.com/uploads/image/thermometer.jpg" /&gt;ronic data during discovery.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;In &lt;i&gt;Gentex Corp. v. Sutter&lt;/i&gt;, No. 3:07-CV-1269, 2011 U.S. Dist. LEXIS 122831 (M.D. Pa. Oct. 24, 2011), the district court granted default judgment to the plaintiffs in a spoliation action.&amp;nbsp;Gentex Corporation sued two of its former employees, Brad Sutter and Patrick Walko, for violating non-disclosure agreements.&amp;nbsp;Gentex claimed that Sutter and Walko copied proprietary files when they left the company and shared them with a rival company, Armor.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;In response to the suit, Armor implemented a litigation hold and instructed employees to preserve &amp;ldquo;all paper documents and electronically stored information concerning the Company&amp;rsquo;s relationship with Brad Sutter and his work while at the Company.&amp;rdquo;&amp;nbsp;Armor also obtained a consulting firm to help preserve documents relevant to the litigation.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;Sutter, however, began destroying evidence despite knowledge of the litigation hold.&amp;nbsp;Sutter scrubbed his computer, explaining that he did so &amp;ldquo;because he was scared because Gentex had sued him.&amp;rdquo;&amp;nbsp;Sutter destroyed all CD-ROMs containing Gentex information that he possessed and purposely destroyed a thumb drive after his deposition.&amp;nbsp;Sutter also deleted numerous email messages when he was printing them for production to Gentex.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;Similarly, Walko knowingly deleted documents relating to Gentex files on his computer.&amp;nbsp;Walko claimed that various supervisors, including Sutter, instructed him, &amp;ldquo;Do what you have to do to clean up.&amp;nbsp;If you need to clean up, clean up.&amp;rdquo;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;Gentex&amp;rsquo;s expert concluded that the deletions were &amp;ldquo;intentional and coordinated and designed to circumvent the duty to preserve documents.&amp;rdquo;&amp;nbsp;The district court agreed and found that Gentex had presented sufficient evidence to show that Sutter and Walko engaged in willful spoliation.&amp;nbsp;The court ultimately determined that granting default judgment to Gentex was the &amp;ldquo;least onerous&amp;rdquo; sanction corresponding to the willfulness of the spoliation, given Sutter and Walko&amp;rsquo;s &amp;ldquo;unabashedly intentional destruction of relevant, irretrievable evidence.&amp;rdquo;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;By contrast, another court facing similar facts refused to levy the ultimate sanction.&amp;nbsp;In &lt;i&gt;Cedar Rapids Lodge &amp;amp; Suites, LLC v. JFS Dev., Inc.&lt;/i&gt;, No. C09-0175, 2011 U.S. Dist. LEXIS 110671 (N.D. Iowa Sept. 27, 2011), the court determined that &amp;ldquo;a stronger showing of bad faith [was] required&amp;rdquo; before it would grant default judgment to the plaintiffs.&amp;nbsp;In that case, plaintiff investors sued the developers of a proposed hotel for fraudulent inducement.&amp;nbsp;Following a protracted discovery dispute, plaintiffs sought default judgment against one of the defendants for failure to comply with discovery requests and for intentional destruction of evidence.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;The defendant previously produced seven computers, ten hard drives, and 23 CDs for inspection and copying.&amp;nbsp;Although the plaintiffs&amp;rsquo; expert extracted over 34,000 relevant documents from these sources, the expert concluded that external drives that had been connected to the laptop were missing.&amp;nbsp;Additionally, the expert contended that a large number of relevant documents, folders, files, and emails had been targeted for strategic deletion.&amp;nbsp;The expert, however, conceded that several innocent explanations existed for the deletions and missing drives.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;Citing an Eighth Circuit decision, the district court determined that there was no proof that the defendant intentionally engaged in spoliation.&amp;nbsp;As an initial matter, the court seemed impressed by the sheer volume of documents that plaintiffs had already recovered from the defendants.&amp;nbsp;The defendant had initially produced 875 documents followed by an additional 2,700 pages, not to mention the 34,000 documents extracted from various hard drives and computers.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;Additionally, the court found that plaintiffs had not met the relevant legal standard.&amp;nbsp;To warrant any sanction, much less a default judgment, the court had to find: 1) intentional destruction indicative of a desire to suppress the truth; and 2) actual prejudice to the other party resulting from the spoliation.&amp;nbsp;Here, the court deemed the defendant to be merely &amp;ldquo;unsophisticated in the requirements of litigation and preservation of documents&amp;rdquo; rather than willfully destructive.&amp;nbsp;Further, the plaintiffs suffered no prejudice, as &amp;ldquo;[i]t would seem that Plaintiffs have plenty of information upon which to pursue their claims.&amp;rdquo;&amp;nbsp;In denying the motion for sanctions, the court simply stated, &amp;ldquo;I believe a stronger showing of bad faith is required.&amp;rdquo;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt"&gt;While a default judgment represents the ultimate sanction in spoliation cases, destruction of electronic evidence can result in sanctions running the gamut from claim dismissal and suppression of evidence to an adverse inference and attorneys&amp;rsquo; fees and costs.&amp;nbsp;As the district court judge in &lt;i&gt;Gentex &lt;/i&gt;observed, &amp;ldquo;I am especially conscious of the deterrence value of harsh sanctions in cases like this where the crucial evidence exists in electronic form, and a party may destroy its opponent&amp;rsquo;s case with the mere click of a button.&amp;rdquo;&amp;nbsp;These two cases teach us to beware the fine line that distinguishes behavior worthy of a default judgment and behavior that is merely vexatious.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/UgnP68w-mJc" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/UgnP68w-mJc/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/11/articles/document-preservation-spoliation-and-the-ultimate-sanction/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/articles">Sanctions</category><category domain="http://www.ediscoverylawreview.com/tags">default</category><category domain="http://www.ediscoverylawreview.com/tags">electronic</category><category domain="http://www.ediscoverylawreview.com/tags">evidence</category><category domain="http://www.ediscoverylawreview.com/tags">hold</category><category domain="http://www.ediscoverylawreview.com/tags">judgment</category><category domain="http://www.ediscoverylawreview.com/tags">litigation</category><category domain="http://www.ediscoverylawreview.com/tags">preservation</category><category domain="http://www.ediscoverylawreview.com/tags">spoliation</category>
         <pubDate>Mon, 14 Nov 2011 10:50:16 -0800</pubDate>
         <dc:creator>Diana Lin</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/11/articles/document-preservation-spoliation-and-the-ultimate-sanction/</feedburner:origLink></item>
            <item>
         <title>Weighing Burdens and Benefits in Hard Drive Preservation Dispute</title>
         <description>&lt;p&gt;Although deleted data can be recovered &amp;ndash; perhaps at significant cost &amp;ndash; destroyed data is likely gone forever.&amp;nbsp;Perhaps it is for this reason that a recent federal court was reluctant to apply a strict proportionality test to a preservation dispute.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt;"&gt;In &lt;i&gt;Pippins v. KPMG LLP&lt;/i&gt;, 2011 U.S. Dist. LEXIS 116427 (S.D.N.Y. Oct 7, 2011), the court denied the defendant&amp;rsquo;s request for a protective order to limit its &lt;img hspace="5" height="167" width="250" vspace="5" align="left" src="http://www.ediscoverylawreview.com/uploads/image/shutterstock_1012421.jpg" alt="Hard Drives" /&gt;preservation obligations.&amp;nbsp;A group of plaintiff sued their former employer alleging that the employer&amp;nbsp;deprived them of overtime pay by purposefully misclassifying them as exempt employees under federal and state employment laws.&amp;nbsp;These plaintiffs moved for class certification, causing the court to stay discovery until it ruled on the certification question.&amp;nbsp;This stay necessitated that the employer indefinitely preserve the hard drives of over 7,500 potential class members.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt;"&gt;After racking up over $1,500,000 in preservation costs, the employer sought a protective order, arguing that the burden of preserving the hard drives was disproportionate to the benefit they might provide and that there were less burdensome methods of preserving any relevant information on the hard drives.&amp;nbsp;While cautioning against the application of a proportionality test in preservation disputes, the court assessed three factors in evaluating the employer&amp;rsquo;s duty to preserve the drives.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt;"&gt;First, the court looked to see if the material was relevant.&amp;nbsp;The former employees believed that the drives contained information relevant to the dispute, such as job responsibilities and hours worked.&amp;nbsp;The employer, on the other hand, argued that similar information was contained in sources such as human resources files and time records.&amp;nbsp;It was not entirely clear exactly what information was on the drives, however, because the employer had not allowed anyone to inspect them.&amp;nbsp;This uncertainty, along with the extremely broad concept of relevance, led the court to conclude that the employer could not establish that the material was not relevant.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt;"&gt;Second, the court looked to see if the material on the hard drives was created by or for &amp;ldquo;key players,&amp;rdquo; namely, people likely to have relevant information.&amp;nbsp;The employer argued that only the named plaintiffs were key players because they purported to represent the entire class.&amp;nbsp;The court disagreed.&amp;nbsp;It reasoned that not only was every former employee a potential plaintiff in the class action, but also that the employer was on notice that the hard drives could contain material relevant to future litigation even if the class was not certified and, thus, had a duty to preserve the hard drives in either situation.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt;"&gt;Finally, the court considered whether the continuing preservation merely maintained information that was available from other, less burdensome, sources.&amp;nbsp;The employer argued that the information was duplicative because it also was contained in a variety of other sources, and because the former employees could testify to their job responsibilities.&amp;nbsp;Nevertheless, the court found that the unofficial information on the hard drives could supplement the official information in the employer&amp;rsquo;s records.&amp;nbsp;As a result, the information on the hard drives was deemed to be not duplicative.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt;"&gt;On balance, the court ruled that the employer had to continue to preserve the hard drives.&amp;nbsp;In the end, there were too many unknowns, such as, the ultimate length and cost of preservation, the relevance of the information on the hard drives, and the outcome of the motion for class certification, for the court to weigh the benefits and burdens in a satisfactory manner.&amp;nbsp;The finality of the destruction that would have accompanied the protective order likely led the court to err on the side of preservation.&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt;"&gt;Note that the duty to preserve potentially relevant information is much broader, and arises much earlier, than the duty to produce information that is relevant and responsive to discovery requests in pending litigation.&amp;nbsp;The &lt;i&gt;Pippins&lt;/i&gt; decision speaks only to the preservation phase of electronic discovery and does not address the scenario where additional potentially relevant information continues to be created and stored on various hard drives after initial preservation efforts are complete (or, stated another way, the issue of the ongoing creation and preservation of electronic data).&amp;nbsp;Businesses may be able to avoid these costs and potential pitfalls by encouraging, if not requiring, employees to save data, not on their individual hard drives, but in a central location that is backed-up on a daily basis.&amp;nbsp;In an ideal scenario, any potentially relevant information would be stored on a back-up and shared server and, at most, duplicate that which is contained on individual hard drives.&amp;nbsp;This may eliminate, or provide strong arguments in favor of eliminating, the need to, and cost of, preserving multiple hard drives multiple times.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/51AzhSSFcoM" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/51AzhSSFcoM/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/10/articles/weighing-burdens-and-benefits-in-hard-drive-preservation-dispute/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/tags">data</category><category domain="http://www.ediscoverylawreview.com/tags">electronically stored information</category><category domain="http://www.ediscoverylawreview.com/tags">preservation</category>
         <pubDate>Mon, 31 Oct 2011 12:26:00 -0800</pubDate>
         <dc:creator>Brian Kint</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/10/articles/weighing-burdens-and-benefits-in-hard-drive-preservation-dispute/</feedburner:origLink></item>
            <item>
         <title>When Are Text Messages Admissible?  The Pennsylvania Superior Court Explains.</title>
         <description>&lt;p&gt;&amp;nbsp;In today&amp;rsquo;s electronic age where text messages, instant messages and e-mails have, to a large degree, supplanted traditional written correspondence, courts are increasingly called upon to apply longstanding evidentiary rules to society&amp;rsquo;s newer methods of communication.&amp;nbsp;A recent opinion, however, from the Pennsylvania Superior Court, &lt;a href="http://www.superior.court.state.pa.us/opinions/S43009_11.pdf"&gt;&lt;i&gt;Commonwealth v. Koch&lt;/i&gt;&lt;/a&gt;, No.1669-MDA-2010, 2011 Pa. Super. LEXIS 2716 (Sept. 16, 2011), suggests that the more things change, the more they stay the same.&lt;/p&gt;
&lt;p&gt;&lt;img hspace="5" height="182" align="left" width="250" src="http://www.ediscoverylawreview.com/uploads/image/text message pic.JPG" alt="" /&gt;According to &lt;i&gt;Koch&lt;/i&gt;, a party seeking to admit a text message as evidence at trial faces authentication requirements similar to those of a party seeking to admit a handwritten letter.&amp;nbsp;A letter, for example, may bear Mr. Smith&amp;rsquo;s signature, or be printed on Mr. Smith&amp;rsquo;s stationery, but that signature may be forged, or the letterhead copied.&amp;nbsp;Typically, some further authentication is needed to show that the letter is what it purports to be &amp;ndash; i.e., a statement made by Mr. Smith.&amp;nbsp;Under &lt;i&gt;Koch&lt;/i&gt;, the same principle applies to text messages: the mere fact that a text message came from Mr. Smith&amp;rsquo;s cell phone number is an insufficient basis to admit that text message as a statement made by Mr. Smith.&amp;nbsp;Additional evidence of the sender&amp;rsquo;s identity is needed.&lt;/p&gt;
&lt;p&gt;In &lt;i&gt;Koch&lt;/i&gt;, the trial court admitted testimony and a transcript of thirteen drug-related text messages obtained from a cell phone that the defendant admitted belonged to her.&amp;nbsp;The defendant objected, claiming there was no evidence substantiating that she was the author of the text messages, nor was there evidence that the drug-related texts were directed at her, because Commonwealth witnesses testified that another person was using the defendant&amp;rsquo;s cell phone at least some of the time. At trial, a police detective further conceded that: the author of the drug-related text messages could not be ascertained; that some of the messages referred to the defendant in the third person and, thus, were not written by the defendant; and that some text messages had been deleted.&amp;nbsp;The defendant was ultimately convicted on two drug-possession charges.&lt;/p&gt;
&lt;p&gt;The Pennsylvania Superior Court reversed, holding that the trial court erred in admitting the text messages because the messages were improperly authenticated.&amp;nbsp;In determining the standard for the authentication of text messages, the Superior Court looked to several recent appellate opinions from around the country, as well as its own opinion in &lt;a href="http://www.superior.court.state.pa.us/Opinions/S10004_05.pdf"&gt;&lt;i&gt;In the Interest of F.P., a Minor&lt;/i&gt;&lt;/a&gt;, 878 A.2d 91 (2005), a case that addressed authentication of instant messages.&lt;span&gt;&amp;nbsp;&amp;nbsp; From these cases, the court concluded that &amp;ldquo;&lt;/span&gt;e-mails and text messages are documents and subject to the same requirements for authenticity as non-electronic documents generally.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Establishing authorship of an e-mail or text message, the court observed, can be difficult because e-mail accounts and cell phones are not always exclusively used by the person to whom the e-mail account or cell phone belongs.&amp;nbsp;In the light of this, the court held that &amp;ldquo;authentication of electronic communications, like documents, requires more than mere confirmation that the number or address belonged to a particular person. Circumstantial evidence, which tends to corroborate the identity of the sender, is required.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Turning to the facts of the case, the court found that evidence showing that the defendant had written the text messages found on her phone was &amp;ldquo;[g]laringly absent.&amp;rdquo;&amp;nbsp;The court noted that there was no confirming testimony from the senders or recipients of the disputed messages and no contextual clues within the messages themselves that revealed the identity of the sender.&amp;nbsp;The court also rejected the idea that the defendant&amp;rsquo;s physical proximity to the cell phone when it was seized was probative of the defendant&amp;rsquo;s authorship of the text messages made days or weeks earlier.&amp;nbsp;Under these circumstances, the court concluded that the admission of the text messages was an abuse of the trial court&amp;rsquo;s discretion.&lt;span&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;With &lt;i&gt;Koch&lt;/i&gt;, the Pennsylvania Superior Court has made clear that an individual&amp;rsquo;s mere association with an e-mail account or cell phone number is an insufficient evidentiary basis for admission of a text message, e-mail, or instant message.&amp;nbsp;A party seeking to introduce electronic communications at trial should be prepared to produce circumstantial evidence that corroborates the identity of the supposed sender.&amp;nbsp;&lt;i&gt;Koch &lt;/i&gt;provides some guidance as to what that circumstantial evidence might be: testimony from the sender or recipients, or contextual clues within the message itself. Merely identifying the phone or account from which the message came, however, is not enough.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;
&lt;meta content="text/html; charset=utf-8" http-equiv="Content-Type"&gt;
&lt;meta content="Word.Document" name="ProgId"&gt;
&lt;meta content="Microsoft Word 11" name="Generator"&gt;
&lt;meta content="Microsoft Word 11" name="Originator"&gt;
&lt;link href="file:///C:%5CDOCUME%7E1%5Cmzabel%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml" rel="File-List" /&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;o:OfficeDocumentSettings&gt;
&lt;o:TargetScreenSize&gt;1024x768&lt;/o:TargetScreenSize&gt;
&lt;/o:OfficeDocumentSettings&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;w:WordDocument&gt;
&lt;w:View&gt;Normal&lt;/w:View&gt;
&lt;w:Zoom&gt;0&lt;/w:Zoom&gt;
&lt;w:PunctuationKerning /&gt;
&lt;w:ValidateAgainstSchemas /&gt;
&lt;w:SaveIfXMLInvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;
&lt;w:IgnoreMixedContent&gt;false&lt;/w:IgnoreMixedContent&gt;
&lt;w:AlwaysShowPlaceholderText&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;
&lt;w:Compatibility&gt;
&lt;w:BreakWrappedTables /&gt;
&lt;w:SnapToGridInCell /&gt;
&lt;w:WrapTextWithPunct /&gt;
&lt;w:UseAsianBreakRules /&gt;
&lt;w:DontGrowAutofit /&gt;
&lt;/w:Compatibility&gt;
&lt;w:DoNotOptimizeForBrowser /&gt;
&lt;/w:WordDocument&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;w:LatentStyles DefLockedState="false" LatentStyleCount="156"&gt;
&lt;/w:LatentStyles&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;style type="text/css"&gt;
&lt;!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	tab-stops:center 3.25in right 6.5in;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	tab-stops:center 3.25in right 6.5in;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
span.MsoPageNumber
	{mso-style-parent:"";
	mso-ansi-font-size:10.0pt;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
--&gt;
&lt;/style&gt;&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
&lt;/style&gt;
&lt;![endif]--&gt;                                                                    &lt;/meta&gt;
&lt;/meta&gt;
&lt;/meta&gt;
&lt;/meta&gt;
&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/G4MpHEE3KUs" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/G4MpHEE3KUs/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/10/articles/when-are-text-messages-admissible-the-pennsylvania-superior-court-explains/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/tags">admissibility</category><category domain="http://www.ediscoverylawreview.com/tags">admissible</category><category domain="http://www.ediscoverylawreview.com/tags">authentication</category><category domain="http://www.ediscoverylawreview.com/tags">authenticity</category><category domain="http://www.ediscoverylawreview.com/tags">cell phone</category><category domain="http://www.ediscoverylawreview.com/tags">cellular phone</category><category domain="http://www.ediscoverylawreview.com/tags">e-mail</category><category domain="http://www.ediscoverylawreview.com/tags">e-mail account</category><category domain="http://www.ediscoverylawreview.com/tags">electronic</category><category domain="http://www.ediscoverylawreview.com/tags">electronic communication</category><category domain="http://www.ediscoverylawreview.com/tags">evidence</category><category domain="http://www.ediscoverylawreview.com/tags">identity</category><category domain="http://www.ediscoverylawreview.com/tags">instant messages</category><category domain="http://www.ediscoverylawreview.com/tags">text messages</category>
         <pubDate>Fri, 07 Oct 2011 10:50:23 -0800</pubDate>
         <dc:creator>Mike Zabel</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/10/articles/when-are-text-messages-admissible-the-pennsylvania-superior-court-explains/</feedburner:origLink></item>
            <item>
         <title>Cost-Benefit Analysis Adopted by the New York Supreme Court for Determining When a Nonparty Must Undertake the Burden and Expense of Recovering Deleted ESI</title>
         <description>&lt;p&gt;&lt;img vspace="10" hspace="10" border="0" align="left" src="http://www.ediscoverylawreview.com/uploads/image/courtroom.jpg" style="width: 235px; height: 156px;" alt="" /&gt;The production of electronically stored information (&amp;ldquo;ESI&amp;rdquo;) that has been deleted is potentially very expensive and time consuming.&amp;nbsp;Often outside computer forensics experts are required to assist with the recovery of the deleted data and the routine business of the party is disrupted while resources are allocated to the recovery process.&amp;nbsp;These are now commonplace burdens of parties involved in litigation.&amp;nbsp;Whether these burdens should be placed on a nonparty with relevant ESI was recently addressed by the Appellate Division of the New York Supreme Court.&amp;nbsp;In &lt;i&gt;Tener, M.D. v. Cremer, M.D., et al.&lt;/i&gt;, 2011 NY Slip Op. 06543, 2011 N.Y. App. Div. LEXIS 6421 (N.Y. App. Div. Sept. 22, 2011), the court, acknowledging that it was charting new territory, addressed for the first time &amp;ldquo;the obligation of a nonparty to produce electronically stored information (ESI) deleted through normal business operations.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt; at 2.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The nonparty was New York University and the computer at issue was located at Bellevue Medical Center.&amp;nbsp;The plaintiff, a doctor, claimed that someone using the NYU computer posted a comment about her on a website known as Vitals.com.&amp;nbsp;The plaintiff served a subpoena on NYU seeking the identity of all persons who had accessed the internet via the subject IP address on the date that the comment was posted.&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt; &amp;nbsp;NYU did not produce any information in response to the subpoena and the plaintiff moved for contempt.&amp;nbsp;NYU claimed that the &amp;ldquo;computers that simply access the web through NYU&amp;rsquo;s portal appear as a text file listing that is automatically written over every 30 days.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;According to NYU, it lacked the &amp;ldquo;technological capability or software, if such exists, to retrieve a text file created more than a year ago and written over at least 12 times.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt; In response, the plaintiff submitted the affidavit of a computer forensics expert who opined that software with the capability to retrieve the deleted data did exist.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The lower court denied the plaintiff&amp;rsquo;s contempt motion.&amp;nbsp;It held that NYU did not have the capability to retrieve the deleted data and incorrectly concluded that &amp;ldquo;this allegation is unrefuted as a reply affidavit contradicting such allegation has not been supplied.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt; at 3.&lt;/p&gt;
&lt;p&gt;On appeal, the Appellate Division reasoned that &amp;ldquo;ESI is difficult to destroy permanently.&amp;rdquo; &lt;i&gt;Id.&lt;/i&gt; at 4.&amp;nbsp;Rather, &amp;ldquo;[d]eletion usually only makes the data more difficult to access.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;Thus, the &amp;ldquo;discovery rules contemplate data recovery.&amp;rdquo;&lt;i&gt;&amp;nbsp;Id.&lt;/i&gt;&amp;nbsp;For instance, guidelines developed by the Commercial Division for Supreme Court, Nassau County (the &amp;ldquo;Guidelines&amp;rdquo;) &amp;ldquo;suggest that the parties be prepared to discuss &amp;lsquo;the need for certified forensic specialists and/or experts to assist with the search for and production of ESI.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;The Guidelines further explain that &amp;ldquo;ESI is not to be deemed inaccessible based solely on its source or type of storage media.&amp;rdquo; &amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;Rather, &amp;ldquo;[i]naccessibility is based on the burden and expense of recovering and producing the ESI and the relative need for the data.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;Thus, the Guidelines advocate a cost-benefit analysis when discovery of deleted ESI is sought.&lt;/p&gt;
&lt;p&gt;Adopting the Guidelines&amp;rsquo; cost-benefit analysis, the Appellate Division highlighted their similarity to the Federal Rules.&amp;nbsp;Pursuant to Fed. R. Civ. P. 45(d)(1)(D), a nonparty &amp;ldquo;need not provide discovery of electronically stored information from sources that the person identifies as not reasonably accessible because of undue burden or cost.&amp;rdquo;&amp;nbsp;&amp;nbsp; However, the Federal Rules give the federal courts the power to order the production of such information upon a showing of good cause and subject to the limitations of Rule 26(b)(2)(C), which considers, among other things, the burden and expense of production in relation to its likely benefit.&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt; at 5.&lt;/p&gt;
&lt;p&gt;The Appellate Division further reasoned that exempting inaccessible data from discovery &amp;ldquo;might encourage quick deletion as a matter of corporate policy, well before the spectre of litigation is on the horizon and the duty to preserve it attaches.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;A cost-benefit analysis eliminates the incentive to permanently delete information as a matter of course to protect it from production.&amp;nbsp;Additionally, a cost-benefit analysis gives &amp;ldquo;the court the flexibility to determine literally whether the discovery is worth the cost and effort of retrieval.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt; at 6.&lt;/p&gt;
&lt;p&gt;The Appellate Division concluded that the plaintiff had demonstrated &amp;ldquo;good cause&amp;rdquo; for production of the deleted ESI, which had the potential to identify the person who posted the comment and potentially defamed the plaintiff.&amp;nbsp;Given the showing of &amp;ldquo;good cause&amp;rdquo;, the court concluded that a cost-benefit analysis must be undertaken to determine whether the retrieval of the information was warranted.&amp;nbsp;It therefore remanded the case to the lower court because the record did not provide enough information for a proper analysis.&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&lt;/p&gt;
&lt;p&gt;On remand, the Supreme Court was instructed to hold a hearing to determine &amp;ldquo;(1) whether the identifying information was written over, as NYU maintains, or whether it is somewhere else, such as in unallocated space as a text file; (2) whether the retrieval software plaintiff suggested can actually obtain the data; (3) whether the data will identify the actual person who used the internet on April 12, 2009 via the IP address plaintiff identified; (4) which of those persons accessed Vitals.com and (5) a budget for the cost of the data retrieval, including line item(s) correlating the cost to NYU for the disruption.&amp;rdquo;&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;The Appellate Division further instructed that the cost-benefit analysis should take into account the fact that NYU is a nonparty.&amp;nbsp;Finally, in the event the Supreme Court determines that the benefits of production outweigh its costs, the court held that the plaintiff should bear the costs.&lt;/p&gt;
&lt;p&gt;This decision is noteworthy because it clearly defines the analysis the New York state courts must undertake when determining whether a nonparty is required to expend the time and resources to recover ESI that has been deleted.&amp;nbsp;Upon a showing of good cause, a court will analyze the costs of recovering the information against the need for the deleted information. &amp;nbsp;The fact that a nonparty is the entity in possession of the deleted data and the one burdened with recovering the data is a factor to be considered by the court.&lt;/p&gt;
&lt;p&gt;Under this decision, nonparties served with subpoenas for deleted ESI may not rely on the fact that the data has been deleted in the course of its normal business as a means for avoiding the costs of complying with the subpoena.&amp;nbsp;Instead, the nonparty should undertake an active investigation into whether the data can be retrieved, the difficulty of such retrieval and the concomitant costs.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/3yZJ6MnSaHU" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/3yZJ6MnSaHU/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/09/articles/costbenefit-analysis-adopted-by-the-new-york-supreme-court-for-determining-when-a-nonparty-must-undertake-the-burden-and-expense-of-recovering-deleted-esi/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/tags">ESI</category><category domain="http://www.ediscoverylawreview.com/tags">New</category><category domain="http://www.ediscoverylawreview.com/tags">York</category><category domain="http://www.ediscoverylawreview.com/tags">courts</category><category domain="http://www.ediscoverylawreview.com/tags">deleted</category><category domain="http://www.ediscoverylawreview.com/tags">nonparty</category><category domain="http://www.ediscoverylawreview.com/tags">state</category>
         <pubDate>Tue, 27 Sep 2011 05:54:03 -0800</pubDate>
         <dc:creator>Catherine Hamilton</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/09/articles/costbenefit-analysis-adopted-by-the-new-york-supreme-court-for-determining-when-a-nonparty-must-undertake-the-burden-and-expense-of-recovering-deleted-esi/</feedburner:origLink></item>
            <item>
         <title>Ensuring Discovery Compliance:  Sanctions Relating to Past, Present, and Future Adverse Parties</title>
         <description>&lt;p&gt;&lt;img height="134" alt="" width="200" align="right" src="http://www.ediscoverylawreview.com/uploads/image/blog post photo 2.JPG" /&gt;Monetary sanctions, attorneys fees, and adverse inference jury instructions are the more common type of sanctions imposed on litigants for the spoliation of evidence, or not producing relevant documents. Recently, however, a court has increased the severity and impact of sanctions by applying them not only to current litigation, but also to a party&amp;rsquo;s future litigation, with the effects lingering for years to come.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;The Underlying Suit&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;&amp;ldquo;Any competent electronic discovery effort would have located this email.&amp;rdquo; These words were written in an opinion by a United States District Judge in the Eastern District of Texas, filed on March 1, 2011, in &lt;em&gt;Green v. Blitz U.S.A., Inc.&lt;/em&gt;, No. 2:07-CV-372, 2011 U.S. Dist. LEXIS 20353 (E.D. Tex., Mar. 1, 2011)&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Green &lt;/em&gt;involved a product liability suit in which the requirement of a flame arrester was in dispute. The jury returned a defense verdict, and the plaintiff collected a low settlement amount as part of a high-low settlement agreement. During discovery in a subsequent case with the same defendant and plaintiff&amp;rsquo;s counsel, counsel learned of documents that were not produced in &lt;em&gt;Green&lt;/em&gt;. The plaintiff then filed a motion for sanctions against the defendant in &lt;em&gt;Green &lt;/em&gt;and a motion to re-open the &lt;em&gt;Green &lt;/em&gt;case. While the court denied the motion to re-open because the statute of limitations had expired, the court did impose sanctions for the discovery abuse.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;The Defendant&amp;rsquo;s Failure to Conduct Adequate Discovery in &lt;em&gt;Green&lt;/em&gt;&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;After 2004, the defendant had just one employee, Mr. Chrisco, who was responsible for searching for, and collecting, documents relevant to the litigation. Mr. Chrisco would meet with the defendant&amp;rsquo;s national counsel, go through the claims, and develop an understanding of what he would be searching for. He would then go to various departments, explain what he was looking for, and ask the departments to look for, and collect, documents. As the litigation was about flame arresters, any documents pertaining to that subject were relevant.&lt;/p&gt;
&lt;p&gt;This is where Mr. Chrisco&amp;rsquo;s preservation and collection efforts ended and where his employer&amp;rsquo;s e-discovery troubles began. The defendant did not &amp;ldquo;institute a litigation-hold of documents, do any electronic word searches for emails, or talk with the IT department regarding how to search for electronic documents.&amp;rdquo; As a result an email entitled &amp;ldquo;FW: Flame Arrester,&amp;rdquo; of which Mr. Chrisco was a recipient, was never produced. Not disclosing this email showed &amp;ldquo;the gravity of [the defendant&amp;rsquo;s] discovery violations for failing to produce relevant documents.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The court found it even &amp;ldquo;more shocking&amp;rdquo; that this email could have been discovered by a simple word search for the &amp;ldquo;obvious term,&amp;rdquo; flame arrester. Even worse was that the individual tasked with the defendant&amp;rsquo;s e-discovery efforts, Mr. Chrisco, admitted to being &amp;ldquo;about as computer . . . illiterate as they get.&amp;rdquo; The court concluded that one did not have to look any further than not searching for the phrase, &amp;ldquo;flame arrester,&amp;rdquo; to determine that the defendant did not make a reasonable effort to produce relevant documents.&lt;/p&gt;
&lt;p&gt;The court also found that the defendant did not properly preserve documents. Instead of issuing a litigation hold, the defendant asked employees to delete electronic documents at least ten times during the two year period that the defendant was in litigation. Moreover, the defendant rotated its backup tapes every two weeks, causing any deleted emails to be permanently deleted.&lt;/p&gt;
&lt;p&gt;&lt;u&gt;Imposition of Sanctions&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;The court imposed three sets of sanctions against the defendant, each seemingly more severe than the previous. First, the court fined the defendant $250,000 to be paid to the plaintiff, the amount by which the court estimated the plaintiff was damaged by not seeing the documents during settlement discussions. Second, the court sanctioned the defendant an additional $500,000, which was to be tolled for thirty days. The court agreed to lift this fine if, in those thirty days, the defendant was able to prove that it issued a copy of the court&amp;rsquo;s memorandum and opinion to any plaintiff in each lawsuit in which it was involved for the past two years, or in which it is currently involved. Third, the court ordered the defendant to file a copy of the court&amp;rsquo;s memorandum and order with its &amp;ldquo;first pleading or filing&amp;rdquo; in any case in which the defendant was involved, &amp;ldquo;whether plaintiff, defendant, or in another official capacity,&amp;rdquo; for the next five years.&lt;/p&gt;
&lt;p&gt;No litigant would want an e-discovery violation to be a recurring nightmare, as it was for the defendant in &lt;em&gt;Green&lt;/em&gt;. The following are some ways that a party may fulfill its e-discovery obligations and avoid the result in &lt;em&gt;Green&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;&amp;bull; &lt;em&gt;Put the Right Employees in Charge&lt;/em&gt;. Strategically choose the individual or individuals that are in charge of collection efforts in house (for example, do not choose an individual who is not familiar with the company&amp;rsquo;s technology).&lt;/p&gt;
&lt;p&gt;&amp;bull; &lt;em&gt;Take Advantage of Counsel&amp;rsquo;s Expertise&lt;/em&gt;. Engage in communications with counsel who has experience and expertise in e-discovery issues. This will ensure that obligations at each stage of the process are complied with and can be defended later.&lt;/p&gt;
&lt;p&gt;&amp;bull; &lt;em&gt;Issue Litigation Holds&lt;/em&gt;. Make sure that a plan is developed to identify triggering events that would give rise to the obligation to issue a litigation hold to your employees and ensure that the litigation holds are promptly issued and include a specific instruction not to delete documents.&lt;/p&gt;
&lt;p&gt;The court&amp;rsquo;s sanctions are becoming increasingly harsh. The sanctions in &lt;em&gt;Green &lt;/em&gt;had the same effect as publishing the defendant&amp;rsquo;s e-discovery violations in a newspaper. The above guidelines can help you avoid becoming the next headline.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/tNWY4bbw8qg" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/tNWY4bbw8qg/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/09/articles/ensuring-discovery-compliance-sanctions-relating-to-past-present-and-future-adverse-parties/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/articles">Sanctions</category><category domain="http://www.ediscoverylawreview.com/tags">e-discovery</category><category domain="http://www.ediscoverylawreview.com/tags">e-discovery compliance</category><category domain="http://www.ediscoverylawreview.com/tags">litigation hold</category><category domain="http://www.ediscoverylawreview.com/tags">spoliation</category>
         <pubDate>Thu, 22 Sep 2011 03:38:27 -0800</pubDate>
         <dc:creator>F Brenden Coller</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/09/articles/ensuring-discovery-compliance-sanctions-relating-to-past-present-and-future-adverse-parties/</feedburner:origLink></item>
            <item>
         <title>When an Employee Tweets</title>
         <description>&lt;p&gt;&amp;nbsp;&lt;span style="font-size: small;"&gt;&lt;img width="200" vspace="10" hspace="10" height="268" border="0" align="left" src="http://www.ediscoverylawreview.com/uploads/image/Foster tweet(1).jpg" alt="" /&gt;Another day.&amp;nbsp;Another TWITTER event.&amp;nbsp;This time it involves the National Football League.&amp;nbsp;Last week, star running back Arian Foster sent a copy of a MRI image showing his severely injured hamstring to all of his followers by TWITTER.&amp;nbsp;His &amp;ldquo;tweet&amp;rdquo; included an explanation of where his hamstring was specifically damaged.&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small;"&gt;The problem is that NFL teams fight hard to keep this type of information private.&amp;nbsp;Foster is one of the top running backs in the league and his availability for the first week of the season, which starts next weekend, was in question.&amp;nbsp;NFL teams often guard this information zealously.&amp;nbsp;They do not want the opposition to find out how injured their players are.&amp;nbsp;Even if a player is not going to play, NFL teams want their opponents to have to prepare as if Foster or another star player would be available.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small;"&gt;There is also the gambling angle.&amp;nbsp;The league administration has strong and very specific rules about the disclosure of injury information.&amp;nbsp;Teams must be accurate in the disclosure of their information so that other teams aren&amp;rsquo;t prejudiced.&amp;nbsp;This, of course, is used by the gambling industry to make sure that the betting lines are accurate.&amp;nbsp;One can only image how quickly the betting line moved before the Houston Texas operator after Foster sent his MRI to the world.&amp;nbsp;Once can also imagine that his MRI was viewed by the team physicians for the other 31 other teams in the league, including the Texans first opponent, just to determine the likelihood that Foster was going to be able to play.&amp;nbsp;On the way to work this morning I was listening to sport talk radio show, were one of the commentators, &amp;nbsp;an ex-NFL player said that Foster&amp;rsquo;s MRI showed his opposition exactly where they needed to hit him to do the most damage.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small;"&gt;On the same show, they interviewed Brian Kelly, the head coach of the Notre Dame Fighting Irish football team, about his players&amp;rsquo; use of TWITTER.&amp;nbsp;During his interview, he made a great point.&amp;nbsp;He said that TWITTER and Facebook and other forms of social media are here to stay.&amp;nbsp;You cannot tell players, even college ones, that they can&amp;rsquo;t use it.&amp;nbsp;So, instead, he teaches them how to manage it.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small;"&gt;Employers should use the same approach.&amp;nbsp;Don&amp;rsquo;t try to prohibit outright use of TWITTER by your employees.&amp;nbsp;Social media is here to stay.&amp;nbsp;I recently read an article that predicted &amp;nbsp;that -- in three to five years -- e-mail accounts run by social media sites will be used for 80% of the business e-mail in the world.&amp;nbsp;This is stunning.&amp;nbsp;One can only imagine the implications.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small;"&gt;Social media isn&amp;rsquo;t going any where and TWITTER, much to the chagrin of many, isn&amp;rsquo;t going anywhere either.&amp;nbsp;Employers should assume that their employees will use TWITTER an outright prohibition on TWITTER and social media is doomed to fail.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small;"&gt;Players must also adopt a specific policy.&amp;nbsp;This policy must specifically identify the company that should not be disclosed by employees by either via TWITTER or other forms of social media.&amp;nbsp;The policy is important because it gives fair notice to employees that their conduct may result in termination.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small;"&gt;If you ever tried a case in front of a jury, you quickly realize the jurors are not interested in applying the technicalities of the law.&amp;nbsp;Juries are interested in fairness.&amp;nbsp;After they issue a verdict and they walk out of the courtroom, they want to feel like they spent their time dispensing justice, not legal technicalities.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small;"&gt;This is why a policy is so important.&amp;nbsp;It is inherently fair to fire an employee for using TWITTER after they have been advised in writing that doing so could result in their termination.&amp;nbsp;Fair notice is an essential element of the fairness that juries look for when they are deciding cases.&amp;nbsp;This is why a policy is so important.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small;"&gt;Like Coach Kelly, employers should train their employees on the right way to use TWITTER and other forms of social media.&amp;nbsp;Just like with email, employees must assume that every &amp;ldquo;tweet&amp;rdquo; will end up on the front page of &lt;i&gt;The New York Times&lt;/i&gt;.&amp;nbsp;As everyone knows, &amp;ldquo;tweets&amp;rdquo; are potentially discoverable.&amp;nbsp;&amp;ldquo;Tweets&amp;rdquo; could be saved for several months or even longer on Blackberries, iPhones and iPads.&amp;nbsp;During this training, employees must also be told that they need to avoid the impulse to TWITTER right away about a work event.&amp;nbsp;You can&amp;rsquo;t take a tweet back; there is no &amp;ldquo;pullback&amp;rdquo; button.&amp;nbsp;Once a tweets is on the internet, its there forever.&amp;nbsp;Employees should be encouraged to be very judicious in their work-related &amp;ldquo;tweets&amp;rdquo;, to the extent they are even authorized to do them.&amp;nbsp;And before pushing the send button, employees should to think about the way a potential &amp;ldquo;tweet&amp;rdquo; could be used against them or use of other competition.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small;"&gt;To protect their confidential information, employers should also monitor the use of TWITTER and other forms of social media.&amp;nbsp;To protect confidential information in the courts, employers must prove that they took reasonable efforts to protect the secrecy of that information.&amp;nbsp;For certain types of employers who know that their employees essentially engage in social &amp;nbsp;media and are authorized to do it for some business purposes, these employers should actively monitor the internet to make sure that their confidential information and trade secrets are not being disclosed by their employees to the rest of the world.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small;"&gt;In the same vein, employers must be very careful to limit access to the most secret information to a small group of employees.&amp;nbsp;As Mark Zuckerberg, Facebook&amp;rsquo;s founder and CEO stated, privacy in the world is essentially dead.&amp;nbsp;Keeping this in mind, employers should work their IT departments to make sure that their most confidential information is protected by limiting internal and external access; by setting up the data so that it cannot be transferred, copied, and/or printed; and by using software that easily tracks who accesses the document, when and what has been done with it.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small;"&gt; So, once again, though the world of TWITTER can provide valuable insight for employers.&amp;nbsp;The NFL literally spends millions of dollars trying to protect information regarding players injuries.&amp;nbsp;Players are often told not even to tell their family about their injuries because teams will fear that this information will be divulged.&amp;nbsp;Now, because of an iPhone and TWITTER, the world can see a very clear picture of Arian Foster&amp;rsquo;s MRI showing a significant injury to his hamstring. &amp;nbsp;And there is no way for him to pull it back.&amp;nbsp;This is the kind of story that keeps most employers up at night, and it&amp;rsquo;s an important lesson for us all.&lt;/span&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/Uu-IeKkX-lA" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/Uu-IeKkX-lA/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/09/articles/opinions/when-an-employee-tweets/</guid>
         <category domain="http://www.ediscoverylawreview.com/tags">Arian</category><category domain="http://www.ediscoverylawreview.com/tags">Employment</category><category domain="http://www.ediscoverylawreview.com/tags">Facebook</category><category domain="http://www.ediscoverylawreview.com/tags">Foster</category><category domain="http://www.ediscoverylawreview.com/tags">MRI</category><category domain="http://www.ediscoverylawreview.com/articles">Opinions</category><category domain="http://www.ediscoverylawreview.com/tags">Twitter</category><category domain="http://www.ediscoverylawreview.com/tags">and</category><category domain="http://www.ediscoverylawreview.com/tags">employee</category><category domain="http://www.ediscoverylawreview.com/tags">law</category><category domain="http://www.ediscoverylawreview.com/tags">media</category><category domain="http://www.ediscoverylawreview.com/tags">policy</category><category domain="http://www.ediscoverylawreview.com/tags">social</category><category domain="http://www.ediscoverylawreview.com/tags">tweet</category>
         <pubDate>Wed, 07 Sep 2011 11:17:36 -0800</pubDate>
         <dc:creator>David J. Walton</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/09/articles/opinions/when-an-employee-tweets/</feedburner:origLink></item>
            <item>
         <title>Prevailing Parties May Recover E-Discovery Costs Under the Federal Rules</title>
         <description>&lt;p&gt;&lt;img height="200" alt="" width="150" align="right" src="http://www.ediscoverylawreview.com/uploads/image/shutterstock_70342576(1).jpg" /&gt;The Clerk for the U.S. District Court for the Eastern District of Pennsylvania recently ruled that there is a heavy presumption that prevailing parties may recover certain e-discovery costs under &lt;a href="http://www.law.cornell.edu/uscode/html/uscode28/usc_sec_28_00001920----000-.html"&gt;28 U.S.C. &amp;sect; 1920&lt;/a&gt;. &lt;a href="http://www.law.cornell.edu/rules/frcp/Rule54.htm"&gt;Federal Rule of Civil Procedure 54(d)(1)&lt;/a&gt; allows prevailing parties to submit bills of costs for certain expenses, enumerated in &lt;a href="http://www.law.cornell.edu/uscode/html/uscode28/usc_sec_28_00001920----000-.html"&gt;28 U.S.C. &amp;sect; 1920&lt;/a&gt;, for taxation by the Clerk against the non-prevailing parties. For example, that statute provides for the taxation of costs related to obtaining copies of transcripts and printing. More significantly, the statute provides for the taxation of &amp;ldquo;[f]ees for exemplification and the cost of making copies of any materials where the copies are necessarily obtained for use in the case.&amp;rdquo; &lt;a href="http://www.law.cornell.edu/uscode/html/uscode28/usc_sec_28_00001920----000-.html"&gt;28 U.S.C. &amp;sect; 1920(4)&lt;/a&gt;. While the term &amp;ldquo;exemplification&amp;rdquo; is undefined, federal district clerks have traditionally awarded, as exemplification and copying costs, those costs related to the production of paper documents, photographs, models, maps, blow-ups, charts, and diagrams.&lt;/p&gt;
&lt;p&gt;In expanding the categories of production costs recognized as &amp;ldquo;exemplification&amp;rdquo; expenses, the Clerk of Court for the Eastern District of Pennsylvania, in &lt;em&gt;Hank&amp;rsquo;s Beverage Co. v. Ajinomoto Co.&lt;/em&gt;, Civ. No. 06-cv-1732 (E.D. Pa. Jul. 26, 2011) (&lt;a href="http://www.ediscoverylawreview.com/uploads/file/https___ecf_paed_uscourts_gov_cgi-bin_show_temp_pl_file=9301805-0--4053(1).pdf"&gt;slip op.&lt;/a&gt;), awarded to the prevailing defendants e-discovery exemplification costs totaling over $500,000. These costs, which do not include the fees incurred by counsel in reviewing the documents, were related to the production of documents, such as processing native files, restoring back-up tape files, hosting and storing documents in electronic databases, scanning hard copy documents, de-duplicating documents, and filtering the documents to capture the documents containing the agreed-upon search terms. The court described these allowable expenses as the &amp;ldquo;costs of hiring a private company that possesses the technology to &lt;em&gt;search for, and/or to recreate, copies of evidence in electronic form&lt;/em&gt;, for the purpose of making the alleged facts contained in the exhibits more clear to the finder(s) of fact . . . .&amp;rdquo; The court explained that such costs are justified for taxation because &amp;ldquo;generally, neither attorneys nor employees of attorneys are competent to conduct such a search, or to recreate such documents in paper format.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The Clerk in &lt;em&gt;Hank&amp;rsquo;s Beverage &lt;/em&gt;further explained that there is a heavy presumption that &amp;ldquo;the 'prevailing party' &lt;em&gt;automatically &lt;/em&gt;is entitled to costs as a matter of course once it has been shown that the costs sought are arguably of the types of costs listed in &lt;a href="http://www.law.cornell.edu/uscode/html/uscode28/usc_sec_28_00001920----000-.html"&gt;28 U.S.C. &amp;sect; 1920&lt;/a&gt;.&amp;rdquo; With this heavy presumption, the Clerk cannot, for example, disallow costs because the losing party is indigent or because the suit was brought in good faith. The &amp;ldquo;heavy presumption&amp;rdquo; of automatic taxation exists because the taxation of costs, as opposed to attorney&amp;rsquo;s fees, is simply &amp;ldquo;ministerial.&amp;rdquo; Likewise, since the award of costs is not punitive, the prevailing parties need not demonstrate any bad acts of their adversaries. The Clerk, however, may find that the prevailing parties are undeserving of such costs for their own bad acts or improprieties.&lt;/p&gt;
&lt;p&gt;The Clerk&amp;rsquo;s willingness to treat e-discovery costs as taxable against the non-prevailing party will likely give pause to parties with e-discovery intensive cases. Prevailing parties, in submitting their post-trial bills of cost, should be mindful to request the taxation of e-discovery costs by the Clerk after a victory.&amp;nbsp;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/tbeZAvLn6MQ" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/tbeZAvLn6MQ/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/08/articles/prevailing-parties-may-recover-ediscovery-costs-under-the-federal-rules/</guid>
         <category domain="http://www.ediscoverylawreview.com/tags">28 U.S.C. § 1920</category><category domain="http://www.ediscoverylawreview.com/tags">54(d)(1)</category><category domain="http://www.ediscoverylawreview.com/tags">Ajinomoto</category><category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/tags">Beverage'</category><category domain="http://www.ediscoverylawreview.com/tags">Hank</category><category domain="http://www.ediscoverylawreview.com/tags">costs</category><category domain="http://www.ediscoverylawreview.com/tags">exemplification</category><category domain="http://www.ediscoverylawreview.com/tags">s</category>
         <pubDate>Tue, 30 Aug 2011 18:30:33 -0800</pubDate>
         <dc:creator>Robert Chu</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/08/articles/prevailing-parties-may-recover-ediscovery-costs-under-the-federal-rules/</feedburner:origLink></item>
            <item>
         <title>Cost Recovery Toolbox: Exceptional Cases under 35 U.S.C. § 285</title>
         <description>&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small"&gt;&lt;img height="133" alt="" width="200" align="left" src="http://www.ediscoverylawreview.com/uploads/image/tool box.jpg" /&gt;&amp;nbsp;In a &lt;/span&gt;&lt;a href="http://www.ediscoverylawreview.com/2011/06/articles/recovering-ediscovery-costs-in-federal-court/"&gt;&lt;span style="font-size: small"&gt;recent post on this blog&lt;/span&gt;&lt;/a&gt;&lt;span style="font-size: small"&gt;, fellow contributor Mike Zabel addressed how a prevailing party might recover the costs of e-discovery in litigating disputes in federal court under &lt;/span&gt;&lt;a href="http://www.law.cornell.edu/uscode/usc_sec_28_00001920----000-.html"&gt;&lt;span style="font-size: small"&gt;28 U.S.C. &amp;sect; 1920&lt;/span&gt;&lt;/a&gt;&lt;span style="font-size: small"&gt;.&amp;nbsp;In &lt;/span&gt;&lt;i&gt;&lt;a href="http://www.ediscoverylawreview.com/uploads/file/Eon-Net v Flagstar.pdf"&gt;&lt;span style="font-size: small"&gt;Eon-Net LP v. Flagstar Bancorp&lt;/span&gt;&lt;/a&gt;&lt;/i&gt;&lt;span style="font-size: small"&gt;, No. 2009-1308, 2011 U.S. App. LEXIS 15650 (Fed. Cir. July 29, 2011), the Court of Appeals for the Federal Circuit highlighted another avenue for litigants in patent cases to recover costs based on discovery violations, affirming sanctions of nearly $500,000 for litigation misconduct.&amp;nbsp;Under &lt;/span&gt;&lt;a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxl_35_U_S_C_285.htm"&gt;&lt;span style="font-size: small"&gt;35 U.S.C. &amp;sect; 285&lt;/span&gt;&lt;/a&gt;&lt;span style="font-size: small"&gt;, the court may award the prevailing party in a patent dispute reasonable attorneys fees in &amp;ldquo;exceptional cases.&amp;rdquo;&amp;nbsp;Plaintiff Eon-Net engaged in improper tactics and made a habit of filing nuisance infringement cases&amp;nbsp;&amp;ndash; well over one hundred of them in total &amp;ndash; but the court began its exceptional case discussion with Eon-Net&amp;rsquo;s &amp;ldquo;retention policy.&amp;rdquo;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small"&gt;Eon-Net adopted a policy that it would not retain relevant documents and destroyed important documents pursuant to that policy.&amp;nbsp;Indeed, Eon-Net&amp;rsquo;s principal testified that &amp;ldquo;I don&amp;rsquo;t save anything so I don&amp;rsquo;t have to look.&amp;rdquo;&amp;nbsp;&lt;i&gt;Flagstar&lt;/i&gt;, 2011 U.S. App. LEXIS 15650, at *18.&amp;nbsp;Eon-Net&amp;rsquo;s approach actively rejected any duty to save documents related to the infringement claim upon which the suit was brought and violated its duty to preserve evidence during prior lawsuits on the same patents.&amp;nbsp;&lt;i&gt;Id.&lt;/i&gt;&amp;nbsp;Based on this misconduct, as well as Eon-Net&amp;rsquo;s improper legal tactics, the court affirmed a&amp;nbsp;costs award that approached $500,000.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small"&gt;Discovery sanctions under &lt;/span&gt;&lt;a href="http://www.law.cornell.edu/rules/frcp/Rule37.htm"&gt;&lt;span style="font-size: small"&gt;Rule 37&lt;/span&gt;&lt;/a&gt;&lt;span style="font-size: small"&gt; and prevailing party costs under 28 U.S.C. &amp;sect; 1920 allow litigants to recoup discovery costs in certain circumstances.&amp;nbsp;The threat of sanctions under either of those rules should be sufficient to keep parties from engaging in outrageous conduct such as the conduct of the plaintiff in &lt;i&gt;Flagstar&lt;/i&gt;.&amp;nbsp;When an opposing party engages in such tactics, however, parties to patent litigation should keep the &amp;ldquo;exceptional case&amp;rdquo; rule in mind as another tool for recovering costs lost due to discovery misconduct.&lt;/span&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/wZprGNghtl4" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/wZprGNghtl4/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/08/articles/cost-recovery-toolbox-exceptional-cases-under-35-usc-a-285/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/tags">costs</category><category domain="http://www.ediscoverylawreview.com/tags">exceptional case</category>
         <pubDate>Fri, 19 Aug 2011 07:09:18 -0800</pubDate>
         <dc:creator>Michael Broadbent</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/08/articles/cost-recovery-toolbox-exceptional-cases-under-35-usc-a-285/</feedburner:origLink></item>
            <item>
         <title>I'm Responsible To Do What?  Counsel's Affirmative Duty To Ensure Compliance With Litigation Holds</title>
         <description>&lt;p&gt;&lt;img height="179" alt="" width="250" align="left" src="http://www.ediscoverylawreview.com/uploads/image/blog post photo.jpg" /&gt;A corporate defendant discovers that it will be subject to litigation, yet it actively destroys probative, relevant evidence. Many of us have read, or heard of, opinions where judges have punished a spoliating-defendant by issuing sanctions anywhere from an adverse inference instruction to an entry of default judgment. In recent years, however, it is not only the client that has felt the weight of the responsibility in discovery matters. Starting with &lt;em&gt;Zublake v. UBS Warburg (&amp;ldquo;Zublake V&amp;rdquo;)&lt;/em&gt;, 229 F.R.D. 422 (S.D.N.Y. 2004), courts all over the country have emphasized the duty placed on counsel&amp;mdash;both in-house and outside&amp;mdash;to ensure that clients comply with their discovery obligations.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;
Many courts have quoted &lt;em&gt;Zubulake V&lt;/em&gt;&amp;rsquo;s famous line, stating that counsel &amp;ldquo;must take affirmative steps to monitor compliance so that all sources of discoverable information are identified and searched.&amp;rdquo; In &lt;em&gt;Qualcomm Inc. v. Broadcom Corp.&lt;/em&gt;, 05-cv-1958, 2008 U.S. Dist. LEXIS 911 (S.D. Ca., Jan. 7, 2008), for example, the Southern District of California found Qualcomm&amp;rsquo;s counsel responsible for a &amp;ldquo;monumental discovery violation&amp;rdquo; because counsel &amp;ldquo;did not conduct a reasonable inquiry into the adequacy of Qualcomm&amp;rsquo;s document search and production.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;
This responsibility is not restricted to outside counsel. In &lt;em&gt;Danis v. USN Communications, Inc.&lt;/em&gt;, No. 98 C 7482, 2000 U.S. Dist. LEXIS 16900 (N.D. Ill. Oct. 23, 2000), the court recognized that in-house counsel did not establish any meaningful document retention program. In-house counsel failed to: 1) give notice to employees to preserve documents; 2) provide criteria as to what should and should not be saved; 3) review any documents that were being thrown away; and 4) review existing practices related to document retention.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;
Although both in-house and outside counsel can be, and have been, sanctioned for failing to adequately monitor their clients&amp;rsquo; compliance with discovery obligations, the following are some steps that can be taken to avoid this result:&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;
&amp;bull; &lt;em&gt;Be proactive&lt;/em&gt;. Identify the triggering events that give rise to the duty to preserve. Once that obligation is triggered, issue a timely and comprehensive litigation hold.&lt;/p&gt;
&lt;p&gt;&amp;bull; &lt;em&gt;Communicate effectively and often&lt;/em&gt;. Do not assume that employees understand what the litigation entails, what their obligations are under the litigation hold, or what documents may be relevant to the litigation.&lt;/p&gt;
&lt;p&gt;&amp;bull; &lt;em&gt;Identify and interview key employees&lt;/em&gt;. Focus on employees who are likely to have relevant information to: educate them as to the case; learn about, and preserve, relevant information; and ensure compliance with your litigation hold.&lt;/p&gt;
&lt;p&gt;&amp;bull; &lt;em&gt;Contact opposing counsel&lt;/em&gt;. Explain your process for collecting relevant information to opposing counsel. If the other side has any issues with your process, it is better to resolve these sooner rather than later.&lt;/p&gt;
&lt;p&gt;&amp;bull; &lt;em&gt;Communicate frequently&lt;/em&gt;. Do not assume that once you issue a litigation hold, your obligations are fulfilled. Do frequently follow-up to ensure that all employees are preserving potentially relevant documents and data.&lt;/p&gt;
&lt;p&gt;&amp;bull; &lt;em&gt;Consider the Court&amp;rsquo;s involvement&lt;/em&gt;. One of the clearest ways to ensure that your clients&amp;rsquo; discovery obligations, and yours, are fulfilled is to ask the court to set specific standards with respect to the scope and duration of preservation and how data will be reviewed and produced. Being willing to seek court intervention early on will educate the court as to the volume of information and the cost involved and may lead the court to set limits on ongoing preservation and document production.&lt;/p&gt;
&lt;p&gt;The responsibility for compliance with the rules with respect to discovery is shared between the client and their counsel. In-house and outside counsel and the various custodians of potentially relevant information need to work as a team and keep the lines of communication open to ensure that their obligations are fulfilled. This allows all involved to comply with their discovery obligations and to identify key documents&amp;mdash;favorable and unfavorable&amp;mdash;early on and develop their litigation strategy accordingly.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/7kpGDipoIV0" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/7kpGDipoIV0/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/08/articles/im-responsible-to-do-what-counsels-affirmative-duty-to-ensure-compliance-with-litigation-holds/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/tags">duty</category><category domain="http://www.ediscoverylawreview.com/tags">e-discovery</category><category domain="http://www.ediscoverylawreview.com/tags">electronic</category><category domain="http://www.ediscoverylawreview.com/tags">preservation</category><category domain="http://www.ediscoverylawreview.com/tags">preserve</category><category domain="http://www.ediscoverylawreview.com/tags">spoliation</category>
         <pubDate>Thu, 18 Aug 2011 10:51:28 -0800</pubDate>
         <dc:creator>F Brenden Coller</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/08/articles/im-responsible-to-do-what-counsels-affirmative-duty-to-ensure-compliance-with-litigation-holds/</feedburner:origLink></item>
            <item>
         <title>Litigation Holds, Take 2</title>
         <description>&lt;p&gt;Once a litigation hold has been drafted, the next steps are to effectively issue, implement, and monitor the hold.&amp;nbsp;These steps are equally critical to ensuring a litigation hold is successful.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt 0.5in; text-indent: -0.25in"&gt;6.&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;How is an effective litigation hold notice issued?&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;An effective litigation hold notice cannot be issued unless, and until, key personnel are identified and informed.&amp;nbsp;This includes personnel in a company&amp;rsquo;s IT department who are responsible for overseeing the preservation of electronic documents.&amp;nbsp;Also, designate one contact person for all preservation related questions.&amp;nbsp;This ensures that information is provided to personnel in a consistent manner.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;The litigation hold MUST be in writing!&amp;nbsp;Many courts require that a litigation hold be in writing in order to be valid.&amp;nbsp;Similarly, ask personnel to complete written acknowledgements, detailing receipt of the litigation hold notice, their understanding of the hold notice, and their agreement to comply with the hold notice.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;When issuing the litigation hold, effective communication is key.&amp;nbsp;Describe the litigation in general terms with understandable language, and avoid legal terms at all costs.&amp;nbsp;Broadly state where relevant data and information could be located.&amp;nbsp;Provide instructions on how to preserve relevant information.&amp;nbsp;Finally, explain the consequences for non-compliance, particularly the importance of not destroying or altering relevant information.&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt 0.5in; text-indent: -0.25in"&gt;7.&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;How should the litigation hold process be maintained and reviewed?&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;A litigation hold is not static.&amp;nbsp;It is a continuing obligation, of which personnel constantly should be reminded.&amp;nbsp;Send reminder notices and encourage personnel to ask questions if any exist.&amp;nbsp;Always consider whether new players or data is involved.&amp;nbsp;Continually document the steps taken to implement and monitor the litigation hold.&amp;nbsp;Depending on the situation, an entity may have a responsibility to utilize outside counsel to monitor the litigation hold process.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt 0.5in; text-indent: -0.25in"&gt;8.&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;When and how should a litigation hold be released?&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;A litigation hold may be released when a party no longer is reasonably aware of the possibility of litigation.&amp;nbsp;When releasing the hold, contact all parties who received the original litigation hold notice, and notify them that their obligations under the hold have ceased.&amp;nbsp;At this time, any document destruction policies may be reintroduced.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;Examples of when a litigation hold should be released include the withdrawal of a complaint, the completion of a deal, and the exhaustion of the appeals process.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt 0.5in; text-indent: -0.25in"&gt;9.&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;Are litigation holds discoverable?&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;Normally, litigation holds are not discoverable.&amp;nbsp;However, litigation holds can become discoverable if questions or concerns surround a party&amp;rsquo;s efforts to preserve relevant information.&amp;nbsp;This is why documenting the litigation hold process is crucial.&amp;nbsp;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/xDqERIRbao4" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/xDqERIRbao4/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/08/articles/litigation-holds-take-2/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category>
         <pubDate>Tue, 16 Aug 2011 05:16:19 -0800</pubDate>
         <dc:creator>Rachel S. Fendell</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/08/articles/litigation-holds-take-2/</feedburner:origLink></item>
            <item>
         <title>Litigation Holds, Take 1</title>
         <description>&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Developing, drafting and implementing a litigation hold are critical to the e-discovery process.&amp;nbsp;A litigation hold ensures that all relevant information is preserved and later helps to ensure that discovery can be responded to efficiently, accurately, and appropriately.&amp;nbsp;Accordingly, a successful litigation hold reduces the possibility of sanctions during the e-discovery process.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt; text-indent: 0.25in"&gt;This first post on litigation holds, provides answers to questions about the beginning of the litigation hold process.&amp;nbsp;The second post, will more thoroughly address the actual implementation of the hold.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt 0.5in; text-indent: -0.25in"&gt;1.&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;What is a litigation hold?&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;During a litigation hold, parties to the litigation preserve, keep, and store potentially relevant information.&amp;nbsp;Parties also must suspend any document destruction policy they follow, for both printed and electronic documents.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt 0.5in; text-indent: -0.25in"&gt;2.&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;When should a litigation hold be issued?&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;A litigation hold should be issued when a party is reasonably aware that it will be a party to litigation.&amp;nbsp;For a plaintiff, triggers could include filing a complaint, seeking advice of counsel, or sending a cease and desist letter.&amp;nbsp;For a defendant, triggers could include receiving a summons or complaint, receiving official notice of a government investigation, or receiving notice of an accident, receiving discovery requests.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt 0.5in; text-indent: -0.25in"&gt;3.&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;Are litigation hold policies and practices necessary?&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;Yes!&amp;nbsp;Before litigation even arises, it is necessary to implement litigation hold policies and train employees on those policies.&amp;nbsp;Have a process, follow the process, implement the process, and document the process!&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt 0.5in; text-indent: -0.25in"&gt;4.&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;What types of issues should be identified before issuing a litigation hold notice?&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;First, a party needs to identify types of electronically stored information that could contain relevant information.&amp;nbsp;Types of electronically stored information range from data stored on computers (laptops and desktops), to cell phones, to personal data devices (Blackberries, Iphones, etc.), to voicemails.&amp;nbsp;A party also must identify where this data physically is stored and whether the data has multiple storage locations.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;Second, a party needs to identify the players.&amp;nbsp;Players are any individuals who might have been a witness to a relevant event, or individuals who otherwise were exposed to information surrounding a relevant event.&amp;nbsp;Always consider whether the individuals surrounding key players, especially secretaries and assistants, would have relevant information.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 12pt 0in 0pt 0.5in; text-indent: -0.25in"&gt;5.&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;How should the litigation hold process be developed?&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt 1in"&gt;&lt;span&gt;&amp;middot;&lt;span style="font: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;Parties can freely decide how to collect relevant data.&amp;nbsp;In considering the scope of the litigation hold, there are many factors to consider such as the:&amp;nbsp;cost to gather data; number of key players involved; locations of players involved, need to secure an outside expert; location of data; types of data; and accessibility of the data.&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/g6gSC_6i2hc" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/g6gSC_6i2hc/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/08/articles/litigation-holds-take-1/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category>
         <pubDate>Fri, 12 Aug 2011 07:42:30 -0800</pubDate>
         <dc:creator>Rachel S. Fendell</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/08/articles/litigation-holds-take-1/</feedburner:origLink></item>
            <item>
         <title>When Does the Duty to Preserve Electronic Evidence Arise?</title>
         <description>&lt;p&gt;&lt;img width="150" hspace="10" height="217" border="0" align="left" src="http://www.ediscoverylawreview.com/uploads/image/Justice.jpg" alt="" /&gt;The duty to preserve electronic evidence is triggered once a party &amp;ldquo;reasonably anticipates&amp;rdquo; litigation.&amp;nbsp;&lt;u&gt;Silvestri v. GMC&lt;/u&gt;, 271 F.3d 583, 591 (4th Cir. 2001); &amp;nbsp;&lt;u&gt;Pension Committee of the Univ. of Montreal Pension Plan v. Banc of Am. Securities, LLC&lt;/u&gt;, 685 F. Supp. 2d 456, 466 (S.D.N.Y. 2010).&amp;nbsp;At that point, parties have an obligation to suspend their routine document retention and destruction policies and implement a &amp;ldquo;litigation hold&amp;rdquo; to safeguard all relevant evidence. &amp;nbsp;The United States Court of Appeals for the Federal Circuit recently reaffirmed the &amp;ldquo;reasonably foreseeable&amp;rdquo; standard in &lt;u&gt;Micron Tech., Inc. v. Rambus, Inc.&lt;/u&gt;, No. 09-1263, 2011 WL 1815975 (Fed. Cir. May 13, 2011).&amp;nbsp;The Court of Appeals explained that the standard is an objective one, &amp;ldquo;asking not whether the party in fact reasonably foresaw litigation, but whether a reasonable party in the same factual circumstances would have reasonably foreseen litigation.&amp;rdquo;&amp;nbsp;&lt;u&gt;Id.&lt;/u&gt; at *6. &amp;nbsp;Significantly, the Court in &lt;u&gt;Micron&lt;/u&gt; rejected the argument that &amp;ldquo;litigation be &amp;lsquo;imminent, or probable without significant contingencies&amp;rsquo;&amp;rdquo; in order to trigger the duty to preserve.&amp;nbsp;&lt;u&gt;Id.&lt;/u&gt;&amp;nbsp;According to the Court, this argument is based on &amp;ldquo;an overly generous reading of several cases&amp;rdquo; and is at odds with the flexible reasonably foreseeable standard. &amp;nbsp;&lt;u&gt;Id.&lt;/u&gt;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;The &amp;ldquo;reasonable anticipation&amp;rdquo; principle is now well-established but not easily applied as it is necessarily shaped by the factual nuances of the parties&amp;rsquo; dispute.&amp;nbsp;Thus, although it is easy to conclude that a defendant has a duty to preserve electronic evidence once it is served with a summons and complaint, the duty to preserve is often triggered in the pre-litigation stage.&amp;nbsp;This is because the duty to preserve is triggered once the defendant is aware of a credible threat of litigation, which is often before a complaint is filed.&amp;nbsp;Determining the date that the party knew or should have known that litigation is reasonably foreseeable is often a subject of dispute.&amp;nbsp;&lt;u&gt;Viramontes v. U.S. Bancorp&lt;/u&gt;, No. 10-761, 2011 WL 291077 (N.D. Ill. Jan. 27, 2011).&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;Some guiding principles, however, are clear. For large organizations, it is clear that more than one or two employees must reasonably anticipate litigation in order to trigger the duty.&amp;nbsp;&lt;u&gt;Zubulake v. UBS Warburg LLC&lt;/u&gt;, 220 F.R.D. 212, 217 (S.D.N.Y. 2003).&amp;nbsp;Thus, in &lt;u&gt;Toussie v. County of Suffolk&lt;/u&gt;, No. 01-6716, 2007 U.S. Dist. LEXIS 93988 (E.D.N.Y. Dec. 21, 2007), the Court reasoned that the duty to preserve electronic evidence did not arise until the complaint was filed.&amp;nbsp;The Court reasoned that, although a &amp;ldquo;handful&amp;rdquo; of employees expected the plaintiffs&amp;rsquo; lawsuit, &amp;ldquo;there was no evidence to suggest that a substantial number of key personnel anticipated litigation prior&amp;rdquo; to such time.&amp;nbsp;In &lt;u&gt;Viramontes&lt;/u&gt;, the fact that the plaintiff&amp;rsquo;s supervisor suspected that the plaintiff might sue, based on a pre-litigation letter written by the plaintiff complaining about the supervisor&amp;rsquo;s allegedly rude behavior, was not enough to find that the defendant-company should have reasonably anticipated future employment discrimination litigation.&amp;nbsp;2011 WL 291077 at *4.&amp;nbsp;The court reasoned that the letter did not assert that the plaintiff might bring employment discrimination claims and, in fact, it suggested a &amp;ldquo;non-litigious resolution&amp;rdquo; to the plaintiff&amp;rsquo;s complaints regarding her supervisor&amp;rsquo;s behavior.&amp;nbsp;&lt;u&gt;Id.&lt;/u&gt;&amp;nbsp;Furthermore, the plaintiff&amp;rsquo;s claims under the Americans with Disabilities Act and the Family and Medical Leave Act were not filed until ten months later.&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;The indications that litigation may be forthcoming must be more than &amp;ldquo;vague&amp;rdquo; statements and the &amp;ldquo;mere existence of a dispute does not necessarily mean that parties should reasonably anticipate litigation[.]&amp;rdquo;&amp;nbsp;&lt;u&gt;Goodman v. Praxair Servs.&lt;/u&gt;, 632 F. Supp. 2d 494, 510 (D. Md. 2009). &amp;nbsp;Thus, a demand letter may be a sufficient warning that litigation is on the horizon and a letter advising that an attorney has been retained will certainly trigger the duty to preserve.&amp;nbsp;&lt;u&gt;Id.&lt;/u&gt; at 511.&amp;nbsp;Conversely, letters written in the midst of the parties&amp;rsquo; dispute do not necessarily trigger the duty.&amp;nbsp;In &lt;u&gt;Cache La Pourdre Feeds, LLC v. Land O&amp;rsquo;Lakes Farmland Feed, LLC&lt;/u&gt;, 244 F.R.D. 614, 622 (D. Colo. 2007), a letter stating that its purpose was to put the defendant on notice of the plaintiff&amp;rsquo;s trademark rights and &amp;ldquo;determine whether this situation can be resolved without litigation&amp;rdquo; did not trigger a duty to preserve.&amp;nbsp;These cases demonstrate that the determination of the trigger date on the duty to preserve is a fact-intensive inquiry.&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;Also of note is the inter-relationship between the timing of the duty to preserve and application of the work product privilege.&amp;nbsp;In &lt;u&gt;Siani v. State Univ. of New York at Farmingdale&lt;/u&gt;, No 09-407, 2010 WL 3170664 (E.D.N.Y. Aug. 10, 2010), for example, the plaintiff argued the defendant had a duty to preserve evidence a full year prior to the filing of the complaint because the defendant retained a law firm at that point to represent it in connection with the plaintiff&amp;rsquo;s allegations of ongoing discrimination.&amp;nbsp;The defendant was hard-pressed to argue to the contrary given that it had marked documents as protected by the work-product privilege around that same time.&amp;nbsp;&lt;u&gt;Id.&lt;/u&gt; at *5.&amp;nbsp;The Court reasoned that the &amp;ldquo;commonsense conclusion&amp;rdquo; dictated that if &amp;ldquo;litigation was reasonably foreseeable for one purpose in January 2008, it was reasonably foreseeable for all purposes.&amp;rdquo;&amp;nbsp;&lt;u&gt;Id.&lt;/u&gt;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&amp;nbsp;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;In conclusion, whether and when a party reasonably anticipates litigation, thereby, triggering the duty to preserve electronic evidence depends on many factors, including but not limited to, who within the defendant organization anticipates the litigation, the clarity of the threat, and when privileged documents are created and labeled as such.&amp;nbsp;A reasoned evaluation of all factors is needed and the organization is under a duty to re-evaluate should new information present itself.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/rfL7PJWzICg" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/rfL7PJWzICg/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/08/articles/when-does-the-duty-to-preserve-electronic-evidence-arise/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/tags">duty</category><category domain="http://www.ediscoverylawreview.com/tags">electronic</category><category domain="http://www.ediscoverylawreview.com/tags">evidence</category><category domain="http://www.ediscoverylawreview.com/tags">preserve</category><category domain="http://www.ediscoverylawreview.com/tags">to</category>
         <pubDate>Wed, 10 Aug 2011 06:10:12 -0800</pubDate>
         <dc:creator>Catherine Hamilton</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/08/articles/when-does-the-duty-to-preserve-electronic-evidence-arise/</feedburner:origLink></item>
            <item>
         <title>Discovery in the Age of Cloud Computing</title>
         <description>&lt;p&gt;&lt;span style="font-size: small"&gt;&lt;img height="250" alt="" width="168" src="http://www.ediscoverylawreview.com/uploads/image/int174B.JPG" /&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="font-size: small"&gt;During the last decade, individuals and business have changed the way they manage their data by moving this data management offsite &amp;ndash; otherwise known as cloud computing.&amp;nbsp;This differs from the old model of information management that, more or less, mirrored the pre-computing era, meaning that an employee&amp;rsquo;s file might be kept in a cabinet in a Human Resources (&amp;ldquo;HR&amp;rdquo;) office or stored on a company&amp;rsquo;s in-house server.&amp;nbsp;With cloud computing, however, that same employee file may be stored hundreds or thousands of miles away from the HR officer who needs to review it &amp;ndash; or the IT officer tasked with preserving that data for potential litigation.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small"&gt;Cloud computing outsources data and software management, migrating it from the local to the global by providing instant access over the internet.&amp;nbsp;According to&amp;nbsp;the National Institute of Standards and Technology, cloud computing has five primary characteristics:&amp;nbsp;(1) &amp;ldquo;on-demand self-service,&amp;rdquo; or the ability to call up stored data or capabilities as needed; (2) broad network access through a variety of platforms; (3) pooling resources providing &amp;ldquo;location independence&amp;rdquo;; (4) &amp;ldquo;rapid elasticity&amp;rdquo; in the distribution of computing capabilities, and (5) &amp;ldquo;measured service,&amp;rdquo; or service-appropriate control and optimization by the cloud system manager rather than the local user.&lt;/span&gt;&lt;a title="" href="#_ftn1" name="_ftnref1"&gt;&lt;/a&gt;&lt;span style="font-size: small"&gt;&lt;a title="" href="#_ftn1" name="_ftnref1"&gt;[1]&lt;/a&gt;&amp;nbsp;It is the pooling of resources and the measured service managed by third-parties that pose the greatest risks during e-discovery.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small"&gt;Under the Federal Rules of Civil Procedure, parties must produce copies or descriptions of documents in their possession, custody, or control.&amp;nbsp;By using cloud services, a potential litigant has placed a third-party in the way of important data.&amp;nbsp;&lt;/span&gt;&lt;span style="font-size: small"&gt;That party&lt;/span&gt;&lt;span style="font-size: small"&gt;, however, may not&amp;nbsp;relinquish control over that data and it must be preserved and, possibly, produced. Control of that data could be set forth in the service contract between the cloud provider and the user.&lt;/span&gt;&lt;a title="" href="#_ftn2" name="_ftnref2"&gt;&lt;/a&gt;&lt;span style="font-size: small"&gt;&lt;a title="" href="#_ftn2" name="_ftnref2"&gt;[2]&lt;/a&gt;&amp;nbsp;Control could also be found because a party has the practical ability to access and obtain the documents from a third-party.&lt;/span&gt;&lt;a title="" href="#_ftn3" name="_ftnref3"&gt;&lt;/a&gt;&lt;span style="font-size: small"&gt;&lt;a title="" href="#_ftn3" name="_ftnref3"&gt;[3]&lt;/a&gt;&amp;nbsp;As a result, and to avoid a misstep during discovery, clients and counsel need to fully understand the agreements governing important data &lt;i&gt;and &lt;/i&gt;the actual technology through which the cloud data is accessed.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small"&gt;Parties employing the cloud are also at risk that certain electronically stored information may be overwritten or subject to routine deletion.&amp;nbsp;Moreover, it may not be technologically or commercially feasible for a cloud service provider to prevent routine maintenance when relevant data is pooled with that of thousands or millions of other users.&amp;nbsp;Without significant guidance on the interplay between cloud computing and any safe harbors for good-faith conduct, potential litigants need to be cautious during discovery to take all reasonable and feasible steps to preserve and produce responsive data.&amp;nbsp;Similarly, litigants and their counsel should remember that discovery should be candid, cooperative, and transparent.&lt;/span&gt;&lt;a title="" href="#_ftn4" name="_ftnref4"&gt;&lt;/a&gt;&lt;span style="font-size: small"&gt;&lt;a title="" href="#_ftn4" name="_ftnref4"&gt;[4]&lt;/a&gt;&amp;nbsp;Failing to timely disclose or address issues raised by cloud computing may result in sanctions that could have been avoided.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: small"&gt;Cloud computing creates new layers of uncertainty for businesses or individuals who may later be involved in litigation.&amp;nbsp;Although the data may be stored elsewhere, parties will likely have &amp;ldquo;control&amp;rdquo; over that which is stored in the cloud and will often bear the same responsibilities with respect to preservation and production as they would for files kept on site.&amp;nbsp;Cloud users should routinely assess their risk by reviewing which data and which services are being migrated to, or are currently in, the cloud.&amp;nbsp;Similarly, cloud computing should be taken seriously from its inception.&amp;nbsp;Parties should conduct their due diligence on potential providers, review agreements and policies, and preempt any risk that saving money now will cause serious costs in court.&amp;nbsp;If litigation arises that may involve cloud data or software, parties should be vigilant in preserving that data and documenting this, and all efforts taken to comply with discovery requests.&lt;/span&gt;&lt;/p&gt;
&lt;div&gt;&lt;br clear="all" /&gt;
&lt;hr align="left" width="33%" size="1" /&gt;
&lt;div id="ftn1"&gt;
&lt;p&gt;&lt;a title="" href="#_ftnref1" name="_ftn1"&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;[1]&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;&lt;font size="2"&gt; Peter Mell and Tim Grance, NIST, The NIST Definition of Cloud Computing 1 (2009), &lt;i&gt;available at&lt;/i&gt; http://www.nist.gov/itl/cloud/upload/cloud-def-v15.pdf.&lt;/font&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;div id="ftn2"&gt;
&lt;p&gt;&lt;a title="" href="#_ftnref2" name="_ftn2"&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;[2]&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;&lt;font size="2"&gt; &lt;i&gt;See, e.g.&lt;/i&gt;, &lt;i&gt;Flagg v. City of Detroit&lt;/i&gt;, 252 F.R.D. 346, 354 (E.D. Mich. 2008) (finding that City maintained control over text messages preserved by cell provider &amp;ldquo;pursuant to its contractual relationship&amp;rdquo;).&amp;nbsp;&lt;/font&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;div id="ftn3"&gt;
&lt;p&gt;&lt;a title="" href="#_ftnref3" name="_ftn3"&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;[3]&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;&lt;font size="2"&gt; &lt;i&gt;See, e.g.&lt;/i&gt;, &lt;i&gt;In re NTL, Inc. Sec. Litig.&lt;/i&gt;, 244 F.R.D. 179, 195 (S.D.N.Y. 2007) (noting that control is often interpreted broadly).&lt;/font&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;div id="ftn4"&gt;
&lt;p&gt;&lt;a title="" href="#_ftnref4" name="_ftn4"&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;[4]&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;&lt;font size="2"&gt; &lt;i&gt;See, e.g.&lt;/i&gt;, &lt;i&gt;Cartel Asset Mgmt. v. Ocwen Fin. Corp.&lt;/i&gt;, No. 01-CV-01644-REB-CBS, at 25 (D.Co. Feb. 8, 2010) (order on pending motions), &lt;i&gt;available at&lt;/i&gt; http://www.thesedonaconference.org/content/tsc_cooperation_proclamation (endorsing Sedona Conference Cooperation Proclamation).&lt;/font&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/E-discoveryLawReview/~4/1DCHZJoBsRQ" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/E-discoveryLawReview/~3/1DCHZJoBsRQ/</link>
         <guid isPermaLink="false">http://www.ediscoverylawreview.com/2011/06/articles/discovery-in-the-age-of-cloud-computing/</guid>
         <category domain="http://www.ediscoverylawreview.com/">Articles</category><category domain="http://www.ediscoverylawreview.com/tags">Cloud</category><category domain="http://www.ediscoverylawreview.com/tags">Cloud Computing</category><category domain="http://www.ediscoverylawreview.com/tags">ESI</category><category domain="http://www.ediscoverylawreview.com/tags">Web 2.0</category><category domain="http://www.ediscoverylawreview.com/tags">eDiscovery</category><category domain="http://www.ediscoverylawreview.com/tags">new media</category>
         <pubDate>Mon, 27 Jun 2011 01:29:00 -0800</pubDate>
         <dc:creator>Michael Broadbent</dc:creator>
      
      <feedburner:origLink>http://www.ediscoverylawreview.com/2011/06/articles/discovery-in-the-age-of-cloud-computing/</feedburner:origLink></item>
      
   </channel>
</rss>

