Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Admin UI implementation to make meta functionality reusable. #581

Open
bnouwt opened this issue Dec 17, 2024 · 0 comments · May be fixed by #583
Open

Update Admin UI implementation to make meta functionality reusable. #581

bnouwt opened this issue Dec 17, 2024 · 0 comments · May be fixed by #583

Comments

@bnouwt
Copy link
Collaborator

bnouwt commented Dec 17, 2024

The current Admin UI is a KB that keeps a collection of other KBs in the network with all metadata about descriptions, knowledge interactions (KIs) and graph patterns attached. This information is automatically updated whenever KBs or KIs are added/removed in knowledge network (it hooks into the meta KIs of the smart connectors themselves). Keeping track of this meta data is not only useful for the Admin UI, but also for other KBs that need this information. So, this issue describes separating this part of the Admin UI from the other code (but keeping it int he admin-ui module).

Concretely, this issue will:

  • make the admin ui use the MockedKnowledgeBase class for convenience instead of the more low-level KnowledgeBase interface.
  • Separate the Admin UI specific stuff, from the Meta Knowledge Base stuff and rename things accordingly.

Two use cases where this new MetaKB class could be useful is in a storage KB where you can select from all KBs and KIs in the network which information you want to store and also a anomaly detection KB where you can select which KIs of which KBs you want to keep track of while looking for anomalies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant