<?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 Philosophical modeling question - types/aspects/future migrations in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/philosophical-modeling-question-types-aspects-future-migrations/m-p/279704#M232834</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We are attempting to avoid any duplication of data in our aspects.&amp;nbsp; So we have a lot of small aspects (10-12) and then a few (7-8) types that use various combinations of the aspects.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Here's an example:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;BaseType - mandatory aspect BaseAspect&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Types 1,2,3 all are subtypes of BaseType&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Type1 has mandatory aspects: aspectA, aspectB, aspectC, aspectD&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Type2 has mandatory aspects: aspectA, aspectD&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Type3 has mandatory aspects:&amp;nbsp; aspectB, aspectC&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This seems pretty brilliant to me :-), but my boss keeps freaking me out saying…"then one day we'll migrate to different types" or bring in data from several repos and migrate the aspect data into new aspects…&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;From what I read declaring a type is an irrevocable act.&amp;nbsp;&amp;nbsp; If you change your mind about the document's type you'd have to upload it again to change it?&amp;nbsp; Or is there some way to clone the document and re-type it?&amp;nbsp; And then maybe have a script transfer some of the metadata into the new aspects?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Please advise…I see people saying "your model is WRONG if you have to change it", but if I could tell the future I'd buy a lottery ticket.&amp;nbsp; Of course, things will change, so we have to make some kind of plan.&amp;nbsp; If I were to give up types entirely could I group the aspects using some other means?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Appreciate any advice from folks who actually use Alfresco in a large company with lots of data!&amp;nbsp;&amp;nbsp; Based on this forum I'm not convinced there are that many of those people - but maybe their code always works and they don't need the forum :-).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 May 2015 19:15:53 GMT</pubDate>
    <dc:creator>ddelapasse</dc:creator>
    <dc:date>2015-05-21T19:15:53Z</dc:date>
    <item>
      <title>Philosophical modeling question - types/aspects/future migrations</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/philosophical-modeling-question-types-aspects-future-migrations/m-p/279704#M232834</link>
      <description>We are attempting to avoid any duplication of data in our aspects.&amp;nbsp; So we have a lot of small aspects (10-12) and then a few (7-8) types that use various combinations of the aspects.Here's an example:BaseType - mandatory aspect BaseAspectTypes 1,2,3 all are subtypes of BaseTypeType1 has mandatory as</description>
      <pubDate>Thu, 21 May 2015 19:15:53 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/philosophical-modeling-question-types-aspects-future-migrations/m-p/279704#M232834</guid>
      <dc:creator>ddelapasse</dc:creator>
      <dc:date>2015-05-21T19:15:53Z</dc:date>
    </item>
    <item>
      <title>Re: Philosophical modeling question - types/aspects/future migrations</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/philosophical-modeling-question-types-aspects-future-migrations/m-p/279705#M232835</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Looks fine to me.&amp;nbsp;&amp;nbsp; But obviously you know your domain.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If in future you do need to migrate to different types then that is a data migration exercise.&amp;nbsp;&amp;nbsp; And can't be avoided.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; But if your data model is correct then you shouln't really have a big problem.&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If your data models are wildly different then that will be harder.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;One final comment, consider using optional aspects as well as mandatory ones.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 May 2015 21:16:06 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/philosophical-modeling-question-types-aspects-future-migrations/m-p/279705#M232835</guid>
      <dc:creator>mrogers</dc:creator>
      <dc:date>2015-05-21T21:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: Philosophical modeling question - types/aspects/future migrations</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/philosophical-modeling-question-types-aspects-future-migrations/m-p/279706#M232836</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I don't see how migration is possible.&amp;nbsp; If I decide that Type2 should be split into new types: Type5 &amp;amp; Type6, is that possible without downloading all the data and reloading it?&amp;nbsp; &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 May 2015 12:30:17 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/philosophical-modeling-question-types-aspects-future-migrations/m-p/279706#M232836</guid>
      <dc:creator>ddelapasse</dc:creator>
      <dc:date>2015-05-22T12:30:17Z</dc:date>
    </item>
  </channel>
</rss>

