<?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: SharePoint: Real World Perspectives</title>
	<atom:link href="http://www.informationarchitected.com/blog/sharepoint-real-world-perspectives/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.informationarchitected.com/blog/sharepoint-real-world-perspectives/</link>
	<description>Information Architected is a consultancy focused on the intelligent use of content, knowledge and processes to drive innovation and thrive in a digital world.</description>
	<lastBuildDate>Thu, 22 Jul 2010 07:17:10 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: berndburkert</title>
		<link>http://www.informationarchitected.com/blog/sharepoint-real-world-perspectives/comment-page-1/#comment-588</link>
		<dc:creator>berndburkert</dc:creator>
		<pubDate>Fri, 15 Jan 2010 19:10:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitected.com/?p=438#comment-588</guid>
		<description>The concept of referential integrity so far has not been a particular strenght of SharePoint. Microsoft apparently understood this is a weak point, and has announced improvements with SP2010. How far this shall take us?  I&#039;m afraid we have to wait and see. It&#039;s hard to implement very basic concepts in a product about 10 years later...&lt;br&gt;&lt;br&gt;“A big problem we have with SharePoint (other than a proliferation of isolated departmental installations) is that links to documents in our large document library break if we re-organize parts of the logical tree structure of our library, since references are only available as path names. In previous work at other companies with Xerox DocuShare product, I could use DocuShare’s permanent document IDs in our URL-based cross-document links and be free to reorganize our logical organization. [ This person went on to ask: ] Do you know of a solution to this problem with SharePoint? ” [Does anyone?]</description>
		<content:encoded><![CDATA[<p>The concept of referential integrity so far has not been a particular strenght of SharePoint. Microsoft apparently understood this is a weak point, and has announced improvements with SP2010. How far this shall take us?  I&#39;m afraid we have to wait and see. It&#39;s hard to implement very basic concepts in a product about 10 years later&#8230;</p>
<p>“A big problem we have with SharePoint (other than a proliferation of isolated departmental installations) is that links to documents in our large document library break if we re-organize parts of the logical tree structure of our library, since references are only available as path names. In previous work at other companies with Xerox DocuShare product, I could use DocuShare’s permanent document IDs in our URL-based cross-document links and be free to reorganize our logical organization. [ This person went on to ask: ] Do you know of a solution to this problem with SharePoint? ” [Does anyone?]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.informationarchitected.com/blog/sharepoint-real-world-perspectives/comment-page-1/#comment-75</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Wed, 08 Apr 2009 16:29:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitected.com/?p=438#comment-75</guid>
		<description> 
 
I agree that there are issues with Sharepoint and effective utilization requires either training or professional services (or both). But when used properly there is a huge payback. 
 
I firmly believe, though that to achieve the payback organizations must: 
1] perform proper planning on the front end, including adoption planning/culture change as well as targeting applications and ROI 
and 
2] Understand that SharePoint is more successfully viewed as a framework for building collaborative and productivity solutions around office products rahter than as a fully featured ECM tool. 
 </description>
		<content:encoded><![CDATA[<p>I agree that there are issues with Sharepoint and effective utilization requires either training or professional services (or both). But when used properly there is a huge payback. </p>
<p>I firmly believe, though that to achieve the payback organizations must:<br />
1] perform proper planning on the front end, including adoption planning/culture change as well as targeting applications and ROI<br />
and<br />
2] Understand that SharePoint is more successfully viewed as a framework for building collaborative and productivity solutions around office products rahter than as a fully featured ECM tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl Frappaolo</title>
		<link>http://www.informationarchitected.com/blog/sharepoint-real-world-perspectives/comment-page-1/#comment-74</link>
		<dc:creator>Carl Frappaolo</dc:creator>
		<pubDate>Wed, 08 Apr 2009 16:28:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitected.com/?p=438#comment-74</guid>
		<description> 
 
Simon: 
 
