Don't forget to accommodate multiple degrees with the same school... (I had
done the same mapping before... :D)

education":[
{"school":{"id":2"","name":"A"}, degrees: [
                                      {"type":"MS", "title":"B",
"year": "YYYY"},
                                      {"type":"PhD", "title":"C",
"year": "YYYY"}
                                     ]
}


On Thu, May 31, 2012 at 2:42 AM, Michael Hunger <
michael.hun...@neotechnology.com> wrote:

> Yes your suggestion sounds good.
>
> If you're interested in the actual classes (e.g. for connecting other
> users to the same class aka stayfriends) then you'd also model the classes
> as nodes (but only if you really need it in your problem domain, you can
> also later still evolve the model).
>
> For looking up users and places you would use unique index id's.
>
> Traversing is fast as it is the core graphdb operation.
>
> The main performance difference is from where you start the traversal
> (i.e. the user which has just a few rels or the place, which might have
> many rels) and how you continue from there.
>
> If you need at some point you can add additional relationship with just
> the degree's for.
>
> e.g. (user) - PHD -> (MIT)
>
> Michael
>
> Am 31.05.2012 um 10:50 schrieb Maaz Bin Tariq:
>
> > I want to store Facebook educations of a user in Neo4j, so that i can
> query on any attribute combinations.
> > Currently Fields I want to save of Facebook education field
> > https://graph.facebook.com/me?fields=id,name,education&access_token=...
> ..
> >
> > {
> > id:1
> > name:"xyz"
> > education":[
> > {"school":{"id":2"","name":"A"},
> >  "degree":{"id":3"","name":"B"},
> >  "year":  {"id":4"","name":"C"},
> >  "type":"X",
> > },.....]
> > }
> >
> > In MySQL I will create an education table with following table user_id,
> school_id,degree_id,year_id,type
> > Not sure whats the best way to store it in Neo4j.
> > 1. possible solution is
> > Node User --------->(edu relationship) ---> Node school
> >
> > degree,year,type are relationship attributes.
> > Not sure it will be be fast if we traverse users on type and degree
> attributes. (i.e relationship attributes)
> > Is there any other or better way?
> >
> > Thanks
> > -Maaz
> > _______________________________________________
> > NOTICE: THIS MAILING LIST IS BEING SWITCHED TO GOOGLE GROUPS, please
> register and consider posting at
> https://groups.google.com/forum/#!forum/neo4j
> >
> > Neo4j mailing list
> > User@lists.neo4j.org
> > https://lists.neo4j.org/mailman/listinfo/user
>
> _______________________________________________
> NOTICE: THIS MAILING LIST IS BEING SWITCHED TO GOOGLE GROUPS, please
> register and consider posting at
> https://groups.google.com/forum/#!forum/neo4j
>
> Neo4j mailing list
> User@lists.neo4j.org
> https://lists.neo4j.org/mailman/listinfo/user
>
_______________________________________________
NOTICE: THIS MAILING LIST IS BEING SWITCHED TO GOOGLE GROUPS, please register 
and consider posting at https://groups.google.com/forum/#!forum/neo4j

Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user

Reply via email to