Hi, The answer to your question is totally dependent on what you want to achieve with your system. There could be a third approach in which you model a Person and Services. A person could have relationships with services that they provide.
If you can share some more details about your use case, it would be easier suggesting a model. -- Thanks and Regards Mahesh Lal -- Thanks and Regards Mahesh Lal On 23 January 2016 at 22:47, Ahmed ABUABDOU <[email protected]> wrote: > Hello, > > I am new to neo4j and wonder about the suggested modeling for the > following simple scenario: > For a a service with a provider such as an Elctrician, Mechanic, Cook > ...etc. how would a node look like? > 1. A generic Node "*Service Provider*" with a property "*type*" and value > "*Electrician*"; another Node "*Service Provider*" with a property "*type*" > and value "*Mechanic*" ..etc. > 2.) Or would be better to create concrete nodes such as "*Electrician*"; > another node "*Mechanic*" ...etc.? > > Thanks > > -- > 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. > -- 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.
