How to configure the portal search to always sort the results by 'Relevance'?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2024 06:53 PM - edited 05-20-2024 06:58 PM
We are upgrading our Utah instances to the Washington release, and our testers found out that the portal search returns inrelevant search results, especially when comparing them to google search results. We have over 40,000 public knowledge articles, and the portal knowledge search is pretty vital for our users.
After some investigation we found out that Washington release stripped the search functionality. It looks, it is no longer possible to configure the search engine to ALWAYS sort the search results by relevance.
In contrast, all search engines I know (google, yahoo, bing, duckduckgo, yandex, etc.) have this as the default setting. Actually, they do not pressent any options to change this behavior, because to show the most relevant information on top of the search results is the essence of any search engine.
We know about the existance of the 'knowledge.search.sort.field' and 'knowledge.portal_search.sort.field' user preferences, but they pretty useless in regards to set the default behavior of the search engine.
Does anyone know how to configure the portal search engine in the Washington release to always sort the results by relevance?
This would be possible by rewriting the "Knowledge Result Sort" widget, but we would like to avoid this modification.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2024 03:11 PM - edited 11-08-2024 03:24 PM
Hi Ron,
HI said they fixed the issue (PRB1767594) in Xanadu, but we are still on the Washington release, and we got a fix in patch level #6.
After getting the patch, we had to do the following to get the desired behavior:
1. Set system property 'glide.knowman.save_portal_search_sort_field_user_preference' to 'false'.
2. Remove all personal resources "knowledge.portal_search.sort.field" from the table "sys_user_preference", except two as defined in step #3.
3. Added two resources "knowledge.portal_search.sort.field" to the table "sys_user_preference" as follows:
- For not authenticated users:
Name: knowledge.portal_search.sort.field; System: false; User: <empty>; Type: string; Value: relevancy:desc
- For authenticated users:
Name: knowledge.portal_search.sort.field; System: true; User: <empty>; Type: string; Value: relevancy:desc
Probable you will need to perform a similar configuration on Xanadu.
I hope this helps.
Thanks,
Marek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2024 07:35 AM
Hi Marek
What is the solution for this, even i'm facing issue in Xanadu