topic types and aspects: usability and scalability in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/types-and-aspects-usability-and-scalability/m-p/274414#M227544 <HTML><HEAD></HEAD><BODY><SPAN>I have been reading quite a bit (including some of Jeff's work – there's a lot of it, so I certainly can't claim to have seen it all!), and have looked through "Professional Alfresco…"</SPAN><BR /><BR /><SPAN>I see content modeling addressed to a moderate degree, but nothing really "deep" so far.&nbsp; Forgive me for dumping these related questions into one post…but at least they're related <img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://connect.hyland.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" />.</SPAN><BR /><BR /><SPAN>I understand how aspects cut-across the type hierarchy (very cool, and remember multiple inheritance from my C++ days - good OO concept), but am unclear whether they are "worth it" from a practical standpoint when it comes to searching and inheritance.&nbsp; </SPAN><BR /><BR /><SPAN>For example, it appears that CMIS code would require far more complex queires to join multiple aspects to a type in order to find objects that are leveraging multiple aspects instead of old-school type-defined properties.&nbsp; </SPAN><BR /><SPAN>I haven't looked too closely, but does the same hold for using "Advanced Search" to query a custom type?&nbsp; I assume that aspects' properties would not be offered for search by default, making the user experience and/or the customization level (of the search services) more difficult?</SPAN><BR /><BR /><SPAN>What about automatically propogating values from parent (folder) to child (document/content subtype)?&nbsp; Does this happen automatically or can it be easily coded if we're talking about the same aspect applied to both the parent and child?&nbsp; The folder-to-child property synchronization (down only in my current case) is a great example of where an aspect should work well (define the aspect and apply it - probably as a mandatory aspect - to both the folder subtype and the document subtype).&nbsp; But am I shooting myself in the foot because I have to do a lot of extra work to make all that easily searchable for the end-users?</SPAN><BR /><BR /><SPAN>Last (for now) but not least (for now <img id="smileywink" class="emoticon emoticon-smileywink" src="https://connect.hyland.com/i/smilies/16x16_smiley-wink.png" alt="Smiley Wink" title="Smiley Wink" /> ), it's unclear how aspects and types scale properly.&nbsp; Is it a lot more db joins and complex queries for the Alfresco repository service to put together document-objects with a few aspects also applied (almost always applied – just varying combinations of them) for display/query versus just having a "thicker" set of types (but also more copy &amp; paste on the model design, because identical properties are defined on a folder tree as the cm:content tree)?&nbsp; Are the indexes combined or outer-joined or something?</SPAN><BR /><BR /><SPAN>Thanks in advance for any help.&nbsp; Maybe some of this is covered somewhere that I haven't found it yet.</SPAN><BR /><BR /><SPAN>-AJ</SPAN></BODY></HTML> Fri, 18 May 2012 13:29:47 GMT aweber1nj 2012-05-18T13:29:47Z types and aspects: usability and scalability https://connect.hyland.com/t5/alfresco-archive/types-and-aspects-usability-and-scalability/m-p/274414#M227544 I have been reading quite a bit (including some of Jeff's work – there's a lot of it, so I certainly can't claim to have seen it all!), and have looked through "Professional Alfresco…"I see content modeling addressed to a moderate degree, but nothing really "deep" so far.&nbsp; Forgive me for dumping the Fri, 18 May 2012 13:29:47 GMT https://connect.hyland.com/t5/alfresco-archive/types-and-aspects-usability-and-scalability/m-p/274414#M227544 aweber1nj 2012-05-18T13:29:47Z Re: types and aspects: usability and scalability https://connect.hyland.com/t5/alfresco-archive/types-and-aspects-usability-and-scalability/m-p/274415#M227545 <HTML><HEAD></HEAD><BODY><SPAN>Where to start?&nbsp;&nbsp; You ask a lot of questions. <img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://connect.hyland.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /> </SPAN><BR /><BR /><SPAN>I don't think there's a lot to choose between types and aspects when it comes to performance, the real differentiator should be how they relate to your business objects.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If you find that your model "just works" then that's a good sign,&nbsp; equally if there's lots of difficulty and work-arounds that's a warning that something is not quite right.</SPAN><BR /><BR /><SPAN>Values are not copied from parent to child, except for a few application special cases.&nbsp; (Can't think of any off the top of my head,&nbsp; but I've done it a few times.)&nbsp; Equally there are a few special cases where you can join data at the database level.</SPAN><BR /><BR /><SPAN>I understand from Andy that SOLR should allow FTS to support arbitary join quireies,&nbsp; however last I heard it was not quite on the roadmap.</SPAN></BODY></HTML> Fri, 18 May 2012 14:06:40 GMT https://connect.hyland.com/t5/alfresco-archive/types-and-aspects-usability-and-scalability/m-p/274415#M227545 mrogers 2012-05-18T14:06:40Z