Hi Nils, > - support an extendible data model (plugins can add fields / > relationships to exisiting objects). From what I've read this is supported.
Everything is dynamic, you can create new nodes/relationships/relationship types and add properties at will. A node can have any combination of properties and relationships attached. > - support query of items by properties and by relationships of other > objects. For example: return all email messages sent to or received from > a particular user, which are part of a collection "work". Yes this can be achieved in a number of ways. Depending on requirements you can use different layouts. Most straight forward would be to have node for each user and email then relationships RECEIVED & SENT. Also a node that symbolizes the "work" collection and a relationship type PART_OF. > > A part I am struggeling with in the design of the app, is that the UI > should support viewing of very large collections, for example all email > messages in "work" collection. These will have to be sortable by > different fields, in case of a mail message even sorting by the name of > the contact (which needs to follow a relationship). I don't really know > how to use Neo4j (or another persistence mechanism, or another layer on > top of Neo4j) to implement such functionality. > This can either be solved by reading in the full collection (using a traverser) then sort it or keep the items sorted in the node space (using linked lists like Timeline utility in index-util component). Regards -Johan _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
