[ADMINCTR-431] Search Relevance metric. Number of queries vs number of clicks on the result Created: 05/Apr/23  Updated: 11/Aug/23  Resolved: 11/Aug/23

Status: Closed
Project: Admincentral
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.33

Type: Task Priority: Neutral
Reporter: Laura Delnevo Assignee: ricardo gonzalez
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-08-11-19-17-40-291.png    
Issue Links:
Cloners
clones MGNLPER-185 Search Performance metric. How many m... Closed
is cloned by MGNLRANK-8 Search Relevance metric. Position of ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: User-based ranking
Story Points: 3
Team: AuthorX
Work Started:
Approved:
Yes

 Description   

Context:
**

OKR 

Objective. Speed up content creation & content management

Key result (Quarterly KR): Search Relevance. Increase % of clicks in the top 10 results

https://docs.google.com/document/d/1txbkoTv53Wi9l2XonnBRQtxiu-xR-GQP0epX6dx8xVs/edit# 

 

AC: 

 Collect using magnolia user metric framework the following data:

  • nb of queries issued into findbar
  • nb of pickedItems
  • the ratio: pickedItems/total queries

Note: we do not need to track the metrics per user. This are cumulative metrics

Dev notes:
The ideal scenario is to send the 2 deltas (totalQueries and pickedItems) over to the magnolia telemetry system. And the ratio would be computed by 

Sum(deltas(pickedItems))/Sum(deltas(totalQueries))

This way we can control when to reset the counters


Generated at Sun Feb 11 23:07:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.