I've been experimenting with Neo4J to run event analytics on page view data, and I've been able to do some pathing analysis that's practically impossible with SQL. I've written a few blogs on the Snowplow Analytics website. In the first I define a graph structure that allows for sequencing of page view events. in the second, I walk through how I got data into Neo4J, so it's probably not very interesting for people who are experienced with Neo4J! In the third, I actually perform the analysis.
I'm very inexperienced with Neo4J so I'd love it if any of you have ideas for new things to try, or ways to improve the queries I've already written, particularly in the last post! I'd especially love it if you know of a way to check a NODES(path) collection for nodes with duplicate properties (in my case, the URL that the View nodes point to. There's also an edge from the View node to the Page node, and those pages are unique, so alternatively we could check in any nodes in NODES(path) have edges to the same Page node...) 1. http://snowplowanalytics.com/blog/2014/07/28/explorations-in-analyzing-web-event-data-in-graph-databases/ 2. http://snowplowanalytics.com/blog/2014/07/30/loading-snowplow-web-event-data-into-graph-databases-for-pathing-analysis/ 3. http://snowplowanalytics.com/blog/2014/07/31/using-graph-databases-to-perform-pathing-analysis-initial-experimentation-with-neo4j/ Thanks to Michael Hunger for his comments on the first post and for spotting my error! Nick -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
