Update Query Cluster name
planned
F
Florian Gehrlein
Often the displayed cluster name is based on a variant of the cluster which is not popular or even useless.
Example @hede:
A cluster is called "vausschnitt Pullover" and the MQ is "pullover v ausschnitt".
"vausschnitt" has 0 popularity within this cluster but is the main title of the cluster.
2 optimizations would be helpful:
- rename the cluster after the master query (no matter if set manually or data based)
- option to rename a cluster (overwriting the existing clustername)
Andreas Wagner
planned
A
Anton Siegordner
Great suggestion! Our ECom Team as well would very appreciate this function as it gets a bit confusing when various team members are working inside Searchhub Clusters not directly knowing which main / master cluster sits behind the cluster "name"
Andreas Wagner
Ok after a long evaluation phase we came to the conclusion that the only practical way would be as already mentioned to give users a special marker where they could flag a label that is inappropriate. This feedback is then fed back to the LLM which should solve the problem.
Leon Anthony MENGE
Hi Andreas,
for me this solution would be fine
Andreas Wagner
under review
Andreas Wagner
Update here: Since we are currently working hard to get the Customer-specific LanguageModels running we already considered this use-case during development. The only thing remaining is the UX/UI part. Expect some UI proposals here for voting in the upcoming weeks.
Leon Anthony MENGE
Maybe it makes sense to have it similar to manually overriding the Masterquery? That there is an icon you can click and then that's the display name.
F
Florian Gehrlein
Sounds like a nice and easy2use way to implement it in the UI. Or maybe just name the query cluster 1:1 as the recent MasterQuery with the option to manually change it with a simple click?
F
Florian Gehrlein
Hi Andy,
using flags or labels is a possibility which could help to get a better overview of mapped clusters - yes.
But the flag/label must be present in the displayed data of the cluster overview (left table).
Maybe you can add a scribble of your idea and how it could look like?
Or maybe you can add a seconde column on the left side called "MQ" and display the masterquery of each cluster already within the overview?
Andreas Wagner
Hi Florian,
unfortunately this is not an easy task as the Label is dynamic and only dependent on the LLM (Large Language Model) we use across customers. The idea of the Label (cluster Name) is NOT to represent the most popular query but the Query that contains most distinguishable information.
Even though we are really strict in terms of data quality when building the LLM there is no practical way to mitigate all errors.
Therefore my idea would be to give customers the possibility to flag these kind of mis-labeled queries and use this feedback to further improve the quality. What do you think?
F
Florian Gehrlein