<?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: A hybrid RDMBS/Alfresco model? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/a-hybrid-rdmbs-alfresco-model/m-p/249790#M202920</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;To answer my own question: The proposed hybrid approach was abandoned due to the complexity involved in splitting up data and it's metadata into different locations. Instead, we settled on a looser coupling between structured and unstructured data, ie. saving references to documents in structured data and vice versa for the Alfresco Repo. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This implies that there is a way to reference the structured data, so a generic service layer must be constructed on top of structured&amp;nbsp; data. An obvious choice would be a RESTful interface in order to integrate it&amp;nbsp; in the Surf client layer. The content model can be used to impose constraints on references. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So, there will be no using repository services directly on structured data. Too bad, but the advantage is that the dependency between systems is greatly reduced.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;best regards, Søren&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Mar 2011 19:57:48 GMT</pubDate>
    <dc:creator>eddie</dc:creator>
    <dc:date>2011-03-04T19:57:48Z</dc:date>
    <item>
      <title>A hybrid RDMBS/Alfresco model?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/a-hybrid-rdmbs-alfresco-model/m-p/249789#M202919</link>
      <description>Hi,For a while now, I have tried to get my head around a possible usage scenario for Alfresco, but not quite been able to articulate what my intentions were. This post inspired me to give it a shot.I have a RDMBS data model and a corresponding Java domain model mapped together using a Hibernate pers</description>
      <pubDate>Thu, 20 Jan 2011 09:16:01 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/a-hybrid-rdmbs-alfresco-model/m-p/249789#M202919</guid>
      <dc:creator>eddie</dc:creator>
      <dc:date>2011-01-20T09:16:01Z</dc:date>
    </item>
    <item>
      <title>Re: A hybrid RDMBS/Alfresco model?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/a-hybrid-rdmbs-alfresco-model/m-p/249790#M202920</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;To answer my own question: The proposed hybrid approach was abandoned due to the complexity involved in splitting up data and it's metadata into different locations. Instead, we settled on a looser coupling between structured and unstructured data, ie. saving references to documents in structured data and vice versa for the Alfresco Repo. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This implies that there is a way to reference the structured data, so a generic service layer must be constructed on top of structured&amp;nbsp; data. An obvious choice would be a RESTful interface in order to integrate it&amp;nbsp; in the Surf client layer. The content model can be used to impose constraints on references. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So, there will be no using repository services directly on structured data. Too bad, but the advantage is that the dependency between systems is greatly reduced.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;best regards, Søren&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 19:57:48 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/a-hybrid-rdmbs-alfresco-model/m-p/249790#M202920</guid>
      <dc:creator>eddie</dc:creator>
      <dc:date>2011-03-04T19:57:48Z</dc:date>
    </item>
  </channel>
</rss>

