<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: SharePoint vs Content Management</title>
	<atom:link href="http://blog.single-sourcing.com/2009/12/sharepoint-vs-content-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.single-sourcing.com/2009/12/sharepoint-vs-content-management/</link>
	<description>Making &#34;write once, publish everywhere&#34; a reality</description>
	<lastBuildDate>Mon, 14 Mar 2011 14:10:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Liz Fraley</title>
		<link>http://blog.single-sourcing.com/2009/12/sharepoint-vs-content-management/comment-page-1/#comment-19</link>
		<dc:creator>Liz Fraley</dc:creator>
		<pubDate>Wed, 30 Dec 2009 20:15:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.single-sourcing.com/?p=204#comment-19</guid>
		<description>I got an email from someone who was watching a discussion to this effect on LinkedIn that gets to the key of this issue:

&gt;&gt;&gt;
Is it just me or do you too see a lack of insight to lifecycle document management? Too many, including some here, seem to view DM as a repository with a exclusive search engine! Little discussion centers on compliance, e-discovery, classification and appropriate retentions including as needed &#039;legal hold&#039;. Some of these are commonly found in Records Management type software. Since software is usually driven from an IT perspective instead of the stakeholders much of those criteria’s is often overlooked or misunderstood. DM systems serve well during the active phase of a document. At some point it has to live in an ERM system for its entirety. This would alleviate the load on the DM system. I have seen just too many companies get into DM systems without understanding the big picture only to flounder and spend.....
&lt;&lt;&lt;</description>
		<content:encoded><![CDATA[<p>I got an email from someone who was watching a discussion to this effect on LinkedIn that gets to the key of this issue:</p>
<p>>>><br />
Is it just me or do you too see a lack of insight to lifecycle document management? Too many, including some here, seem to view DM as a repository with a exclusive search engine! Little discussion centers on compliance, e-discovery, classification and appropriate retentions including as needed &#8216;legal hold&#8217;. Some of these are commonly found in Records Management type software. Since software is usually driven from an IT perspective instead of the stakeholders much of those criteria’s is often overlooked or misunderstood. DM systems serve well during the active phase of a document. At some point it has to live in an ERM system for its entirety. This would alleviate the load on the DM system. I have seen just too many companies get into DM systems without understanding the big picture only to flounder and spend&#8230;..<br />
<<<</p>
]]></content:encoded>
	</item>
</channel>
</rss>

