Spotify plugin overwrites the MB IDs even if we have the correct ones

The Spotify plugin (this may be true for other plugins, but I have not checked them all) currently populates all the fields including the mb_album_id and mb_artist_id with spotify_album_id and spotify_artist_id. This makes sense during the initial import (or when we are only using Spotify as the tag source) when we don’t have the MB ids and we need some IDs to be populated. However, if we initially imported the album with MusicBrainz plugin and the MB ids are correctly populated, Spotify (or any other plugin) should not overwrite the correct MB IDs.

Basically, any plugin should check if the MB ID fields are empty (i.e., initial import) and only then populate those fields. If MB IDs are already present, the plugin should only update the plugin-specific fields. Thus, if Spotify tagger is used after the album was already imported using MB, Spotify should only update the Spotify-specific fields and not incorrectly change the MB ids to Spotify IDs.

[JOJ0]

I think it’s still relevant. Even though there are similar issues open, in here are some useful hints on how it could possibly fixed. HTH

[arsaboo]

I am not even sure how to handle this, so I am going to leave this issue open for now. But given the number of open issues/questions related to this topic, I sincerely hope that we address this issue sooner than later.