You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
MockedKnowledgeBase
class for convenience instead of the more low-levelKnowledgeBase
interface.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.The text was updated successfully, but these errors were encountered: