{"action":"opened","issue":{"url":"https://api.github.com/repos/redlink-gmbh/smarti/issues/2","repository_url":"https://api.github.com/repos/redlink-gmbh/smarti","labels_url":"https://api.github.com/repos/redlink-gmbh/smarti/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/redlink-gmbh/smarti/issues/2/comments","events_url":"https://api.github.com/repos/redlink-gmbh/smarti/issues/2/events","html_url":"https://github.com/redlink-gmbh/smarti/issues/2","id":241713478,"number":2,"title":"Add support for knowledge provider configuration","user":{"login":"ruKurz","id":853776,"avatar_url":"https://avatars2.githubusercontent.com/u/853776?v=3","gravatar_id":"","url":"https://api.github.com/users/ruKurz","html_url":"https://github.com/ruKurz","followers_url":"https://api.github.com/users/ruKurz/followers","following_url":"https://api.github.com/users/ruKurz/following{/other_user}","gists_url":"https://api.github.com/users/ruKurz/gists{/gist_id}","starred_url":"https://api.github.com/users/ruKurz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ruKurz/subscriptions","organizations_url":"https://api.github.com/users/ruKurz/orgs","repos_url":"https://api.github.com/users/ruKurz/repos","events_url":"https://api.github.com/users/ruKurz/events{/privacy}","received_events_url":"https://api.github.com/users/ruKurz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-07-10T13:33:19Z","updated_at":"2017-07-10T13:33:19Z","closed_at":null,"body":"This issues aims to extend Smarti for „Knowledge Provider“ configuration support.\r\n\r\nAs Smarti extracts keywords and other facts from a conversation, these should be used to query external information sources, called knowledge provider. Currently only one Solr endpoint can be configured. In order to attach enterprise search engines or public web searches as google, we need a flexible deployment configuration as well as a runtime configuration for client specific settings. Also endusers should be able to modify search parameters (filters, keywords, etc.) via the Smarti UI.\r\n\r\nSince the client* himself must be able to change this configuration, this feature requires an administration backend for Smarti.\r\n\r\nIf one client configures 10 or more websites to be searched, Smarti UI runs the risk to be overloaded. For this reason the UI must be clear and intuitive. Also the users themselves must have the flexibility to change/select/switch the sources. This story leads in three main requirements:\r\n\r\n1. deployment configuration (for all customers)\r\n* Additional Search/Knowledge Provider like google, Solr or other external search providers are added with essential configuration (e. g. which token types are forwarded as search terms)\r\n* Changing this configuration needs a server reboot\r\n\r\n2. runtime configuration (per customer)\r\n* One client should be able to select and configure the specific knowledge providers that are relevant for him\r\n* In the case of google and or Solr multiple instances of the same source must be configurable\r\n\r\n3. UI integration (user behavior)\r\n* At run-time users should be able to select sources they want to search, e.g. by selecting/changing a source in the Smarti UI. This is important if Smarti suggest the \"wrong\" source or if another source is more appropriate.\r\n* the user is able to initiate a search in a specific source when the \"human intelligence\" knows the right way to search\r\n* the interaction with the results of external sources gives us information about the relevance of result entries. This information should not be lost. Instead the usage of search result suggestions should be tracked somehow, in order to improve the scoring\r\n\r\n*Remark: A client is identified by a \"domain\" which is already part of all requests issued to Smarti."}}
{"actor":{"display_login":"ruKurz"}}