Using a Graph DB to store metadata #6586
Replies: 2 comments
-
Interesting idea, and thanks for sharing the AGE link. |
Beta Was this translation helpful? Give feedback.
-
Hi, yes, definitely it would be a great extension actually I'm missing the relationships a lot. I'm planning to develop my own extension to use the graphdb capabilities to register and better maintain relations between packages (it would be a perfect fit with my jsonschema which allows also multiple strongly typed of resources). Currently I'm still evaluating the platforms and the correct technologies to use: Do you have some progress to share on this topic? |
Beta Was this translation helpful? Give feedback.
-
Metadata naturally lends itself to graph databases, as it logically maps to how triples work, without having to deal with rigid metadata schemas.
In addition, it enables more natural, flexible, powerful queries without complex joins and even enables inference.
There have been several attempts to graft graph DBs to CKAN in the past, but they have not reached critical mass.
Now that we have the Apache AGE (A Graph Extension) project (https://age.apache.org/) that adds graph database functionality to PostgreSQL, perhaps, its time to revisit storing metadata as a graph and replace the
extras
tables?Tabular data will still remain as regular SQL objects. And it can all be done with PostgreSQL.
Any thoughts?
Beta Was this translation helpful? Give feedback.
All reactions