The expected result is that the following post would at least be somewhere among the search results (Arguably, it should be among the top results, because it is probably the forum’s most liked post containing the search string, it definitely is the most liked post in its topic):
But the actual result is that this post does not come up in the search results at all. The post is obviously indexed with the search term because when I navigate to the Benchmarking different storage providers topic and search for “hubic” there, it is found.
But! This is only the case if there is an actual 501st post that is being cut off. If there are only a few posts that contain the search string (as is the case in my example), then the displayed search results should be identical regardless of the sorting order. Discourse clearly is not doing that because in the OP example, the number of hits actually differs, depending on the sort order. I don’t understand it.
To put it in more UX terms: discourse says at the end of maybe two dozen hits: “No more results found” which is either trivial (because we’re at the end of the results list) or wrong (because there clearly are more posts containing the search term).
In the old days, when discourse limited the total number of hits and cut off everything below the top whatever-it-was, I can see But
That is not how search works — the most liked webpage with the most Facebook likes does not automatically get the highest search ranking. If you want ordering by likes, then select that in your search…
Why do you think that? Never mind how popular or well-liked the post in question is. And right now, I don’t care whether that post ranks high or low among the search results. I just want it to show up. Regardless of sorting order. Because there are just a few dozen posts containing the search term. Why not show all of them?
Let me make this explicit: out of the 5 ways of sorting search results, the post only shows up in two of them:
Relevance: not listed
Latest posts: listed
Most liked: listed
Most viewed: not listed
Latest topic: not listed
Only that I had the feeling you weren’t happy with the default sort order.
For experienced members, they could adjust the sort preference to better find what they’re looking for. But for a newer member that was searching for the “best” post, they might not think to try different sort filters and not see the result you hope they’d see.
If this is correct, I think there should be some way to have a default sort filter other than by relevance.