Skip to content
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.

Token based Related Conversation #189

Closed
westei opened this issue Jan 30, 2018 · 2 comments
Closed

Token based Related Conversation #189

westei opened this issue Jan 30, 2018 · 2 comments
Assignees
Milestone

Comments

@westei
Copy link
Member

westei commented Jan 30, 2018

We need a QueryProvider that supports to suggest related Conversation based on Removed/Added Tokens of the User.

The current SolrMLT based solution does not allow for this and for using the ConversationQueryBuilder the conversation service needs to support uploading modified Analysis (with updated Tokens based on User Interactions with the Widget).

This will also require a configuration change for existing Clients if we move away from the Solr MLT to a Token based implementation.

@westei westei added this to the v0.7.0 milestone Jan 30, 2018
@westei westei self-assigned this Jan 30, 2018
westei added a commit that referenced this issue Feb 2, 2018
…ation web service; The AnalysisService also supports parsing custom Analysis. In this case only Templates and Queries are re-calculated
westei added a commit that referenced this issue Feb 2, 2018
… used for this issue. Refactored the QueryBuilder to be client executed. The Idea is to use the MessageSearchService (used by the Chatpal demo and Smarti `6.6.1`) for the Smarti Widget to search for related conversations.

* implementation of #192: The MLT now uses only recent messages as context for related conversation searches
* Added support for a configuration that allows to enable/disable a filter for completed conversations (default: also consider not completed)
westei added a commit that referenced this issue Feb 2, 2018
…h functionality required to search for “Expertengespräche” based on tokens; The service and webservice was updated to work with the new authentication model; ConversationSearchQuerybuilder now supports configuration of defaults (e.g. highlighting, sorting, … ) The defaults are set based on what was used for the chatpal demo powered by the 0.6.1 version of the message search
@westei
Copy link
Member Author

westei commented Feb 2, 2018

Server side implementation is more or less complete. Widget support is pending (hence assiging to @Peym4n )

The query is based on the related.conversation template. Here is an example Query

{
      "_class" : "io.redlink.smarti.query.conversation.ConversationSearchQuery",
      "creator" : "queryBuilder:conversationsearch:conversationsearch",
      "displayTitle" : "Conversationen zum Thema [Request, Facets, Solr Query, einfachen Parameter, `facet.limit` parameter, Anzahl, schau, Sagen]",
      "confidence" : 0.6,
      "url" : null,
      "inlineResultSupport" : false,
      "created" : 1517574598824,
      "state" : "Suggested",
      "defaults" : {
        "hl" : "true",
        "fl" : "id,message_id,meta_channel_id,user_id,time,message,type",
        "sort" : "time desc",
        "hl.fl" : "message",
        "rows" : 3
      },
      "keywords" : [ "Request", "Facets", "Solr Query", "einfachen Parameter", "`facet.limit` parameter", "Anzahl", "schau", "Sagen" ],
      "queryParams" : [ ],
      "filterQueries" : [ "-meta_support_area:*" ]
    }

Notes:

  • The url is not yet set, but this is expected to do a GET /conversation/search-message
  • filterQueries are set based on the configured meta fields and context information of the conversation (similar to the SolrMLT)
  • configuration supports setting the defaults

@mrsimpson
Copy link
Collaborator

Created #212 as a minor left-over

@ghost ghost removed the in review label Feb 22, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants