<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Google has its Share of eDiscovery Woes.</title>
	<atom:link href="http://www.kazeon.com/blog/2009/03/google-has-its-share-of-ediscovery-woes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kazeon.com/blog/2009/03/google-has-its-share-of-ediscovery-woes/</link>
	<description></description>
	<lastBuildDate>Thu, 26 Jan 2012 21:20:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Muddu</title>
		<link>http://www.kazeon.com/blog/2009/03/google-has-its-share-of-ediscovery-woes/comment-page-1/#comment-13</link>
		<dc:creator>Muddu</dc:creator>
		<pubDate>Tue, 21 Apr 2009 18:35:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.kazeon.com/blog/?p=71#comment-13</guid>
		<description>Google has a fine search product. But eDiscovery is not just search. It starts with careful identification of all Electronically Stored Information (ESI), across the enterprise no matter what the source. Then, the data has to be analyzed and reviewed for Early Case Assessments – this is best done while leaving the data at their original source in order to avoid moving them around, thus saving network bandwidth and storage costs. Next, the data has to be processed/culled for relevance such that the resulting data set is crisp and small/medium sized. Finally, the data needs to be put under fine-grained analysis and review, including allowing for collaborative/distributed review for in-house as well as external counsel. In addition to the above, the right solution needs to have the ability to perform Legal Hold on key ESI such that it can be proven that the right steps were taken to contain spoliation of data as well as meta-data. On the whole, the eDiscovery process needs to follow an accurate, defensible, legal case workflow with the ability to allow multiple user roles, such as legal administrator/supervisor or reviewer. Once all of this is complete, corporations will want to export the relevant dataset for production and presentation. All of this constitutes eDiscovery, and unless a vendor offers all these capabilities in a modular fashion, I would strongly recommend looking around for options. Therefore software options need to be carefully chosen in order to implement in-house eDiscovery.</description>
		<content:encoded><![CDATA[<p>Google has a fine search product. But eDiscovery is not just search. It starts with careful identification of all Electronically Stored Information (ESI), across the enterprise no matter what the source. Then, the data has to be analyzed and reviewed for Early Case Assessments – this is best done while leaving the data at their original source in order to avoid moving them around, thus saving network bandwidth and storage costs. Next, the data has to be processed/culled for relevance such that the resulting data set is crisp and small/medium sized. Finally, the data needs to be put under fine-grained analysis and review, including allowing for collaborative/distributed review for in-house as well as external counsel. In addition to the above, the right solution needs to have the ability to perform Legal Hold on key ESI such that it can be proven that the right steps were taken to contain spoliation of data as well as meta-data. On the whole, the eDiscovery process needs to follow an accurate, defensible, legal case workflow with the ability to allow multiple user roles, such as legal administrator/supervisor or reviewer. Once all of this is complete, corporations will want to export the relevant dataset for production and presentation. All of this constitutes eDiscovery, and unless a vendor offers all these capabilities in a modular fashion, I would strongly recommend looking around for options. Therefore software options need to be carefully chosen in order to implement in-house eDiscovery.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ</title>
		<link>http://www.kazeon.com/blog/2009/03/google-has-its-share-of-ediscovery-woes/comment-page-1/#comment-8</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Tue, 24 Mar 2009 13:57:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.kazeon.com/blog/?p=71#comment-8</guid>
		<description>Muddu, could you expand on the Google legal problems a bit? I have been concerned with the lack of tools for some time, but continue to be presented with GoogleApps (By ill advised management)  as a viable alternative to traditional in-house applications and eDiscovery methods. Notwithstanding the fact that they have recently had security problems with sharing, I have serious doubts about their ability to do litigation holds accross ALL of their application suites.

Thanks,

Russ</description>
		<content:encoded><![CDATA[<p>Muddu, could you expand on the Google legal problems a bit? I have been concerned with the lack of tools for some time, but continue to be presented with GoogleApps (By ill advised management)  as a viable alternative to traditional in-house applications and eDiscovery methods. Notwithstanding the fact that they have recently had security problems with sharing, I have serious doubts about their ability to do litigation holds accross ALL of their application suites.</p>
<p>Thanks,</p>
<p>Russ</p>
]]></content:encoded>
	</item>
</channel>
</rss>

