Sure, no problem. The design is really quite simple.
DataResources are meant to be just that, data resources... kind of
like a file in a file system. Just like a file, a data resources can
only be in one group and a group can only be in one other group (ie it
is a real tree). This allows for consistent organization with "a place
for everything and everything in its place", and just one place.
In practical applications DataResources should never be used alone,
they should always be used through one or more Content records.
Content records are much more flexible in their structure and can
support lists, trees, and graphs.
If you really want to organize DataResources, then the way to do it is
through Content records. A single DataResource record can be referred
to by many Content records, and those Content records can be part of
all sorts of different Content structures: documents, lists, trees,
graphs, etc.
-David
On Jan 21, 2009, at 8:10 PM, Hans Bakker wrote:
> I am looking at a way to manage content with categories. I get now
> plenty of documents via the emailattachements in the system and it
> needs
> some organization
>
> There is a way to manage DataResources with categories, however with
> the
> limitation that a dataResource can only be in one datacategory.
>
> David, you were the original designer of this data model, do you have
> any thoughts about this?
>
> --
> Antwebsystems.com: Quality OFBiz services for competitive prices
>
Locked
