Order of search results

Feature description:

This relates to how search results are displayed on the search page. Currently, there are seven selectable options, including “All,” “Album artists,” “Albums,” “Songs,” “Genres,” “All Artists” and “Playlists.” When a search is initiated, results are organised in this specific order. For example, if a user is searching for a playlist, the only way to filter and see Playlist-specific results is by checking the “Playlists” option and the disabling the rest. Otherwise, the search results will be arranged with “Album artists” first, followed by “Albums,” “Songs,” etc.

My suggestion is to allow users to customise the order in which search results are presented or results should automatically be organised based on the most refined result. For example, if a keyword is highly specific to some genre, the genre should appear first and the rest after it. Typically, the search results prioritise ‘Albums’ and ‘Songs’, despite the lack of specificity in these results.

Problem solved:

The issue I’m encountering, probably related to Emby, is that the search results aren’t as refined as they should be. For example, when I search specifically for a playlist, tracks from songs and albums (I have check marked these three options) are listed first and the relevant playlist appears at the very end. While a workaround exists where I can uncheck the other options and select only “Playlists” during each search, this is not a practical long-term solution.

Brought benefits:

The search results with the highest level of accuracy and specificity will get priority.

Other application solutions:

 

 

Additional description and context:

 

 

Screenshots / Mockup:

    

And how do you define that refined stuff? Or that a keyword is more likely to be genre or playlist or anything else? (And that of course is the 128 languages that Play Store support) …

The only improvements that could be made would require mixing all the results and loading everything in memory + do complex fuzzy matching.
Then imagine that on a large 800 000 songs library with 50 000 artists and 120 000 albums and searching “the” the device explode.

TL;DR this is not possible, to search something specific you can and should directly use the text filter in each page that is faster and more efficient.

1 Like

What I meant by “refined” was the result most closely matching the search keyword. Thank you for explaining the complexities involved, I understand that I didn’t consider this when suggesting refining the result as a second, automatic option for adjusting the search order.

As for your suggestion about using each page, I’d like your thoughts on having a dedicated page for search settings page, such as “Settings/Interface/Page Settings,” where users can already manage six page-specific settings, from “Home page” to “Playlist page”. What do you think about the seventh option for the Settings page where users can manually define the search order themselves, as initially suggested as manual option?

Besides the “All” option, the search page includes six additional options, ranging from “Album artists” to “Playlist.” A settings page could allow users to customise the display order of search results. For example, changing the number 2 option of “Album artists” with the number 7 option of “Playlists” . What’s your opinion on this?

As said this is too much of a niche issue.

Either you know what you are searching for and you just check what you want or use the filter in the corresponding page. Else you don’t know and the order does not really matter either.

Alright, I understand your point and I’m open to your suggestion, but I also want to reiterate that it’s not a matter of not knowing what to search for. It’s more of a niche situation, as you said, and I’ll manage it. Thanks again for your support.