search

AidanTilgner / Onyx-Personal

This is my personal version of the (so far nonexistent) Onyx Systems core microservices. This is the original project and might change over time, but is completely self-hostable. Still very much pre-production though.
1 stars 0 forks source link

Add ability of interpretation server to keep track of context based on session ID, and later user ID #48

Open AidanTilgner opened 2 years ago

AidanTilgner commented 2 years ago

This isn't gonna be the issue for creation of user based context, but will mention it as it will be based off of this

Entity extraction is going to require being able to look at the context of the conversation that has transpired such far and see if any relevant information exists. The Action server is going to be equipped with an endpoint to find metadata on the action required. Because of this, there will be an ability to add a "search_context_for" property to the response of that endpoint. Then, using that response, we can search the metadata accordingly. Since everything is action specific, we can get as specific or generic as we want in the action.

The way to gather this information will be variant, and will not only come from one source. An action's metadata might contain information on things to store, alternatively, if an action detects something it thinks the Interpretation server should store, it can make a post request to an endpoint to do that.

AidanTilgner commented 2 years ago

The unstable version of NLU, which uses forms, keeps track of forms based on session_id, which is included in the package, and readable by all servers.