<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Thinking Records &#124; Thinking Records</title>
	<atom:link href="http://thinkingrecords.co.uk/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://thinkingrecords.co.uk</link>
	<description>James Lappin's records management blog</description>
	<lastBuildDate>Fri, 16 Dec 2011 02:46:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Is there a sustainable and scaleable records management model in SharePoint 2010? by Future Proof &#8211; Protecting our digital future &#187; Initial advice on implementing recordkeeping requirements in SharePoint 2010</title>
		<link>http://thinkingrecords.co.uk/2010/07/28/does-sharepoint-2010-have-a-sustainable-and-scaleable-records-management-model/#comment-813</link>
		<dc:creator><![CDATA[Future Proof &#8211; Protecting our digital future &#187; Initial advice on implementing recordkeeping requirements in SharePoint 2010]]></dc:creator>
		<pubDate>Fri, 16 Dec 2011 02:46:45 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingrecords.co.uk/?p=1161#comment-813</guid>
		<description><![CDATA[[...] together some excellent blog posts about implementation decisions concerning SharePoint. His post ‘Is there a sustainable and scaleable records management model in SharePoint 2010?’ outlines some of the issues to consider in relation to SharePoint’s flexible model. The comments [...]]]></description>
		<content:encoded><![CDATA[<p>[...] together some excellent blog posts about implementation decisions concerning SharePoint. His post ‘Is there a sustainable and scaleable records management model in SharePoint 2010?’ outlines some of the issues to consider in relation to SharePoint’s flexible model. The comments [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is SharePoint good for? by Nick Inglis (@nickinglis)</title>
		<link>http://thinkingrecords.co.uk/2011/11/13/what-is-sharepoint-good-for/#comment-791</link>
		<dc:creator><![CDATA[Nick Inglis (@nickinglis)]]></dc:creator>
		<pubDate>Wed, 23 Nov 2011 17:30:13 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingrecords.co.uk/?p=1690#comment-791</guid>
		<description><![CDATA[The thing about box is that it looks like a screwdriver, but it really is one of those multitipped screwdrivers. With their open API architecture and their new /bin program for developers they will be able to provide (if not already) the complete array of features that SharePoint offers and in the future pose a serious threat to SharePoint.]]></description>
		<content:encoded><![CDATA[<p>The thing about box is that it looks like a screwdriver, but it really is one of those multitipped screwdrivers. With their open API architecture and their new /bin program for developers they will be able to provide (if not already) the complete array of features that SharePoint offers and in the future pose a serious threat to SharePoint.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is SharePoint good for? by Links for 2011-11-13 &#124; Vorsprung durch Bürokratie</title>
		<link>http://thinkingrecords.co.uk/2011/11/13/what-is-sharepoint-good-for/#comment-790</link>
		<dc:creator><![CDATA[Links for 2011-11-13 &#124; Vorsprung durch Bürokratie]]></dc:creator>
		<pubDate>Wed, 23 Nov 2011 10:53:55 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingrecords.co.uk/?p=1690#comment-790</guid>
		<description><![CDATA[[...] What is SharePoint good for? « Thinking Records &#8220;Rob Koplowitz said that SharePoint was a Swiss army knife of a product that had a huge array of different features. A service like Box.net was like a screwdriver – it did one job (filesharing). But if you only want a screwdriver, why buy a Swiss army knife?&#8221; [...]]]></description>
		<content:encoded><![CDATA[<p>[...] What is SharePoint good for? « Thinking Records &#8220;Rob Koplowitz said that SharePoint was a Swiss army knife of a product that had a huge array of different features. A service like Box.net was like a screwdriver – it did one job (filesharing). But if you only want a screwdriver, why buy a Swiss army knife?&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Is SharePoint a records management system? &#8211; podcast by stephen (@dasmacintosh2)</title>
		<link>http://thinkingrecords.co.uk/2011/10/19/is-sharepoint-a-records-management-system-podcast/#comment-764</link>
		<dc:creator><![CDATA[stephen (@dasmacintosh2)]]></dc:creator>
		<pubDate>Tue, 08 Nov 2011 00:47:21 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingrecords.co.uk/?p=1619#comment-764</guid>
		<description><![CDATA[Hi Fellas

I think this is a very interesting and helpful podcast. I particularly like the note of caution that comes into the conversation around the 38th minute. My concern, though, is that your depiction of microsoft is akin to setting up a straw man. The progress made between sharepoint 2007 and sharepoint 2010 suggests that, far from being an afterthought, microsoft has thought very hard and imginatively about RM and are making good progress. I am lookning forward to your next podcast about the integration of sharepoint and traditional EDRMS products.]]></description>
		<content:encoded><![CDATA[<p>Hi Fellas</p>
<p>I think this is a very interesting and helpful podcast. I particularly like the note of caution that comes into the conversation around the 38th minute. My concern, though, is that your depiction of microsoft is akin to setting up a straw man. The progress made between sharepoint 2007 and sharepoint 2010 suggests that, far from being an afterthought, microsoft has thought very hard and imginatively about RM and are making good progress. I am lookning forward to your next podcast about the integration of sharepoint and traditional EDRMS products.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Preserving e-mail &#8211; records management perspectives by Pourquoi conserver les courriels est plus difficile qu&#8217;il ne semble &#124; Le regard de Janus</title>
		<link>http://thinkingrecords.co.uk/2011/08/11/preserving-e-mail-records-management-perspectives/#comment-705</link>
		<dc:creator><![CDATA[Pourquoi conserver les courriels est plus difficile qu&#8217;il ne semble &#124; Le regard de Janus]]></dc:creator>
		<pubDate>Sat, 01 Oct 2011 18:11:41 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingrecords.co.uk/?p=1475#comment-705</guid>
		<description><![CDATA[[...] ce sujet qui complète celui de Chris, suite à une discussion lors du séminaire. L’original est ici et la traduction là: [...]]]></description>
		<content:encoded><![CDATA[<p>[...] ce sujet qui complète celui de Chris, suite à une discussion lors du séminaire. L’original est ici et la traduction là: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Preserving e-mail &#8211; records management perspectives by Nicola Franklin</title>
		<link>http://thinkingrecords.co.uk/2011/08/11/preserving-e-mail-records-management-perspectives/#comment-698</link>
		<dc:creator><![CDATA[Nicola Franklin]]></dc:creator>
		<pubDate>Tue, 20 Sep 2011 10:36:58 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingrecords.co.uk/?p=1475#comment-698</guid>
		<description><![CDATA[Very interesting reflections James.  I recently saw the trend towards &quot;every business application to have enough records management functionality to manage its own records&quot;, exemplified by the new MoReq standard, being enacted in practice, at the IRMS site visit to Dyson&#039;s R&amp;D headquarters. 
I&#039;ve written about it in more detail on my blog  (http://thelibrarycareer.blogspot.com/2011/08/event-irms-site-visit-to-dyson-r-centre.html), but in summary they rejected the option of an EDRM (despite having a £4m budget available to implement one) and instead are building RM functionality into their line of business systems.  
Clare - there was certainly also an element there of &#039;employees not users&#039; and &#039;just get on with following the procedures&#039; there as well!  Perhaps it helps them that their users are largely engineers and programmers, who are used to structured procedures?]]></description>
		<content:encoded><![CDATA[<p>Very interesting reflections James.  I recently saw the trend towards &#8220;every business application to have enough records management functionality to manage its own records&#8221;, exemplified by the new MoReq standard, being enacted in practice, at the IRMS site visit to Dyson&#8217;s R&amp;D headquarters.<br />
I&#8217;ve written about it in more detail on my blog  (<a href="http://thelibrarycareer.blogspot.com/2011/08/event-irms-site-visit-to-dyson-r-centre.html" rel="nofollow">http://thelibrarycareer.blogspot.com/2011/08/event-irms-site-visit-to-dyson-r-centre.html</a>), but in summary they rejected the option of an EDRM (despite having a £4m budget available to implement one) and instead are building RM functionality into their line of business systems.<br />
Clare &#8211; there was certainly also an element there of &#8216;employees not users&#8217; and &#8216;just get on with following the procedures&#8217; there as well!  Perhaps it helps them that their users are largely engineers and programmers, who are used to structured procedures?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Records management in SharePoint 2010 &#8211; early thoughts by Denise Francis</title>
		<link>http://thinkingrecords.co.uk/2009/10/28/records-management-in-sharepoint-2010-some-early-thoughts/#comment-694</link>
		<dc:creator><![CDATA[Denise Francis]]></dc:creator>
		<pubDate>Fri, 26 Aug 2011 11:16:53 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingrecords.co.uk/?p=770#comment-694</guid>
		<description><![CDATA[I would like to see more on the idea of using metadata columns rather than folders.]]></description>
		<content:encoded><![CDATA[<p>I would like to see more on the idea of using metadata columns rather than folders.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Preserving e-mail &#8211; records management perspectives by clare cowling</title>
		<link>http://thinkingrecords.co.uk/2011/08/11/preserving-e-mail-records-management-perspectives/#comment-689</link>
		<dc:creator><![CDATA[clare cowling]]></dc:creator>
		<pubDate>Fri, 19 Aug 2011 11:25:12 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingrecords.co.uk/?p=1475#comment-689</guid>
		<description><![CDATA[James - great article as always.  I would say us recrods managers have more than just philosophical concerens about email management and archiving.  In all the discussions about managing in place, search tools etc business continuity seems to be ignored ie if I&#039;ve been working on something major and haven&#039;t bothered to save the business critical emails into the appropriate shared area (which takes - let&#039;s face it - about 10 seconds to do if you do it immediately, so why all the fuss about doing it?) and then swan off on holiday or break a leg no-one in my team will be able to locate those vital emails unless there&#039;s a crisis of such major propertions that the compliance team is allowed to search my account.  But even then they may not know what to search for - or my team may not even know that the crucial information exists in the first place.  So off everyone goes on expensive and time-consuming tangents, reinventing the wheel, losing the court case, getting fined by the ICO, running yet another project etc.  In the name of efficiency, isn&#039;t it time we stopped pandering to what the &quot;user&quot; (they aren&#039;t users, they are employees)wants to do and telling them that, as employees of our organisation, they must abide by our best practice rules and manage emails properly.  And tell them to get on with it! Clare

Clare]]></description>
		<content:encoded><![CDATA[<p>James &#8211; great article as always.  I would say us recrods managers have more than just philosophical concerens about email management and archiving.  In all the discussions about managing in place, search tools etc business continuity seems to be ignored ie if I&#8217;ve been working on something major and haven&#8217;t bothered to save the business critical emails into the appropriate shared area (which takes &#8211; let&#8217;s face it &#8211; about 10 seconds to do if you do it immediately, so why all the fuss about doing it?) and then swan off on holiday or break a leg no-one in my team will be able to locate those vital emails unless there&#8217;s a crisis of such major propertions that the compliance team is allowed to search my account.  But even then they may not know what to search for &#8211; or my team may not even know that the crucial information exists in the first place.  So off everyone goes on expensive and time-consuming tangents, reinventing the wheel, losing the court case, getting fined by the ICO, running yet another project etc.  In the name of efficiency, isn&#8217;t it time we stopped pandering to what the &#8220;user&#8221; (they aren&#8217;t users, they are employees)wants to do and telling them that, as employees of our organisation, they must abide by our best practice rules and manage emails properly.  And tell them to get on with it! Clare</p>
<p>Clare</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How MoReq 2010 differs from previous electronic records management (ERM) system specifications by Vaughan Spooner</title>
		<link>http://thinkingrecords.co.uk/2011/05/06/how-moreq-2010-differs-from-previous-electronic-records-management-erm-system-specifications/#comment-688</link>
		<dc:creator><![CDATA[Vaughan Spooner]]></dc:creator>
		<pubDate>Mon, 15 Aug 2011 12:38:46 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingrecords.co.uk/?p=1326#comment-688</guid>
		<description><![CDATA[A South African records process perspective!   

Firstly, the people involved in putting together the MoReq 2010 document must be commended for their efforts and obvious passion in what they do, not that I am forgetting about the folks who originally developed the MoReq spec.

I must be quite honest that 520 pages is daunting and I am not sure I have the energy to go through the document and give it the justice that it deserves.

Be that as it may, what I would like to put the table is that even though records managers face an ever incredibly difficult task, that at the end of the day they cannot address multiple system(s) issues unless they address the problems at a process level. Many of these problems are because businesses continue to go out and buy system after system that they think are a panacea for all their EDRM issues. The only way to understand the problem is to understand the process and then try and fit it to the system(s).

in addition, no matter whether a record is one item or format or an aggregation, you can only have one record (in a business context) just like you can only have one original - is a printed pdf of a signed purchase order the record, is the scanned copy of the hardcopy the record or is the transaction in an ERP the record? How many records or copies of the record do we want to manage? Simplistically I only have one birth certificate or passport or drivers licence - why would a business want multiple copies of a record or aggregation of a record?

Turning to the new MoReq 2010 I am not so convinced that line of business system vendors will incorporate electronic records management functionality into their systems - what is the benefit imperative to them? Just as is what is the bottom line benefit to a business forcing a vendor to be MoReq 2010 complaint? What was the benefit in the original MoReq 2 and if there was such how many BS vendors requested certification?

I fear that the world-wide community of records and information management practitioners is creating standards that are slowly becoming a rocket science monster that is going to destroy us. 

If I was to want to implement a records management &quot;system&quot; today where would I start - ISO15489; ISO/TR 15801; ICA-Req; GARP; SEDONA; et al! There is just too much to comprehend and I would strongly advocate a call to go back to basics.

Only once you have mastered the basics can you start looking at all the problems of aggregation, compound records, multiple business systems and EDRMS and EDMS and ECM and, not forgetting the 800lb gorilla in the room, SharePoint!

Finally, what I have promised myself, despite feelings of suicide may be a serious option, is that I intend over the next 6 months fighting my way through every single page of the 520 in MoReq 2010 with the hope that I can understand exactly what it is and what it is trying to achieve.]]></description>
		<content:encoded><![CDATA[<p>A South African records process perspective!   </p>
<p>Firstly, the people involved in putting together the MoReq 2010 document must be commended for their efforts and obvious passion in what they do, not that I am forgetting about the folks who originally developed the MoReq spec.</p>
<p>I must be quite honest that 520 pages is daunting and I am not sure I have the energy to go through the document and give it the justice that it deserves.</p>
<p>Be that as it may, what I would like to put the table is that even though records managers face an ever incredibly difficult task, that at the end of the day they cannot address multiple system(s) issues unless they address the problems at a process level. Many of these problems are because businesses continue to go out and buy system after system that they think are a panacea for all their EDRM issues. The only way to understand the problem is to understand the process and then try and fit it to the system(s).</p>
<p>in addition, no matter whether a record is one item or format or an aggregation, you can only have one record (in a business context) just like you can only have one original &#8211; is a printed pdf of a signed purchase order the record, is the scanned copy of the hardcopy the record or is the transaction in an ERP the record? How many records or copies of the record do we want to manage? Simplistically I only have one birth certificate or passport or drivers licence &#8211; why would a business want multiple copies of a record or aggregation of a record?</p>
<p>Turning to the new MoReq 2010 I am not so convinced that line of business system vendors will incorporate electronic records management functionality into their systems &#8211; what is the benefit imperative to them? Just as is what is the bottom line benefit to a business forcing a vendor to be MoReq 2010 complaint? What was the benefit in the original MoReq 2 and if there was such how many BS vendors requested certification?</p>
<p>I fear that the world-wide community of records and information management practitioners is creating standards that are slowly becoming a rocket science monster that is going to destroy us. </p>
<p>If I was to want to implement a records management &#8220;system&#8221; today where would I start &#8211; ISO15489; ISO/TR 15801; ICA-Req; GARP; SEDONA; et al! There is just too much to comprehend and I would strongly advocate a call to go back to basics.</p>
<p>Only once you have mastered the basics can you start looking at all the problems of aggregation, compound records, multiple business systems and EDRMS and EDMS and ECM and, not forgetting the 800lb gorilla in the room, SharePoint!</p>
<p>Finally, what I have promised myself, despite feelings of suicide may be a serious option, is that I intend over the next 6 months fighting my way through every single page of the 520 in MoReq 2010 with the hope that I can understand exactly what it is and what it is trying to achieve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Approaches to EDRMS in local government by James Lappin</title>
		<link>http://thinkingrecords.co.uk/2009/03/29/edrms-approaches-in-localgovernment/#comment-675</link>
		<dc:creator><![CDATA[James Lappin]]></dc:creator>
		<pubDate>Thu, 07 Jul 2011 10:45:31 +0000</pubDate>
		<guid isPermaLink="false">http://thinkingrecords.wordpress.com/?p=3#comment-675</guid>
		<description><![CDATA[Hi Jason,  the early adopters of SharePoint 2010 have tended to be organisations that didn&#039;t have an existing  SharePoint 2007 implementation.  Organisations that had a SharePoint 2007 implementations have not rushed to upgrade to SharePoint 2010 (because of the need for all the testing/buying new hardware/scheduling downtime etc).  This means the organisations with the most experience of SharePoint (and most capable of adapting it for records management) have not yet started using SharePoint 2010. The first service pack has just been issued for SharePoint 2010 so I suspect we will see most of the SharePoint 2007 implementations upgrade over the next 6 to 12 months.   There may be some good case studies of records management in SharePoint 2010 out there, but I haven&#039;t heard of any.]]></description>
		<content:encoded><![CDATA[<p>Hi Jason,  the early adopters of SharePoint 2010 have tended to be organisations that didn&#8217;t have an existing  SharePoint 2007 implementation.  Organisations that had a SharePoint 2007 implementations have not rushed to upgrade to SharePoint 2010 (because of the need for all the testing/buying new hardware/scheduling downtime etc).  This means the organisations with the most experience of SharePoint (and most capable of adapting it for records management) have not yet started using SharePoint 2010. The first service pack has just been issued for SharePoint 2010 so I suspect we will see most of the SharePoint 2007 implementations upgrade over the next 6 to 12 months.   There may be some good case studies of records management in SharePoint 2010 out there, but I haven&#8217;t heard of any.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

