You can have nodes that represent users, and link those nodes to the
concept nodes via a "PARTICIPATED" relationship when they perform some
action on that concept.
Assuming your users can be identified with a number between 1 and 100k,
another option I guess is to use a bitset (saving it as a Byte Array) in
the relationships between concepts and when traversing you'd check to see
if the bitset was "1" for the user doing the traversal if they participated
in the child concept.
You could also link a user just to the most detailed level and traverse UP
the concept graph.
On Thursday, January 9, 2014 11:58:13 AM UTC-6, pete huerter wrote:
>
> I am looking for a scalable db to support an app that aims to serve people
> recovering from various forms of childhood abuse. The app attempts to
> aggregate info entered by each survivor to be used as a tool by survivors
> in their recovery. My initial target is 100k people.
>
> *The UI is a big concept map (graph) that is dynamically defined by the
> survivors. I want to track the participation of each survivor in each node
> of the resulting graph. Worst case I am looking for a db that can track the
> participation of 100k survivors at each node in the graph, and 100k users
> simultaneously defining and/or querying the graph. So, worst case, each
> node/edge would have either 100k properties (participants) or a single
> property ("particpants") with 100k entries that is constantly being
> appended to and queried to find relationships. Is Neo4j capable of this
> sort of scalability? *
>
> *More info:*
>
> I want a survivor to be able to enter his/her experiences and also query
> for example "of all survivors that are male that have young children of
> their own and are still with their spouse what challenges do they face and
> what has helped them face these challenges?".
>
> Imagine a graph decorated with people, a person appears at (subscribes to)
> a node or edge if that node/edge is relevant to his/her personal
> experiences. When the graph does not reflect his/her experiences they add
> to the graph to cover their case. Users following along in this new
> subgraph can add themselves or not if this new experience is relevant to
> them ... and so on.
>
> I need a db that can not only represent the graph (easy) but track and
> aggregate participation for each node/edge in graph (hard?). *My initial
> target is 100k people simultaneously editing and querying the graph*. It
> is important that the entire graph be visible (in aggregated form) and that
> users can navigate the graph (diving) by querying.
>
> Survivors need to know they are in good company. And those who have
> recovered are really good at helping other survivors. The goal of this
> project is to facilitate the recovery process for many.
>
> I would really appreciate some steering please.
>
> Sincerely,
> Pete Huerter
>
--
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/groups/opt_out.
