https://connect.hyland.com/t5/nuxeo-forum/physical-document-hierarchy-layouting/m-p/315256#M2257 <P>Thanks, makes perfect sense!</P> Fri, 03 Feb 2012 13:46:53 GMT scerazy_ 2012-02-03T13:46:53Z https://connect.hyland.com/t5/nuxeo-forum/physical-document-hierarchy-layouting/m-p/315254#M2255 <P>It should be as logical as:</P> <P><A href="http://doc.nuxeo.com/display/DAMDOC/Nuxeo+DAM+Core" target="test_blank">http://doc.nuxeo.com/display/DAMDOC/Nuxeo+DAM+Core</A></P> <P>But I see no such structure in my install (as per attachment)</P> <P>Seb<IMG src="https://connect.hyland.com/upfiles/nuxeo.PNG" alt="alt text" /></P> Fri, 03 Feb 2012 12:03:41 GMT https://connect.hyland.com/t5/nuxeo-forum/physical-document-hierarchy-layouting/m-p/315254#M2255 scerazy_ 2012-02-03T12:03:41Z https://connect.hyland.com/t5/nuxeo-forum/physical-document-hierarchy-layouting/m-p/315255#M2256 <P>The documents are stored on disk (in the file system) using a simple hash. The object id is used to create what you see on disk. So an object with the id f5da36d9-bcba-421e-9932-317b3ae2ed4e will be hashed to the folder f5/da (assuming you have the default # of folder levels of 2). The object id is stored in the relational database and used to find/access the object. This approach is similar to almost every scalable document management/archive system I have ever seen. It is a highly scalable, fast architecture and allows for single object store (meaning if two binaries map to the same hash and are the same file then only one copy is stored).</P> Fri, 03 Feb 2012 13:21:38 GMT https://connect.hyland.com/t5/nuxeo-forum/physical-document-hierarchy-layouting/m-p/315255#M2256 bruce_Grant 2012-02-03T13:21:38Z https://connect.hyland.com/t5/nuxeo-forum/physical-document-hierarchy-layouting/m-p/315256#M2257 <P>Thanks, makes perfect sense!</P> Fri, 03 Feb 2012 13:46:53 GMT https://connect.hyland.com/t5/nuxeo-forum/physical-document-hierarchy-layouting/m-p/315256#M2257 scerazy_ 2012-02-03T13:46:53Z