A graph database is a kind of NoSQL database that uses graph structures with nodes, edges, and properties to represent and store information.
We will talk in this group about the different approaches on how to store information from Drupal entities in such a database.
On of the topics will be Neo4j. Neo4j is a graph database, reliable and fast for managing and querying highly connected data. http://www.neo4j.org
This group was started to aggregat all the discussion into one place and invite as many people to join and together to find the best approach:
Related module:
-
Neo4j Connector https://www.drupal.org/project/neo4j_connector
issue: https://www.drupal.org/node/2238949 -
Search API: https://www.drupal.org/project/search_api
issue: https://www.drupal.org/node/2286293 -
Other modules that could come into the discussion:
https://www.drupal.org/project/relation
Group review - Administration role
For the review of this group they asked me to either:
set the membership to open
OR
to have multiple admins.
Since recently there is lot of spam content produced by robots, I would rather go with having multiple admins.
I am asking you: who would like to join in as an admin for this group?
Read moreNeo4j - storing relation of entities - how to
Use case:
We are working on a project where entities are cross linked. My question is how would it be the best to store these relations.
Entities:
-person
-company
-skill
-job
Relations:
Friends:
person < - > person
CV:
person < - > skill
Working at:
person < - > company
Jobs available:
job < - > company
Skills needed for a job:
job < - > skill
Problem/Motivation
to find the best matching job (that require skills that you have) from the companies where your friends and friends-of-friends work at.
Proposed resolution
Read more