<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Digital Pulp Blog &#187; development</title>
	<atom:link href="http://blog.digitalpulp.com/tag/development/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.digitalpulp.com</link>
	<description>Great Things Happen</description>
	<lastBuildDate>Tue, 15 May 2012 19:25:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Making of a Content Aggregation Engine</title>
		<link>http://blog.digitalpulp.com/2009/10/16/the-making-of-a-content-aggregation-engine/</link>
		<comments>http://blog.digitalpulp.com/2009/10/16/the-making-of-a-content-aggregation-engine/#comments</comments>
		<pubDate>Fri, 16 Oct 2009 18:15:31 +0000</pubDate>
		<dc:creator>jblecher</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[development]]></category>

		<guid isPermaLink="false">http://www.digitalpulp.com/blog/?p=383</guid>
		<description><![CDATA[Traditional Content Management Systems assume that the content you are managing lives within the CMS. What if the content that makes up your website is being syndicated from many disparate sources (RSS, custom databases, etc.) as well as arriving via manual content entry? Well, as long as they were used in different ways, it&#8217;s not [...]]]></description>
			<content:encoded><![CDATA[<p>Traditional Content Management Systems assume that the content you are managing lives within the CMS. What if the content that makes up your website is being syndicated from many disparate sources (RSS, custom databases, etc.) as well as arriving via manual content entry? Well, as long as they were used in different ways, it&#8217;s not a big deal. But what if every item–every article on the site–was to be managed and displayed the <em>same</em> way, no matter what the source? Those and other challenging questions were what we faced when we embarked on building the <a title="Communications of the ACM" href="http://cacm.acm.org" target="_blank">new Communications of the ACM website</a>.</p>
<p>The DP team conceived and implemented a custom-built Content Aggregation Engine (CAE) to pull in, or ingest, content from all of the previously mentioned disparate sources and unify it into a single data model for publishing on the site. The hours dedicated to coding were significantly less than the time spent defining the business rules, testing the application and making the product rock solid. The project required everything from broad strategic thinking to very detailed execution. </p>
<p>It&#8217;s a challenge to give a recognized industry leader the ability to supercharge their flagship publication. The Content Aggregation Engine was our way of providing even more value to their prestigous membership.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.digitalpulp.com/2009/10/16/the-making-of-a-content-aggregation-engine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

