Predefined constraint

37 views
Skip to first unread message

André Victor

unread,
Oct 27, 2017, 5:33:47 PM10/27/17
to Popotojs alpha
Firstly, great job. Popoto.js is awesome.

I have been trying to create a similar form to filter the results using a predefined constraint, like you showed in http://www.popotojs.com/live/node-images/input.html
However, I made some adjustments to meet my requirements, but I still have not achieved to the expected behavior. I hope getting your help to make it work.

In order to avoid using the same filter for both Labels, I have created different buttons and text boxes, one for each label I want to filter (ex.: one for Person and another for Movie). However, if a label occurs more than once during the navigation from root node, the same constraint is applied in these occurences and this is not the behavior I expect to implement.

Let's see my graph. I have been populating a simple news model with 3 labels: News (ex.: BBC, TV5, CNN, etc.), Person (people mentioned in the news) and Place (places mentioned in the news). The relationship directions were originally defined: News->Person and News->Place. However, to allow the navigation of paths and more complex queries in Popoto, I have created the bidirectional relationship.

Suppose, for instance, a navigation where the root node is Person and I expand its relationships. In this case, I will see all the news that mention this person. Further, if I continue navigating and expand the relationships of these news, I will see again the Person label. However, if I have a filter ou constraint defined, I could choose only Person nodes that match with constraint initially defined, as well as News and so on. I have been trying to implement differently. I intend, for example, to see what people are usually mentioned together, even when I use a constraint to filter the initial or final set of nodes I want to see, but without limiting all the path.

If I filter a node in Neo4jBrowser, for instance, and expand its relationships from the root node, I will see Person nodes that does not match the same original filter. It is the same behaviour I expect to implement.

I am not sure if you understand my point. I evalueated your code and I supposed to change the query string in some javascript function in popoto.js. I have tried to change some functions, like generateResultQuery, generateData, and etc. but it has not worked. Could you suggest me what funcion or javascript code I should change to meet my requirements?

Thanks a lot and congratulations again for the initiative.

My best regards,
Andre
Reply all
Reply to author
Forward
0 new messages