One feature I miss from spotify, although clearly not essential, but that I keep coming back to, is being able to display some trivia about artists.
There are several services that could be used:
discogs
lastfm
Metabrainz (thanks @Matthias_Meulien , I found out about this from you previous post here).
I’ll probably end up giving a try on this by writing a generic extension for this, although initial experiments show that this will never be perfect, esp. for artists that have homonyms.
Ah right, last.fm seems very furnished as well. I feared their dev account were manually reviewed, but it seems they are not after all. And their search seems to be a bit more effective, sorting by relevance.
If the music files have tags with MBID (Musicbrainz identifier) then it’s non-ambiguous. This is what was implemented in Argos.
Ha didn’t know that was a thing ! I’m mostly listening music from tidal though, so I can’t use that. I was considering building a db of id associations, but that’s the kind of thing that is hard to maintain…
Note also that the Troi recommendation engine from Musicbrainz devs implements a fuzzy index that could be reused to dynamically deduce MBIDs from artist and track names.
Would be nice to be able to automagically bind MBIDs to tracks in Mopidy!
Could work out, but this only works for releases, so it’d need to go idal artist → Tidal album → MusicBrainz album → MusicBrainz artist.
I’ll start by fetching data from last.fm, and see how it compares with what I can find from metabrainz in practice.
I realized that metabrainz does not store any artist bio / description, which is mostly what I was looking for, and Wikipedia data is not the best as well, as it’s purpose is more being factual than giving a short description of what a band is about.
Would adding a bio : string field to our existing Artist model suffice for what you’re looking for? Although unsure how some backend (e.g. Mopidy-Spotify) would be able to populate this field without calling out to an 3rd party service, Spotify’s API doesn’t provide this data as far as I remember. And we no wouldn’t want every backend reimplenting a metabrainz lookup system. Not sure how this would best fit.
Honestly I’m not sure it’s worth changing the models for that now, we can start experimenting with the different data sources first:
see what we can get in different usecases
see how that can be integrated in the frontends
For now, beside bio, what could be nice:
artist specific images
period of activity (this is displayed in lastFm, I’m not sure exactly where this info comes from, but this could be computed with first and last release e.g.)