Ok that makes sense. I'll give this a shot and see how it works out. Thanks.
On Tuesday, October 4, 2016 at 6:50:55 AM UTC-6, Michael Hunger wrote: > > Really good question. > > It depends a bit on what you want to do with the data. In general as > enrollment is an important concept, it would be turned into a node. > > CREATE > (s:Student)-[:ENROLLED]->(e:Enrollment)-[:IN_COURSE]->(c:Course)<-[:PROVIDING]-(d:Department)-[:OF_COLLEGE]->(co:College),(e)-[:DURING]->(sm:Semester) > > [image: Inline image 1] > > On Tue, Oct 4, 2016 at 7:43 AM, Chase Willden <[email protected] > <javascript:>> wrote: > >> I'm trying to understand how to architect an educational graph database. >> Here is my use case. >> >> 20,000 student enrollments >> per semester (10 total) >> enrolled in a section of >> 300 unique courses.within >> 20 departments within >> 8 colleges >> >> Any suggestions on how to structure this? >> >> As a side, I've been reading and it seems that structuring the graph >> database is a common learning barrier for many beginners with Neo4j. >> >> -- >> 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] <javascript:>. >> 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.
