11-15-2013 04:42 PM
Hi folks, is there a best-practice for modeling a reference from one document to another? For example is it a good or bad idea to have one document's schema have a "String" field that will contain a Nuxeo UID to another document? I'm aware of Relations in Nuxeo, but i think I need some additional features beyond just a relationship. Specifically, I want to keep multiple references to a document and preserve the order of the linkage.
11-20-2013 11:08 AM
Don't know if it's a best practice or not but I have used a similar approach in a number of applications to model more complex relationships (and to minimize relation service overheads) including preservation of the order and hierarchy of links. In my case I haven't used UID as the key, instead I have used separate field with uniquely generated value (with some content-specific meaning). The approach works very well.
11-20-2013 11:08 AM
Don't know if it's a best practice or not but I have used a similar approach in a number of applications to model more complex relationships (and to minimize relation service overheads) including preservation of the order and hierarchy of links. In my case I haven't used UID as the key, instead I have used separate field with uniquely generated value (with some content-specific meaning). The approach works very well.
11-20-2013 12:54 PM
thank you very much! this is just the kind of technique idea I was hoping to hear
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.