[MGNLPER-215] Investigate why Pages Title search behaves differently Created: 13/Dec/23  Updated: 09/Feb/24

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

Type: Spike Priority: Neutral
Reporter: Laura Delnevo Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: searchx
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-8301 In-App search functionality for Pages Closed
relates to MGNLUI-8302 In-App search functionality for Assets Closed
relates to MGNLPER-218 Investigate Global API vs In-App API Closed
Template:
Epic Link: SearchX 1. In-App search & Top Nav

 Description   

Following findings with the implementation of MGNLUI-8301 and MGNLUI-8302 we have confirmed that both apps have the same Search behavior:

  • If we search with the node name -> contains and not by exact with FTS and In-app search
  • Node properties -> it’s an exact match
  • There’s a case when searching with the page title, the FTS and In-app search behave differently. This needs investigation to understand why 

Performance concern

Search by contains, and not by exact match -> may potentially have a performance impact. E.g

Pages has property value: “container for”
exact match:
“container for”
“container”
“for”
are the keywords which can return page
**

not by exact match
all the options above AND
“container”
“container for”
“container for”….


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