Search results on the API route are now ranked based on their similarity to the search key. An added flag has been introduced to allow users to modify the minimum similarity score, which is defaulted to ?similarity=75 to return results that have similarity of 75% or greater. To accommodate these performance impacts by ranking the results, the search field de-bouncing has been increased to 450ms, which is still within unnoticeable limits. Additionally, the default results limit on the client side has been increased from 20 to 25 for more results.
The search is still case insensitive.
Thing now appears at the top:
After some quick tests i have noticed that searching for specific ID's will require significantly more numbers than it used to, as it doesnt return all the results with that number in it but instead by string matching with a score. However, this should be a non-issue as when searching for a specific id using numbers, the user should have the entire id anyways.
THIS HAS BEEN RESOLVED BY INTRODUCING CUSTOM RANKER FUNCTION
To-dos
[x] Add relavence ranking to search results.
[x] Update search field de-bouncing to improve performance impact.
Description
Search results on the API route are now ranked based on their similarity to the search key. An added flag has been introduced to allow users to modify the minimum similarity score, which is defaulted to
?similarity=75to return results that have similarity of 75% or greater. To accommodate these performance impacts by ranking the results, the search field de-bouncing has been increased to 450ms, which is still within unnoticeable limits. Additionally, the default results limit on the client side has been increased from 20 to 25 for more results. The search is still case insensitive.Thing now appears at the top:
After some quick tests i have noticed that searching for specific ID's will require significantly more numbers than it used to, as it doesnt return all the results with that number in it but instead by string matching with a score. However, this should be a non-issue as when searching for a specific id using numbers, the user should have the entire id anyways. THIS HAS BEEN RESOLVED BY INTRODUCING CUSTOM RANKER FUNCTION
To-dos
Misc
Closes #86