Enhanced Search Result Ordering #11
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `ISearchSource` `get_search_results()` gets an optional sixth value in the return tuple called `order` which is supposed to contain a quadtuple which is to be composed of * rating for pagename/filename * rating for headings * rating for description/content * timestamp The `order` parameter is then used to sort search results. The ratings are evaluated in above order. In each case, a higher value will signify a more relevant search result.
|
I added a link to this PR from #10372. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was looking for a solution to enhance the usefulness of trac search results. Stock trac seems to sort search results by the date of last change, which might not always be what users expect. Looking for a medium solution between using complete indexing server as suggested in https://trac.edgewall.org/wiki/AdvancedSearch and the current solution, I suggest a medium solution (with regard to both complexity and quality), ordering the results based on occurrence of the search word in page/ticket title, headers and content.
The
ISearchSourceget_search_results()gets an optional sixth value in the return tuple calledorderwhich is supposed to contain a quadtuple which is to be composed ofThe
orderparameter is then used to sort search results. The ratings are evaluated in above order. In each case, a higher value will signify a more relevant search result.