<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Content Model, Best practices? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/content-model-best-practices/m-p/145515#M101688</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I think this is a great resource:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://ecmarchitect.com/images/articles/alfresco-content/content-article.pdf" rel="nofollow noopener noreferrer"&gt;http://ecmarchitect.com/images/articles/alfresco-content/content-article.pdf &lt;BR /&gt;&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;BR,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Alessandro&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Hi All,&lt;BR /&gt;&lt;BR /&gt;When developing a custom content model, what are best practices so far? I can either attach properties to content types, but also to aspects. I can automatically attach aspects to content with a content rule, based on a content type. But what are the consequences when i attach metadata/properties directly to the aspect instead of to the content type?&lt;BR /&gt;&lt;BR /&gt;Does anyone have experience with this decission?&lt;BR /&gt;&lt;BR /&gt;Thanks for your posts!&lt;BR /&gt;&lt;BR /&gt;Koen Bonnet&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 08 Oct 2007 06:50:48 GMT</pubDate>
    <dc:creator>alarocca</dc:creator>
    <dc:date>2007-10-08T06:50:48Z</dc:date>
    <item>
      <title>Content Model, Best practices?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/content-model-best-practices/m-p/145512#M101685</link>
      <description>Hi All,When developing a custom content model, what are best practices so far? I can either attach properties to content types, but also to aspects. I can automatically attach aspects to content with a content rule, based on a content type. But what are the consequences when i attach metadata/proper</description>
      <pubDate>Fri, 05 Oct 2007 08:01:42 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/content-model-best-practices/m-p/145512#M101685</guid>
      <dc:creator>kbonnet</dc:creator>
      <dc:date>2007-10-05T08:01:42Z</dc:date>
    </item>
    <item>
      <title>Re: Content Model, Best practices?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/content-model-best-practices/m-p/145513#M101686</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Hi All,&lt;BR /&gt;&lt;BR /&gt;When developing a custom content model, what are best practices so far? I can either attach properties to content types, but also to aspects. I can automatically attach aspects to content with a content rule, based on a content type. But what are the consequences when i attach metadata/properties directly to the aspect instead of to the content type?&lt;BR /&gt;&lt;BR /&gt;Does anyone have experience with this decission?&lt;BR /&gt;&lt;BR /&gt;Thanks for your posts!&lt;BR /&gt;&lt;BR /&gt;Koen Bonnet&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt;Personally I think you want to consider your types carefully.&amp;nbsp; In OO deep hierarchies can lead to issues and I think the same thing applies here.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Aspects can be added and removed and unless I have a very good reason to make a type, I'll tend to make an aspect (if we are talking about extensions of cm:content or cm:folder or other existing types.)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Good question BTW, I am curious to hear what others have to say.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Oct 2007 05:23:54 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/content-model-best-practices/m-p/145513#M101686</guid>
      <dc:creator>rdanner</dc:creator>
      <dc:date>2007-10-06T05:23:54Z</dc:date>
    </item>
    <item>
      <title>Re: Content Model, Best practices?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/content-model-best-practices/m-p/145514#M101687</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Well, my approach, not necesserally the correct one &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://connect.hyland.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;, is the following, I am trying to identify types like things which have strong evidence of existence like Invoice, Purchase Order, Purchase Requisition, Partner, Supplier… After that from these nouns I am creating types without any properties (sort of like marker interfaces) and I am trying to apply as much of properties through apects. Only if property is very much specific for a certain type I will apply it directly to the type. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kind regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Denis&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Oct 2007 21:33:20 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/content-model-best-practices/m-p/145514#M101687</guid>
      <dc:creator>dhalupa</dc:creator>
      <dc:date>2007-10-06T21:33:20Z</dc:date>
    </item>
    <item>
      <title>Re: Content Model, Best practices?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/content-model-best-practices/m-p/145515#M101688</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I think this is a great resource:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://ecmarchitect.com/images/articles/alfresco-content/content-article.pdf" rel="nofollow noopener noreferrer"&gt;http://ecmarchitect.com/images/articles/alfresco-content/content-article.pdf &lt;BR /&gt;&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;BR,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Alessandro&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Hi All,&lt;BR /&gt;&lt;BR /&gt;When developing a custom content model, what are best practices so far? I can either attach properties to content types, but also to aspects. I can automatically attach aspects to content with a content rule, based on a content type. But what are the consequences when i attach metadata/properties directly to the aspect instead of to the content type?&lt;BR /&gt;&lt;BR /&gt;Does anyone have experience with this decission?&lt;BR /&gt;&lt;BR /&gt;Thanks for your posts!&lt;BR /&gt;&lt;BR /&gt;Koen Bonnet&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Oct 2007 06:50:48 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/content-model-best-practices/m-p/145515#M101688</guid>
      <dc:creator>alarocca</dc:creator>
      <dc:date>2007-10-08T06:50:48Z</dc:date>
    </item>
  </channel>
</rss>

