<?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 for kelly andrew heard</title>
	<atom:link href="http://blog.kellyheard.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.kellyheard.com</link>
	<description></description>
	<lastBuildDate>Fri, 25 Jun 2010 15:51:58 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on New to Commerce Server 2009 by Lee</title>
		<link>http://blog.kellyheard.com/newadditions/comment-page-1/#comment-1634</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Fri, 25 Jun 2010 15:51:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=314#comment-1634</guid>
		<description>Just noticed the code didn&#039;t append correctly! I&#039;ve posted the answer on:
http://social.msdn.microsoft.com/Forums/en-US/commserver2009/thread/d992854b-80df-4b58-b4ae-4dba2ff014cc</description>
		<content:encoded><![CDATA[<p>Just noticed the code didn&#8217;t append correctly! I&#8217;ve posted the answer on:<br />
<a href="http://social.msdn.microsoft.com/Forums/en-US/commserver2009/thread/d992854b-80df-4b58-b4ae-4dba2ff014cc" rel="nofollow">http://social.msdn.microsoft.com/Forums/en-US/commserver2009/thread/d992854b-80df-4b58-b4ae-4dba2ff014cc</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New to Commerce Server 2009 by Lee</title>
		<link>http://blog.kellyheard.com/newadditions/comment-page-1/#comment-1633</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Fri, 25 Jun 2010 15:50:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=314#comment-1633</guid>
		<description>After several people also asking me &quot;Can the left-hand category navigation throughout the site can be restored&quot; and no real answers anywhere - I did some tinkering and fixed it using this:

Insert the following code at the bottom of the category.aspx (or any other) template:


    
    
     
  
  
                                
    
</description>
		<content:encoded><![CDATA[<p>After several people also asking me &#8220;Can the left-hand category navigation throughout the site can be restored&#8221; and no real answers anywhere &#8211; I did some tinkering and fixed it using this:</p>
<p>Insert the following code at the bottom of the category.aspx (or any other) template:</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extensibility or Hack? by Stanislava</title>
		<link>http://blog.kellyheard.com/extensibility-or-hack/comment-page-1/#comment-949</link>
		<dc:creator>Stanislava</dc:creator>
		<pubDate>Tue, 12 Jan 2010 08:59:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=398#comment-949</guid>
		<description>&lt;blockquote cite=&quot;#commentbody-38&quot;&gt;
&lt;strong&gt;&lt;a href=&quot;#comment-38&quot; rel=&quot;nofollow&quot;&gt;Colin Coller&lt;/a&gt; :&lt;/strong&gt;I have numerous objections to the practice, some philosophical, others experiential. :)
1. It puts additional load on something that you want to be really fast.
2. It puts additional load on something that’s relatively expensive to license on a per-processor basis.
3. It makes it more difficult to partition and distribute your data and your processing.
4. It makes it more difficult to size and tune your caches.
5. It causes you to think about data in terms of the catalog API and the catalog structures, which is good for some things and absolutely terrible for many other things.
6. It makes it easier to make bad decisions about how and where you manage your content.
7. It makes it more likely that you’ll have to extend and maintain your own version of the out-of-the-box tools.
If I were architecting a medium or larger e-commerce website on Commerce Server, I’d have serious reservations about storing non-product data in the catalog. I’d head toward other pre-packaged or custom components and stores, and only come back to the catalog if absolutely necessary.
My $0.02,
Colin&lt;/blockquote&gt;

Hi,
In fact I have such systems with content implemented in Commerce server and such with content in Share Point and CMS. Commerce only systems are faster. Relation between product and content in Commerce only system is easier and faster, and such relation is always required, because the content is about the products. Retrieving of the contend related to product and products related to content is easier and faster and Commerce only systems.
You have objections, but you do not provide alternative? What is you suggestion for Content mamagent system with Commerce server?</description>
		<content:encoded><![CDATA[<blockquote cite="#commentbody-38"><p>
<strong><a href="#comment-38" rel="nofollow">Colin Coller</a> :</strong>I have numerous objections to the practice, some philosophical, others experiential. :)<br />
1. It puts additional load on something that you want to be really fast.<br />
2. It puts additional load on something that’s relatively expensive to license on a per-processor basis.<br />
3. It makes it more difficult to partition and distribute your data and your processing.<br />
4. It makes it more difficult to size and tune your caches.<br />
5. It causes you to think about data in terms of the catalog API and the catalog structures, which is good for some things and absolutely terrible for many other things.<br />
6. It makes it easier to make bad decisions about how and where you manage your content.<br />
7. It makes it more likely that you’ll have to extend and maintain your own version of the out-of-the-box tools.<br />
If I were architecting a medium or larger e-commerce website on Commerce Server, I’d have serious reservations about storing non-product data in the catalog. I’d head toward other pre-packaged or custom components and stores, and only come back to the catalog if absolutely necessary.<br />
My $0.02,<br />
Colin</p></blockquote>
<p>Hi,<br />
In fact I have such systems with content implemented in Commerce server and such with content in Share Point and CMS. Commerce only systems are faster. Relation between product and content in Commerce only system is easier and faster, and such relation is always required, because the content is about the products. Retrieving of the contend related to product and products related to content is easier and faster and Commerce only systems.<br />
You have objections, but you do not provide alternative? What is you suggestion for Content mamagent system with Commerce server?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extensibility or Hack? by Kelly</title>
		<link>http://blog.kellyheard.com/extensibility-or-hack/comment-page-1/#comment-193</link>
		<dc:creator>Kelly</dc:creator>
		<pubDate>Mon, 14 Sep 2009 13:05:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=398#comment-193</guid>
		<description>This type of data is a little more challenging to store in the catalog as it is always changing with customers.  You don&#039;t want to be creating one-off products every time you get a new customer.  There are probably a few ways you could do this, but one way would be to create some additional fields at the order level (form and line item) and persist the customer specific data when the item gets added to the basket.  This data will then get persisted to your completed Purchase Order.  Another way might be, if the customer data you&#039;re capturing is similar enough you could create a profile for the customer and store the data in some custom profile attributes.  As for calculating the premiums, this will involve some custom logic regardless of how you do it.

Another way might be to create custom properties on your insurance products in the catalog.  These custom properties would only serve as a sort of &quot;list&quot; of the type of details you need to capture.  Each new property could also have an associated &quot;cost&quot; as well that could be used to calc the total premium.

Hope this helps a little!</description>
		<content:encoded><![CDATA[<p>This type of data is a little more challenging to store in the catalog as it is always changing with customers.  You don&#8217;t want to be creating one-off products every time you get a new customer.  There are probably a few ways you could do this, but one way would be to create some additional fields at the order level (form and line item) and persist the customer specific data when the item gets added to the basket.  This data will then get persisted to your completed Purchase Order.  Another way might be, if the customer data you&#8217;re capturing is similar enough you could create a profile for the customer and store the data in some custom profile attributes.  As for calculating the premiums, this will involve some custom logic regardless of how you do it.</p>
<p>Another way might be to create custom properties on your insurance products in the catalog.  These custom properties would only serve as a sort of &#8220;list&#8221; of the type of details you need to capture.  Each new property could also have an associated &#8220;cost&#8221; as well that could be used to calc the total premium.</p>
<p>Hope this helps a little!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extensibility or Hack? by rishi girdhar</title>
		<link>http://blog.kellyheard.com/extensibility-or-hack/comment-page-1/#comment-191</link>
		<dc:creator>rishi girdhar</dc:creator>
		<pubDate>Mon, 14 Sep 2009 12:28:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=398#comment-191</guid>
		<description>Hi Kelly,
I am trying to implement for an insurance firm where we need to store non-product data such as 
Proposer Details - User name, address, spouse name, age etc
and Product specific details like incase of travel insurance
Travel dates, source and destination,etc
based on these  inputs I need to calculate the premium also.

What do you suggest for it?</description>
		<content:encoded><![CDATA[<p>Hi Kelly,<br />
I am trying to implement for an insurance firm where we need to store non-product data such as<br />
Proposer Details &#8211; User name, address, spouse name, age etc<br />
and Product specific details like incase of travel insurance<br />
Travel dates, source and destination,etc<br />
based on these  inputs I need to calculate the premium also.</p>
<p>What do you suggest for it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New to Commerce Server 2009 by Kelly</title>
		<link>http://blog.kellyheard.com/newadditions/comment-page-1/#comment-120</link>
		<dc:creator>Kelly</dc:creator>
		<pubDate>Wed, 19 Aug 2009 13:33:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=314#comment-120</guid>
		<description>My apologies for not replying to this sooner.  The easiest way to do this is to use SharePoint designer (which is now free from Microsoft).  Most of the content you&#039;re looking to change would be right on the masterpage of the template pack&#039;s theme.</description>
		<content:encoded><![CDATA[<p>My apologies for not replying to this sooner.  The easiest way to do this is to use SharePoint designer (which is now free from Microsoft).  Most of the content you&#8217;re looking to change would be right on the masterpage of the template pack&#8217;s theme.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New to Commerce Server 2009 by Cmyweb</title>
		<link>http://blog.kellyheard.com/newadditions/comment-page-1/#comment-66</link>
		<dc:creator>Cmyweb</dc:creator>
		<pubDate>Sat, 27 Jun 2009 03:00:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=314#comment-66</guid>
		<description>I&#039;ve deployed the template pack.  It was pretty straightforward and much better looking.  What&#039;s the best/quickest way to update the basics - logo, contact us, etc.  ?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve deployed the template pack.  It was pretty straightforward and much better looking.  What&#8217;s the best/quickest way to update the basics &#8211; logo, contact us, etc.  ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extensibility or Hack? by Colin Coller</title>
		<link>http://blog.kellyheard.com/extensibility-or-hack/comment-page-1/#comment-38</link>
		<dc:creator>Colin Coller</dc:creator>
		<pubDate>Thu, 21 May 2009 19:22:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=398#comment-38</guid>
		<description>I have numerous objections to the practice, some philosophical, others experiential. :)

1. It puts additional load on something that you want to be really fast.

2. It puts additional load on something that&#039;s relatively expensive to license on a per-processor basis.

3. It makes it more difficult to partition and distribute your data and your processing.

4. It makes it more difficult to size and tune your caches.

5. It causes you to think about data in terms of the catalog API and the catalog structures, which is good for some things and absolutely terrible for many other things.

6. It makes it easier to make bad decisions about how and where you manage your content.

7. It makes it more likely that you&#039;ll have to extend and maintain your own version of the out-of-the-box tools.

If I were architecting a medium or larger e-commerce website on Commerce Server, I&#039;d have serious reservations about storing non-product data in the catalog.  I&#039;d head toward other pre-packaged or custom components and stores, and only come back to the catalog if absolutely necessary.

My $0.02,

Colin</description>
		<content:encoded><![CDATA[<p>I have numerous objections to the practice, some philosophical, others experiential. :)</p>
<p>1. It puts additional load on something that you want to be really fast.</p>
<p>2. It puts additional load on something that&#8217;s relatively expensive to license on a per-processor basis.</p>
<p>3. It makes it more difficult to partition and distribute your data and your processing.</p>
<p>4. It makes it more difficult to size and tune your caches.</p>
<p>5. It causes you to think about data in terms of the catalog API and the catalog structures, which is good for some things and absolutely terrible for many other things.</p>
<p>6. It makes it easier to make bad decisions about how and where you manage your content.</p>
<p>7. It makes it more likely that you&#8217;ll have to extend and maintain your own version of the out-of-the-box tools.</p>
<p>If I were architecting a medium or larger e-commerce website on Commerce Server, I&#8217;d have serious reservations about storing non-product data in the catalog.  I&#8217;d head toward other pre-packaged or custom components and stores, and only come back to the catalog if absolutely necessary.</p>
<p>My $0.02,</p>
<p>Colin</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New CS09 Sites &amp; Cache Refresh by mzzm</title>
		<link>http://blog.kellyheard.com/cs09cacherefresh/comment-page-1/#comment-34</link>
		<dc:creator>mzzm</dc:creator>
		<pubDate>Sun, 17 May 2009 02:50:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=351#comment-34</guid>
		<description>I&#039;ve run into this issue many times and continue to used the url&#039;s as you&#039;ve explained. There has got to be a better way to add the applications after the face, yet I haven&#039;t dug into it enought. Anyone done this successfully?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve run into this issue many times and continue to used the url&#8217;s as you&#8217;ve explained. There has got to be a better way to add the applications after the face, yet I haven&#8217;t dug into it enought. Anyone done this successfully?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SXSW Begins by South By &#171; Brandon Hubbard</title>
		<link>http://blog.kellyheard.com/sxswbegins/comment-page-1/#comment-14</link>
		<dc:creator>South By &#171; Brandon Hubbard</dc:creator>
		<pubDate>Wed, 22 Apr 2009 01:54:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=157#comment-14</guid>
		<description>[...] had already seared my eyes on MySpace and plucked almost random strings from my iTunes library when Kelly and I met at Bridgehead to compare list.  He&#8217;d also done research, maybe using more sound [...]</description>
		<content:encoded><![CDATA[<p>[...] had already seared my eyes on MySpace and plucked almost random strings from my iTunes library when Kelly and I met at Bridgehead to compare list.  He&#8217;d also done research, maybe using more sound [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
