<?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"
	>
<channel>
	<title>Comments on: Code of Practice for Cultural Collections Management</title>
	<atom:link href="http://openculture.collectionstrustblogs.org.uk/2009/03/05/code-of-practice-for-cultural-collections-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://openculture.collectionstrustblogs.org.uk/2009/03/05/code-of-practice-for-cultural-collections-management/</link>
	<description></description>
	<pubDate>Thu, 29 Jul 2010 20:27:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Graham Bowen</title>
		<link>http://openculture.collectionstrustblogs.org.uk/2009/03/05/code-of-practice-for-cultural-collections-management/#comment-3786</link>
		<dc:creator>Graham Bowen</dc:creator>
		<pubDate>Thu, 07 May 2009 11:00:40 +0000</pubDate>
		<guid isPermaLink="false">http://openculture.collectionstrustblogs.org.uk/?p=66#comment-3786</guid>
		<description>One view I have with regard to holistic management of cultural collections is the development of an a easy to use collections records database which complies to libraries museums and archives holdings. A once and for all 'not broke so don't need fixing' this will enable confidence in software futureproofing issues. The products on the market are to varied and non-compatible therefore reduces effective record inforamtion sharing. 

The other view is what are the likely costs with regard to impacts of a new code to be successfully implemented. For example 'what are the next generation of services' and what are their vehicles of delivery'.</description>
		<content:encoded><![CDATA[<p>One view I have with regard to holistic management of cultural collections is the development of an a easy to use collections records database which complies to libraries museums and archives holdings. A once and for all &#8216;not broke so don&#8217;t need fixing&#8217; this will enable confidence in software futureproofing issues. The products on the market are to varied and non-compatible therefore reduces effective record inforamtion sharing. </p>
<p>The other view is what are the likely costs with regard to impacts of a new code to be successfully implemented. For example &#8216;what are the next generation of services&#8217; and what are their vehicles of delivery&#8217;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
