Use other knowledge graphs

[Davy-Chendy]

Thanks for your work. If I now have a simple CSV file of the Knowledge Graph that I want to use in my KG_RAG, how can I embed it in the code concisely and quickly, and what I need to change?

[karthiksoman]

Thanks @Davy-Chendy
That is an interesting application which we are planning to incorporate. It should include minimal changes such as (possible) modification in the vector database population and routing to local graph (rather than current API call to the remote graph).
Once this is added to KG-RAG and tested, I will post the announcement here :)

[christ25442544]

I was wondering if there have been any updates or progress? Excited to test that too!!

[karthiksoman]

@christ25442544 Thank you for your dedicated interest! We're excited about this feature and have been discussing ideas through collaborations. The fact that this GitHub issue remains open is to gather more input from the community. We appreciate your patience as we work on it.

[Mnikley]

I think the idea to fetch data from another data source (local, or remote) would be great. An universal interface that defines the required methods / parameters would be needed, from which connectors for SPOKE/local files/databases (e.g. neo4j) could be derived, which then replace get_context_using_spoke_api(). I can help with the python neo4j driver if help is wanted.

[karthiksoman]

@Mnikley That sounds like a fantastic extension! The key requirement is that it should offer flexibility in switching between external knowledge bases. For instance, if the user wishes to switch back to SPOKE, the system should handle it seamlessly. If you have a working prototype, feel free to submit a PR. Sounds exciting!

[Mnikley]

@karthiksoman ok - I don't have a prototype yet, but will submit a PR as soon as I have something 👍

[karthiksoman]

@Mnikley Sounds good and looking forward to that!