Thanks for the comments. Despite the fact that you are a solution provider, I have posted your comments, because you clearly point out the fact that your views are somewhat prejudiced by your affiliation with Autonomy. Thank you for your honesty - and your input. I hope other will feel free to share their opinions on how SharePoint implementations can be made more effective. 
And, BTW, since you asked, the 15 day construction project here in Boston made their deadline. You can learn more about it at &lt;a href=&quot;http://www.15days.tv/15days.html.&quot; target=&quot;_blank&quot;&gt;http://www.15days.tv/15days.html.&lt;/a&gt; 
 </description>
		<content:encoded><![CDATA[<p>Simon: </p>
<p>Thanks for the comments. Despite the fact that you are a solution provider, I have posted your comments, because you clearly point out the fact that your views are somewhat prejudiced by your affiliation with Autonomy. Thank you for your honesty &#8211; and your input. I hope other will feel free to share their opinions on how SharePoint implementations can be made more effective.<br />
And, BTW, since you asked, the 15 day construction project here in Boston made their deadline. You can learn more about it at <a href="http://www.15days.tv/15days.html." target="_blank"></a><a href="http://www.15days.tv/15days.html" rel="nofollow">http://www.15days.tv/15days.html</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Cole</title>
		<link>http://www.informationarchitected.com/blog/sharepoint-real-world-perspectives/comment-page-1/#comment-73</link>
		<dc:creator>Simon Cole</dc:creator>
		<pubDate>Wed, 08 Apr 2009 16:28:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitected.com/?p=438#comment-73</guid>
		<description>Hi Carl, 
 
I read your blog with great interest. 
 
I didn&#039;t make it to the seminar on SharePoint (and I haven&#039;t got round to catching up with it yet, but the issues raised by customers validates what we see in the market on a daily basis. I work for Autonomy and in relation to the question raised above regarding refernces, the Autonomy RM solution, previously Meridio, has an excellent solution to this with Smart Shortcuts - The content is moved outside of SharePoint (which can only be a good thing, SQL is not the place to store content), also it keeps MOSS license costs down (albeit you need an Autonomy license!). 
 
Anyway, just thought I&#039;d share this. I don&#039;t really expect this to be posted as it may come across as a blatant attempt to advertise our wares on your blog! If you haven&#039;t already, you should check out the Autnomy ControlPoint solution aimed at tackling the compliance and management issues around SharePoint, if for no other reason to be aware that the big players have cottoned onto the SharePoint issue and the need to solve the issues around it. 
 
One other thought (and maybe I missed an update somewhere along the line). What ever happened to that rush building job they were doing round the corner from where you live/work. Did BPM mke it all possible or did they forget to order nails and it all came crashing down round them? 
 
Best Regards, 
Simon Cole </description>
		<content:encoded><![CDATA[<p>Hi Carl, </p>
<p>I read your blog with great interest. </p>
<p>I didn&#039;t make it to the seminar on SharePoint (and I haven&#039;t got round to catching up with it yet, but the issues raised by customers validates what we see in the market on a daily basis. I work for Autonomy and in relation to the question raised above regarding refernces, the Autonomy RM solution, previously Meridio, has an excellent solution to this with Smart Shortcuts &#8211; The content is moved outside of SharePoint (which can only be a good thing, SQL is not the place to store content), also it keeps MOSS license costs down (albeit you need an Autonomy license!). </p>
<p>Anyway, just thought I&#039;d share this. I don&#039;t really expect this to be posted as it may come across as a blatant attempt to advertise our wares on your blog! If you haven&#039;t already, you should check out the Autnomy ControlPoint solution aimed at tackling the compliance and management issues around SharePoint, if for no other reason to be aware that the big players have cottoned onto the SharePoint issue and the need to solve the issues around it. </p>
<p>One other thought (and maybe I missed an update somewhere along the line). What ever happened to that rush building job they were doing round the corner from where you live/work. Did BPM mke it all possible or did they forget to order nails and it all came crashing down round them? </p>
<p>Best Regards,<br />
Simon Cole</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/


Served from: www.informationarchitected.com @ 2010-07-29 16:43:44 -->