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

ConversationInterestingTermsExtractor needs to support Clients #290

Open
westei opened this issue Sep 27, 2018 · 0 comments
Open

ConversationInterestingTermsExtractor needs to support Clients #290

westei opened this issue Sep 27, 2018 · 0 comments
Assignees
@westei
Labels
bug ready
Milestone
v0.9.0

Comments

@westei
Copy link
Member

westei commented Sep 27, 2018

The ConversationInterestingTermsExtractor looks for interesting Terms (part of Keyword Extraction) in the Conversation Index.

This allows to suggest Keywords based on Topics mentioned in previous conversations.

However the current Implementation does not respect multiple clients but will search in Conversations of any Client. Because of this this component is deactivated at the moment.

With this fixed this component will replace the Customer specific Solr Indexes
@westei westei added this to the v0.9.0 milestone Sep 27, 2018
@westei westei self-assigned this Sep 27, 2018
westei added a commit that referenced this issue Sep 28, 2018
@westei
WIP solr7 update
5aebed3 
* deleted the chatpal backend #289
* updated Solr Version to `7.5.0` #248
* started to update Solr configurations for the new Solr Version #248
* started to adapt the ConversationInterestingTermsExtractor so that it works with multiple clients (will replace the Systel Crawl Solr index) #290
westei added a commit that referenced this issue Sep 28, 2018
@westei
finished implementation of #290
3fbdfb2 
* The MLT query uses the iterms field the contains the content but is configured to work with the IterestingTerms implementation
* Only Messages are considered (to avoid text duplications in indexed conversations)
* The actual MLT query filters for the current Client so that only content of this client is used to calculate interesting Terms
westei added a commit that referenced this issue Apr 4, 2019
@westei
fix for #308: Also required adaptations to the assertions in tests as…
02fb779 
… fixing this issued caused the new ConversationInterestingTerms (#290) to extract additional keywords (as the conversation do now get indexed during the integration tests)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@westei westei

Labels
bug ready
Projects
None yet
Milestone
v0.9.0
Development

No branches or pull requests
1 participant
@westei