Searching for exact matches about mopidy-spotify HOT 6 OPEN

Agree! Should do this differently for the upcoming Mopidy-Spotify 2.0.

from mopidy-spotify.

Do you think there is any merit in doing this in pyspotify 2.0? At least the exact searches bit.

I vaguely remember the mention of an additional higher-level wrapper that did some extra useful stuff (I think this was based around the bug where starred playlists have no name),

from mopidy-spotify.

It's worth considering at least. The immediate issue I can think of is how to make an "exact match" overlay over the existing search work nicely with pagination. If you search for "foo" and ask for 20 results, then you're told that "we found 73 results, here's the first 20" and then there's only 18 in the result, since two wasn't exact matches.

from mopidy-spotify.

mopidy/mopidy#272 seems relevant here. We should consider using artist/albumbrowse instead of or in addition to search for find_exact.

from mopidy-spotify.

To move the entire discussion over here, I'm quoting @trygveaa from mopidy/mopidy#272:

We can first do a search for the query provided. Then traverse either the artist or album results, depending on what the query contained, to find the one that matches exactly (this means that searches will have to be able to return artists and albums, as discussed in #285). At last we do a lookup of the artist or album to retrieve all the tracks.

The benefits of this vs. a normal search:

• We are able to retrieve all the tracks from the artist or album, not just a matching subset of the max number of tracks returned by searches.
• We won't have to do any filtering.

The disadvantage:

• We have to do two queries to Spotify.

from mopidy-spotify.

From the discussion in mopidy/mopidy#727 it sounds like making exact searches exact would help on data quality in the ncmpcpp library view as well.

from mopidy-spotify.