[MGNLPER-72] Make Find Bar result ranking user specific Created: 12/Dec/18 Updated: 17/Apr/19 Resolved: 29/Jan/19 |
|
| Status: | Closed |
| Project: | Periscope |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Federico Grilli |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | 0d | Remaining Estimate: | 0d |
| Σ Time Spent: | 0.5d | Time Spent: | 0.5d |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Search relevance | ||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Foundation 2, Foundation 3 | ||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 13 | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Goal: Improve the relevance of Find Bar results for an individual user. In Magnolia 6.0, the AI ranks results based on the click-behavior of the entire user population of the instance. We want to make results specific to one user. Business benefit: Help users find their own content items faster. Remember what the user typically works with. Be personal, be relevant. User story:
Acceptance criteria:
|