[MGNLPER-39] Support cross-supplier search and ranking for "Top hits" Created: 27/Jul/18  Updated: 22/Sep/22  Resolved: 22/Sep/22

Status: Closed
Project: Periscope
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Neutral
Reporter: Cedric Reichenbach Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: 0.05h
Time Spent: Not Specified
Original Estimate: 0.05h

Issue Links:
Relates
relates to MGNLUI-4728 Predictable result category order Closed
dependency
is depended upon by MGNLPER-34 Make Periscope configurable Closed
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: Periscope improvements
Story Points: 13
Team: AuthorX

 Description   

User story:

As an editor, I want to find content quickly and see relevant content first. I have lots of similarly named content all over the system: a tour about Botswana, images of Botswana, and a special landing page about Botswana. When I search "botswana" give me the most relevant items wherever they are.

Business benefit: Find content faster. Feel that you are in control of your content. Avoid losing content.

Acceptance criteria from MGNLPER-34:

  • Top hits in the Find Bar are the most relevant results across all result suppliers.
  • Limit Top Hits to 3 items.
    • This requires minor adjustments in the search and ranking system, which has so far only been focused on per-supplier search and ranking.
  • In CE, take the top 3 results as ranked by Lucene.
  • In EE, take the top 3 results as ranked by AI.
  • List Top hits in their own group in the search results, after Apps. See mockup.

Mockup "Top hits": https://zpl.io/agnRPLO



 Comments   
Comment by Cedric Reichenbach [ 05/Nov/18 ]

This is technically problematic to implement at the moment: In order to get top results across all suppliers, we first need the result list of all those suppliers, which is fairly expensive. We basically need to search whole Magnolia and then bubble up the most relevant results.

Now, in order to avoid "jumps" in the UI, we always list suppliers in proper order. That is, if expected order apps -> pages -> assets, we'll always wait for apps to be finished before we list anything else, even if pages or assets would already be available. And since top results would (naturally) be among the first suppliers in that list, we'd always have to wait for that one to be finished first, which is roughly equivalent to waiting for all the results to be in before we display anything. Thus, we'd lose the benefit of chunk-wise ("as-they-arrive") result listing.

Comment by Simon Lutz [ 19/Dec/18 ]

Value to be reviewed.

Generated at Mon Feb 12 10:28:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.