Skill Cloud – Part 3
One of the obvious way to store a skill cloud is through a graph database. Neo4j or Titan are two possible choices. For no reason in particular, I’ll go with Neo4j, and use the embedded version with Java simple for a way to get up and running quickly. Adding the Maven dependencies into my pom.xml is the easiest way to get started. The Neo4j HelloWorld sample is probably the easiest thing to borrow as a skeleton for a quick start.
Modelling a person, their skills and their team is obvious an important part of this proof of concept (PoC). Skill’s and team members would be modelled as Node’s (obviously), with appropriate relationships to capture linkage to a persons skills cloud (node’s) coupled with who working with who in a team – team is clearly a node in itself.
This nicely leads to “Representing time dependent graphs in Neo4j ” on GitHub. What’s possibly interesting is that ideally you want a bi-temporal view of the nodes and relationships, since people, and teams change over time.