<?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: Observations on AIIM 2010</title>
	<atom:link href="http://barclaytblair.com/observations-on-aiim-2010/feed/" rel="self" type="application/rss+xml" />
	<link>http://barclaytblair.com/observations-on-aiim-2010/</link>
	<description>Essays in Information Governance</description>
	<lastBuildDate>Thu, 16 Feb 2012 21:36:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: C3 Associates ECM Blog &#187; Measurement Matters &#8211; And the Important Ones May Not be What You Think</title>
		<link>http://barclaytblair.com/observations-on-aiim-2010/comment-page-1/#comment-58</link>
		<dc:creator>C3 Associates ECM Blog &#187; Measurement Matters &#8211; And the Important Ones May Not be What You Think</dc:creator>
		<pubDate>Wed, 05 May 2010 04:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://barclaytblair.com/?p=426#comment-58</guid>
		<description>[...] already so many excellent summaries out there I&#8217;m not sure what more I could add. I thought Barclay Blair&#8217;s observations were particularly astute, especially as it related to Google&#8217;s perspective on ECM. Mike Alsup [...]</description>
		<content:encoded><![CDATA[<p>[...] already so many excellent summaries out there I&#8217;m not sure what more I could add. I thought Barclay Blair&#8217;s observations were particularly astute, especially as it related to Google&#8217;s perspective on ECM. Mike Alsup [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://barclaytblair.com/observations-on-aiim-2010/comment-page-1/#comment-51</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sun, 25 Apr 2010 17:54:37 +0000</pubDate>
		<guid isPermaLink="false">http://barclaytblair.com/?p=426#comment-51</guid>
		<description>This was an excellent post, especially liked the commentary about the &quot;vendor echo chamber&quot; and engineering driven development, removed from sales and reality. Before the conference, my perception was that the conference would be the Sharepoint Show, combined with a vendor community desperately trying to find their place in the market, and end users still reeling from the great recession. 

Interesting to see Google&#039;s take on E2.0, considering their impact on consumers and the googlization of information is pushing organizations to change their processes and technology to accommodate this new paradigm.</description>
		<content:encoded><![CDATA[<p>This was an excellent post, especially liked the commentary about the &#8220;vendor echo chamber&#8221; and engineering driven development, removed from sales and reality. Before the conference, my perception was that the conference would be the Sharepoint Show, combined with a vendor community desperately trying to find their place in the market, and end users still reeling from the great recession. </p>
<p>Interesting to see Google&#8217;s take on E2.0, considering their impact on consumers and the googlization of information is pushing organizations to change their processes and technology to accommodate this new paradigm.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://barclaytblair.com/observations-on-aiim-2010/comment-page-1/#comment-48</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Fri, 23 Apr 2010 16:37:34 +0000</pubDate>
		<guid isPermaLink="false">http://barclaytblair.com/?p=426#comment-48</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by btblair: Is the information lifecycle less of a circle and more of an infinity symbol? My thoughts on #AIIM10 http://barclaytblair.com/ja6...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by btblair: Is the information lifecycle less of a circle and more of an infinity symbol? My thoughts on #AIIM10 <a href="http://barclaytblair.com/ja6.." rel="nofollow">http://barclaytblair.com/ja6..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Medina</title>
		<link>http://barclaytblair.com/observations-on-aiim-2010/comment-page-1/#comment-47</link>
		<dc:creator>Larry Medina</dc:creator>
		<pubDate>Fri, 23 Apr 2010 16:26:18 +0000</pubDate>
		<guid isPermaLink="false">http://barclaytblair.com/?p=426#comment-47</guid>
		<description>Thanks for another good post, Barclay.

Sadly, this is the same song Google was singing at ARMA in Las Vegas 2 years ago- a few of us engaged them in some lengthy conversations explaining why these models didn&#039;t work (from a business or RM perspective) and what DID work and why. 

The funny thing was they were arguing AGAINST the need to retain e-mail (in certain cases) longer than 5 years, and sometimes either &#039;permanently&#039; or to place holds on it to ensure it was unaltered.  They were of the opinion that all data should be treated equally, and well... sometimes &#039;stuff gets lost or changed&#039; =)  

As for MO$$, I too fear the coming of 2010.  The hype can never match the actual product, but unlike movies, everyone has to hope the sequel is better than the original release.  Biggest issue for me is it STILL doesn&#039;t &#039;get&#039; retention... REAL retention issues like assigning a period longer than 3 years and managing permissions, access rights, allowing for migration, not modifying formal file attributes when viewed or moved, etc.  And everything still needs to be done with the assistance of &#039;trusted partners&#039; through 3rd party products, many of which are not supported when the primary application goes through an upgrade.

From an RM viewpoint, I think I might even fear Exchange 2010 even more.  This blog http://bit.ly/bN8USj sought to ally any fears that Exchange 2010 wasn&#039;t ready for prime time when it comes to retention, but when I submitted a comment (tried 3x) asking for an explanation of a few issues, the writer not only failed to answer them, they refused to post the comment. 

Truly a case of the Emperor&#039;s New Clothes on their part... and in this case, we know who &#039;they&#039; are</description>
		<content:encoded><![CDATA[<p>Thanks for another good post, Barclay.</p>
<p>Sadly, this is the same song Google was singing at ARMA in Las Vegas 2 years ago- a few of us engaged them in some lengthy conversations explaining why these models didn&#8217;t work (from a business or RM perspective) and what DID work and why. </p>
<p>The funny thing was they were arguing AGAINST the need to retain e-mail (in certain cases) longer than 5 years, and sometimes either &#8216;permanently&#8217; or to place holds on it to ensure it was unaltered.  They were of the opinion that all data should be treated equally, and well&#8230; sometimes &#8216;stuff gets lost or changed&#8217; =)  </p>
<p>As for MO$$, I too fear the coming of 2010.  The hype can never match the actual product, but unlike movies, everyone has to hope the sequel is better than the original release.  Biggest issue for me is it STILL doesn&#8217;t &#8216;get&#8217; retention&#8230; REAL retention issues like assigning a period longer than 3 years and managing permissions, access rights, allowing for migration, not modifying formal file attributes when viewed or moved, etc.  And everything still needs to be done with the assistance of &#8216;trusted partners&#8217; through 3rd party products, many of which are not supported when the primary application goes through an upgrade.</p>
<p>From an RM viewpoint, I think I might even fear Exchange 2010 even more.  This blog <a href="http://bit.ly/bN8USj" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/bit.ly/bN8USj?referer=');">http://bit.ly/bN8USj</a> sought to ally any fears that Exchange 2010 wasn&#8217;t ready for prime time when it comes to retention, but when I submitted a comment (tried 3x) asking for an explanation of a few issues, the writer not only failed to answer them, they refused to post the comment. </p>
<p>Truly a case of the Emperor&#8217;s New Clothes on their part&#8230; and in this case, we know who &#8216;they&#8217; are</p>
]]></content:encoded>
	</item>
</channel>
</rss>

