<?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: Aggregation, it&#8217;s what you need</title>
	<atom:link href="http://openculture.collectionstrustblogs.org.uk/2009/01/22/aggregation-its-what-you-need/feed/" rel="self" type="application/rss+xml" />
	<link>http://openculture.collectionstrustblogs.org.uk/2009/01/22/aggregation-its-what-you-need/</link>
	<description></description>
	<pubDate>Mon, 06 Sep 2010 14:13:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: James Grimster</title>
		<link>http://openculture.collectionstrustblogs.org.uk/2009/01/22/aggregation-its-what-you-need/#comment-3705</link>
		<dc:creator>James Grimster</dc:creator>
		<pubDate>Thu, 22 Jan 2009 11:42:13 +0000</pubDate>
		<guid isPermaLink="false">http://openculture.collectionstrustblogs.org.uk/?p=48#comment-3705</guid>
		<description>Regarding scale - it should be noted that in attempting aggregation the data of the museums - and I'm thinking local, volunteer and history society - needs to be in state to interchange at the national level in the first place. Will each local data point have the resources to surface their data in a harvestable format? Or should consideration be made of regional or sub-regional mapping / pre-aggregation support and clustering projects at this point?</description>
		<content:encoded><![CDATA[<p>Regarding scale - it should be noted that in attempting aggregation the data of the museums - and I&#8217;m thinking local, volunteer and history society - needs to be in state to interchange at the national level in the first place. Will each local data point have the resources to surface their data in a harvestable format? Or should consideration be made of regional or sub-regional mapping / pre-aggregation support and clustering projects at this point?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
