Hello Will, Great session!! :) I just have one small question if you help answer that please. You mentioned that there could be multiple tags associated with a node. Could you please share an example where having multiple labels for a node would be useful?
Let's say you have a Service Node which represents every service (train) in a plan. Now in a typical plan for 6 months, you might have hundreds of thousands of services which run on different days. Now instead of having just one label "Service", you can also label them as SundayService, MondayService and so on to represent Services which run on a given weekday. By doing that you will have the total number of SundayService nodes far less than Sevices nodes. So now you can use label SundayService in your cypher queries to work on smaller data set rather than huge dataset of Service nodes, which will make you query much faster. Hope it helps
Hi William, I am too confused about Neo4j and wanted to ask you directly. Any help would be appreciated. What I want to create is search engine for documents ok. I am also interested in grap machine learning and recommendation engines but also want my platform seem a bit interactive and stylish so I will use react js. The question is that which way is much more compatible with Neo4j? Node. js+react or Django+react? What do you suggest me as beginner on graph databases? I want to fully dive into this topics. Thanks in advance!!!
Sorry about that - looks like the dropbox link died :-( I've added the slides to the Github repo here: github.com/johnymontana/oscon-neo4j-recommendations
will ,great session thank you for it
Hey William,
The cypher Query at 27:40 Considering the direction of relationship
Is it *Match (t)
Hello Will, Great session!! :) I just have one small question if you help answer that please. You mentioned that there could be multiple tags associated with a node. Could you please share an example where having multiple labels for a node would be useful?
Let's say you have a Service Node which represents every service (train) in a plan. Now in a typical plan for 6 months, you might have hundreds of thousands of services which run on different days. Now instead of having just one label "Service", you can also label them as SundayService, MondayService and so on to represent Services which run on a given weekday. By doing that you will have the total number of SundayService nodes far less than Sevices nodes. So now you can use label SundayService in your cypher queries to work on smaller data set rather than huge dataset of Service nodes, which will make you query much faster.
Hope it helps
Hi William, I am too confused about Neo4j and wanted to ask you directly. Any help would be appreciated. What I want to create is search engine for documents ok. I am also interested in grap machine learning and recommendation engines but also want my platform seem a bit interactive and stylish so I will use react js.
The question is that which way is much more compatible with Neo4j? Node. js+react or Django+react? What do you suggest me as beginner on graph databases? I want to fully dive into this topics.
Thanks in advance!!!
Hey William Lyon! Thanks for your presentation.
The link for your slides is not available anymore.
Sorry about that - looks like the dropbox link died :-( I've added the slides to the Github repo here: github.com/johnymontana/oscon-neo4j-recommendations
Where can I get the data for this if it is not on the sandbox
Here in his github link: github.com/johnymontana/oscon-neo4j-recommendations/blob/master/graph-based-rec-sys.ipynb