<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>nSourceIT &#187; e-Discovery</title>
	<atom:link href="http://www.nsourceit.com/category/e-discovery/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nsourceit.com</link>
	<description>Information Technology, e-Discovery, and Litigation Support Services</description>
	<lastBuildDate>Tue, 27 Jul 2010 14:20:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>A primer on e-Discovery ethics</title>
		<link>http://www.nsourceit.com/2010/04/01/a-primer-on-e-discovery-ethics/</link>
		<comments>http://www.nsourceit.com/2010/04/01/a-primer-on-e-discovery-ethics/#comments</comments>
		<pubDate>Thu, 01 Apr 2010 18:26:23 +0000</pubDate>
		<dc:creator>Ed Valio</dc:creator>
				<category><![CDATA[ED.IT Blog Posting]]></category>
		<category><![CDATA[e-Discovery]]></category>
		<category><![CDATA[case law]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[ethics]]></category>

		<guid isPermaLink="false">http://www.nsourceit.com/?p=769</guid>
		<description><![CDATA[From Practical e-Discovery:  &#8221;Lawson v. Sun Microsystems, Inc., 2010 WL 503054 (S.D. Ind. February 8, 2010) - Lawson is an ediscovery decision that has flown under the radar of most bloggers and legal commentators. It is a relatively short opinion, addressing whether sanctions should be imposed on the plaintiff and his former attorneys after the plaintiff [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://blog.hinshawlaw.com/practicalediscovery/2010/03/29/a-primer-on-ediscovery-ethics/" target="_blank">Practical e-Discovery</a>:  &#8221;Lawson v. Sun Microsystems, Inc., 2010 WL 503054 (S.D. Ind. February 8, 2010) - Lawson is an ediscovery decision that has flown under the radar of most bloggers and legal commentators. It is a relatively short opinion, addressing whether sanctions should be imposed on the plaintiff and his former attorneys after the plaintiff unlocked certain password-protected documents produced by defendant in discovery that were privileged. The decision, however, implicates a number of ethical issues and the case could be used in teaching a course on ediscovery ethics.  Because of the brevity of the district court’s opinion, many of the facts discussed below are taken from the Magistrate’s Report and Recommendation which can be read <a href="http://www.scribd.com/doc/29109552" target="_blank">here</a>.</p>
<p style="text-align: center;"><img class="aligncenter size-full wp-image-770" title="ethics" src="http://www.nsourceit.com/wp-content/uploads/2010/04/ethics.gif" alt="" width="410" height="300" /></p>
<p>The Magistrate, in addressing the defendant’s sanctions motion, described the issues presented by that motion as:</p>
<p>&#8216;[T]he perfect storm of problems that can arise from voluminous electronic discovery in high stakes litigation. As with the storm of any magnitude – and this one might qualify as a Category 5 from the National Hurricane Center – the damage can be severe. Such is the case in the wake of this maelstrom.&#8217;</p>
<p>The defendant claimed in its motion for sanctions that the case was an &#8216;ediscovery version of Watergate,&#8217; with the plaintiff acting as &#8216;the henchman who broke into the password-protected documents&#8217; and his counsel engaging in the &#8216;cover-up.&#8217; The district court, however, was not persuaded. While a relatively modest monetary sanction was imposed upon the plaintiff, the district court ultimately vacated the Magistrate’s recommended monetary sanction on plaintiff’s former counsel. Even when the defendant’s hyperbole is ignored, Lawson presents a number of knotty ethical issues that practitioners must be ready to recognize and properly address.&#8221;</p>
<p><a href="http://blog.hinshawlaw.com/practicalediscovery/2010/03/29/a-primer-on-ediscovery-ethics/" target="_blank">Practical e-Discovery &#8211; A Primer on e-Discovery ethics</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nsourceit.com/2010/04/01/a-primer-on-e-discovery-ethics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Microsoft to release documentation for Outlook .pst file format</title>
		<link>http://www.nsourceit.com/2009/11/02/microsoft-to-release-documentation-for-outlook-pst-file-format/</link>
		<comments>http://www.nsourceit.com/2009/11/02/microsoft-to-release-documentation-for-outlook-pst-file-format/#comments</comments>
		<pubDate>Mon, 02 Nov 2009 16:56:07 +0000</pubDate>
		<dc:creator>Ed Valio</dc:creator>
				<category><![CDATA[ED.IT Blog Posting]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[e-Discovery]]></category>
		<category><![CDATA[file format]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Outlook]]></category>
		<category><![CDATA[PST]]></category>

		<guid isPermaLink="false">http://www.nsource.info/?p=567</guid>
		<description><![CDATA[A post on &#8220;Interoperability @ Microsoft&#8221; last week by Paul Lorimer revealed that Microsoft intends to release documentation for Outlook&#8217;s .pst file format.

&#8221;In order to facilitate interoperability and enable customers and vendors to access the data in .pst files on a variety of platforms, we will be releasing documentation for the .pst file format. This [...]]]></description>
			<content:encoded><![CDATA[<p>A post on &#8220;<a href="http://blogs.msdn.com/interoperability/archive/2009/10/26/roadmap-for-outlook-personal-folders-pst-documentation.aspx">Interoperability @ Microsoft</a>&#8221; last week by Paul Lorimer revealed that Microsoft intends to release documentation for Outlook&#8217;s .pst file format.</p>
<p style="text-align: center;"><a href="http://nsource.info/wp-content/uploads/2009/11/outlook_2007_logo.jpg"><img class="aligncenter size-medium wp-image-568" style="border: 0px;" title="outlook_2007_logo" src="http://nsource.info/wp-content/uploads/2009/11/outlook_2007_logo-271x265.jpg" alt="outlook_2007_logo" width="271" height="265" /></a></p>
<p>&#8221;In order to facilitate interoperability and enable customers and vendors to access the data in .pst files on a variety of platforms, we will be releasing documentation for the .pst file format. This will allow developers to read, create, and interoperate with the data in .pst files in server and client scenarios using the programming language and platform of their choice. The technical documentation will detail how the data is stored, along with guidance for accessing that data from other software applications. It also will highlight the structure of the .pst file, provide details like how to navigate the folder hierarchy, and explain how to access the individual data objects and properties.</p>
<p>This documentation is still in its early stages and work is ongoing. We are engaging directly with industry experts and interested customers to gather feedback on the quality of the technical documentation to ensure that it is clear and useful. When it is complete, it will be released under our Open Specification Promise, which will allow anyone to implement the .pst file format on any platform and in any tool, without concerns about patents, and without the need to contact Microsoft in any way.&#8221;</p>
<p>I think this is going to turn out to be big news for folks in both the IT and e-Discovery fields.</p>
<p><a href="http://blogs.msdn.com/interoperability/archive/2009/10/26/roadmap-for-outlook-personal-folders-pst-documentation.aspx" target="_blank">Interoperability @ Microsoft &#8211; Roadmap for Outlook Personal Folders (.pst) Documentation</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nsourceit.com/2009/11/02/microsoft-to-release-documentation-for-outlook-pst-file-format/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>In-House Counsel Sanctioned for Defendant’s Failure to Preserve Evidence</title>
		<link>http://www.nsourceit.com/2009/11/01/in-house-counsel-sanctioned-for-defendant%e2%80%99s-failure-to-preserve/</link>
		<comments>http://www.nsourceit.com/2009/11/01/in-house-counsel-sanctioned-for-defendant%e2%80%99s-failure-to-preserve/#comments</comments>
		<pubDate>Mon, 02 Nov 2009 02:34:02 +0000</pubDate>
		<dc:creator>Ed Valio</dc:creator>
				<category><![CDATA[ED.IT Blog Posting]]></category>
		<category><![CDATA[e-Discovery]]></category>
		<category><![CDATA[eDiscovery]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[in-house counsel]]></category>
		<category><![CDATA[sanctions]]></category>

		<guid isPermaLink="false">http://www.nsource.info/?p=559</guid>
		<description><![CDATA[From Ralph Losey&#8217;s &#8220;e-Discovery Team&#8221; blog:
&#8221;Many courts have imposed monetary sanctions against outside counsel of record for their negligence in working with their clients to preserve evidence. See eg., Green v. McClendon, 2009 WL 2496275 (S.D.N.Y. Aug. 13, 2009) (discussed before in Mathematical Formula for Justice Proves the Importance of ESI in Civil Litigation). But [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://ralphlosey.wordpress.com/2009/11/01/in-house-counsel-sanctioned-for-defendants-failure-to-preserve-evidence/" target="_blank">Ralph Losey&#8217;s &#8220;e-Discovery Team&#8221; blog</a>:</p>
<p>&#8221;Many courts have imposed monetary sanctions against outside counsel of record for their negligence in working with their clients to preserve evidence. See eg., Green v. McClendon, 2009 WL 2496275 (S.D.N.Y. Aug. 13, 2009) (discussed before in Mathematical Formula for Justice Proves the Importance of ESI in Civil Litigation). But this decision goes a step further and reaches behind the curtain to impose sanctions against in-house counsel. This was not your typical in-house counsel situation either. It was not a remote in-house attorney representing a large corporation. The attorney sanctioned was the general counsel for a local governmental entity, the Seminole County Sheriff’s Department.</p>
<p style="text-align: center;"><a href="http://nsource.info/wp-content/uploads/2009/11/footprint.jpg"><img class="aligncenter size-medium wp-image-560" style="border: 0px;" title="footprint" src="http://nsource.info/wp-content/uploads/2009/11/footprint-271x180.jpg" alt="footprint" width="271" height="180" /></a></p>
<p>This District Court opinion has not been published yet, but I expect it will be soon. It is, as far as I know, the first in the country to impose a monetary sanction against an in-house counsel who was not an attorney of record and was not a named party. The amount of the sanction has not yet been determined by the District Court judge who entered the order, but it will be substantial. The plaintiff incurred costs and attorney fees in excess of $300,000 to bring and prove the sanctions motion.&#8221;</p>
<p>Read more &#8211; <a href="http://ralphlosey.wordpress.com/2009/11/01/in-house-counsel-sanctioned-for-defendants-failure-to-preserve-evidence/">e-Discovery Team: In-House Counsel Sanctioned for Defendant’s Failure to Preserve Evidence</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nsourceit.com/2009/11/01/in-house-counsel-sanctioned-for-defendant%e2%80%99s-failure-to-preserve/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AZ Supreme Court: Metadata is public record</title>
		<link>http://www.nsourceit.com/2009/10/29/az-supreme-court-metadata-is-public-record/</link>
		<comments>http://www.nsourceit.com/2009/10/29/az-supreme-court-metadata-is-public-record/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 03:52:14 +0000</pubDate>
		<dc:creator>Ed Valio</dc:creator>
				<category><![CDATA[ED.IT Blog Posting]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[e-Discovery]]></category>
		<category><![CDATA[Arizona]]></category>
		<category><![CDATA[ESI]]></category>
		<category><![CDATA[metadata]]></category>

		<guid isPermaLink="false">http://www.nsource.info/?p=533</guid>
		<description><![CDATA[From ARS Technica:
&#8221;The Arizona state Supreme Court has ruled that the metadata attached to public records is itself public, and cannot be withheld in response to a public records request. Such a ruling on file metadata may not seem like a huge win for open government advocates, but it definitely is, given that metadata has [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://arstechnica.com/tech-policy/news/2009/10/lobbyists-beware-arizona-rules-metadata-is-public-record.ars?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=rss" target="_blank">ARS Technica</a>:</p>
<p>&#8221;The Arizona state Supreme Court has ruled that the metadata attached to public records is itself public, and cannot be withheld in response to a public records request. Such a ruling on file metadata may not seem like a huge win for open government advocates, but it definitely is, given that metadata has unmasked more than one lobbyist&#8217;s effort to influence Congress.&#8221;</p>
<p style="text-align: center;"><a href="http://nsource.info/wp-content/uploads/2009/10/AZ-Court-Seal.JPG"><img class="aligncenter size-medium wp-image-534" title="AZ Court Seal" src="http://nsource.info/wp-content/uploads/2009/10/AZ-Court-Seal-271x256.jpg" alt="AZ Court Seal" width="271" height="256" /></a></p>
<p><a href="http://arstechnica.com/tech-policy/news/2009/10/lobbyists-beware-arizona-rules-metadata-is-public-record.ars?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=rss" target="_blank">ARS Technica &#8211; Lobbyists beware: judge rules metadata is public record</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nsourceit.com/2009/10/29/az-supreme-court-metadata-is-public-record/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Things to Think About for Your Rule 26(f) Meeting</title>
		<link>http://www.nsourceit.com/2009/10/27/things-to-think-about-for-your-rule-26f-meeting/</link>
		<comments>http://www.nsourceit.com/2009/10/27/things-to-think-about-for-your-rule-26f-meeting/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 12:40:50 +0000</pubDate>
		<dc:creator>Ed Valio</dc:creator>
				<category><![CDATA[ED.IT Blog Posting]]></category>
		<category><![CDATA[e-Discovery]]></category>
		<category><![CDATA[26(f)]]></category>
		<category><![CDATA[case management]]></category>
		<category><![CDATA[discovery plan]]></category>
		<category><![CDATA[ESI]]></category>

		<guid isPermaLink="false">http://www.nsource.info/?p=504</guid>
		<description><![CDATA[From Bow Tie Law&#8217;s Blog:
In a case management hearing, the parties were directed to consider the following electronically stored information (ESI) issues at their Rule 26(f) conference for drafting their proposed Rule 16(b) order:
With regard to any discoverable electronically stored information (ESI) the parties may have, the Court further requests that the joint discovery plan [...]]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://bowtielaw.wordpress.com" target="_blank">Bow Tie Law&#8217;s Blog</a>:</p>
<p>In a case management hearing, the parties were directed to consider the following electronically stored information (ESI) issues at their Rule 26(f) conference for drafting their proposed Rule 16(b) order:</p>
<blockquote><p><em>With regard to any discoverable electronically stored information (ESI) the parties may have, the Court further requests that the joint discovery plan also include any issues and concerns related to the following:</em></p>
<p><em>a. What ESI is available and where it resides;</em></p>
<p><em>b. Ease/difficulty and cost of producing information;</em></p>
<p><em>c. Schedule and format of production;</em></p>
<p><em>d. Preservation of information; and</em></p>
<p><em>e. Agreements about privilege or work-product protection.</em></p>
<p><em> Wallace v. Tindall, 2009 U.S. Dist. LEXIS 89669, *2-3 (W.D. Mo. Sept. 29, 2009).</em></p></blockquote>
<p style="text-align: center;"><img class="size-medium wp-image-505  aligncenter" title="thinker" src="http://nsource.info/wp-content/uploads/2009/10/thinker-271x361.jpg" alt="thinker" width="271" height="361" /></p>
<p><a href="http://bowtielaw.wordpress.com/2009/10/22/things-to-think-about-for-your-rule-26f-meeting%E2%80%A6/" target="_blank">Bow Tie Law&#8217;s Blog &#8211; Things to Think About for Your Rule 26(f) Meeting&#8230;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nsourceit.com/2009/10/27/things-to-think-about-for-your-rule-26f-meeting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
