We can add a new field to the menu e.g. searchweight as default value 5 (medium). If we can increase the number to 10 then this menu item will be most relevant in the search results.
so when user type e.g product and product window has relevance 10 then instead alphabetical order we can weight the search result and show product window as first.
later - if we want we can use specific algorithms and types for relevance calculation well. (eg. weight by usage) in menu, we need to add default sort order - alphabetically, search relevance, usage-relevance.
Environment
None
Activity
Show:
Carlos Ruiz November 29, 2019 at 11:16 AM
Implementing a usage counter sounds not too difficult, we could add a new table, or simply add a Counter to AD_TreeBar.
Heng Sin Low November 29, 2019 at 8:49 AM
Having a searchweight at menu item is too manual and it is hard for the implementor to guess a good weight value for all users. A better approach should be driven by the user’s usage pattern. For e.g, with search term “pr”, product window come first for user A if user A use that more often and user B can have price list windows comes first if that’s what user B usually use everyday.
For such implementation, you can’t have it as a single field at menu item as that should be something user specific and not a system wide share value.
We can add a new field to the menu e.g. searchweight as default value 5 (medium). If we can increase the number to 10 then this menu item will be most relevant in the search results.
so when user type e.g product and product window has relevance 10 then instead alphabetical order we can weight the search result and show product window as first.
later - if we want we can use specific algorithms and types for relevance calculation well. (eg. weight by usage)
in menu, we need to add default sort order - alphabetically, search relevance, usage-relevance.