Modeling a multilevel index in neoj4

pehrlich says:

This is interesting, I like it. I imagine if you wanted to query for the next 20 days, rather than from a date range, you could do this:<br /><br />START root=node:node_auto_index(name = &#39;Root&#39;)<br />MATCH <br /> commonPath=root-[:`2011`]-&gt;()-[:`01`]-&gt;()-[:`01`]-&gt;,<br /> valuePath=startLeaf-[:NEXT*0..]-&gt;middle-[:NEXT*0..20]-&gt;endLeaf,<br /> values=middle-[:VALUE]-&gt;

bww00 says:

Thanks!<br />I have a problem for a clinic setting, where there are multiple patients with multiple events per interval (say 1 – 15 minutes), and multiple state changes for an event. Would it be better to have tree for each patient, or a common tree for all ? What impact would the granularity of the time be, down to the minute or second ?<br /><br />Regards,<br />Bryan Webb

Peter Neubauer says:

@bww00 depends a bit on the amount of data. How big is the total number of events going to be?

panisson says:

Hello Peter, thank you for this nice example.<br />We are trying to use this approach to represent a timeline of frames, and a graph on each frame. However, we are using the Neo4j <a href="http://api.neo4j.org/current/org/neo4j/graphdb/Node.html#createRelationshipTo(org.neo4j.graphdb.Node,%20org.neo4j.graphdb.RelationshipType)&quot; rel="nofollow">createRelationshipTo</a> method to create the

André Panisson says:

Thanks Peter, I was not aware of the availability of the DynamicRelationshipsType class.

Simon Hallé says:

Hi Peter, thanks for the example, looks pretty good! Although I haven&#39;t done much tests with Lucene, I was wondering why you noted that using such index would be &quot;very costly&quot; to do the sorting? In my situation, I need to implement a filter that returns all Nodes within a date range. Nodes are tagged with a start and optional end date (node properties). I noticed that

Unknown says:

Thanks Peter, for a nice explanation. I&#39;m seriously looking at the graph databases now for our reporting suite – I have tried to model the time series data as you had suggested but since it goes down up to the seconds level I&#39;m quite conscious about performance. I have devices sending the data so I can append to the timeline graph with seconds precision. These devices are tied to a client

flip101 says:

@bww00 Can you share your data model? I would like to make a similar setup. I have the same question about: Where to introduce several &quot;users&quot; into this model. Have you gotten any test results back?<br /><br />@Unknown I don&#39;t think you have to specify the frames to the smallest unit of time. You can have an hour as smallest frame and then attach all those events to this hour. But