Feature request #1410
Replies: 2 comments
-
|
Hi @velmurugan-dhanapal, thanks for the feature suggestion list. I have converted this issue to a discussion item in GitHub for better tracking. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @velmurugan-dhanapal for this break down. Just for reference, I'll list out the existing GitHub issues we have for any matching features. If you can, comment on the individual features if there is some aspect of it you want a specific way, especially if it doesn't match whatever is there now. This will help us ensure that Graph Explorer is delivering the functionality that the users actually need.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
3.Multiple default connection options in the connection page
4.Default graph view based one some node which we add as default. Example Person node is default, then based on logged in user it will pull and shoiw the default view
5.Chatbot for analytics, if the user ask questions with help of the graph schema view context, llm will provide the query which will be executed and give as response. Note: the llm API will be private configrable and while calling the api we need to pass the token in header. [create/delete/update option should be restricted in configrable way]
Priority:
1.Schema visualization[there can be same edge label for multiple different node relationship]
2.Chatbot for analytics , User can ask questions should give the answer from the Knowledge Graph
The LLM call should be private API configurable , while calling the api there will be token passed in header for authentication. [The token generation will be api call with private SSO api.], In code level some placeholder ,so tat we can add code to generate token at runtime and add in the header of LLM api call
Beta Was this translation helpful? Give feedback.
All reactions