mopidy/mopidy-spotify

Searching for exact matches

Open

#11 opened on Jan 7, 2014

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Python (879 stars) (103 forks)batch import
C-enhancementHelp neededgood first issue

Description

When using MPD's find command the results are supposed to be an exact match of the query but due to limitations in Spotify's searching you actually get partial matches more akin to SQL's LIKE operator.

e.g. Searching for "Opposite of December" gives you results from two albums:

  • "Opposite of December"
  • "The Opposite Of December / Tear From The Red"

This is pretty annoying when you browse an artist's album in MPD clients and get wrong and duplicate tracks entries.

I know of no way to force exact matching in Spotify queries so maybe we could further filter the results returned to us in find_exact()? Similarly, we could also filter by the fields that Spotify queries don't support i.e. track_no. The motivation for this being that much larger amounts of data are returned to the client than are necessary and it just slows things down. This also combines with the first problem and you can get the full track info for loads of unwanted tracks!

Contributor guide