Reported by DontMindMe:
Don’t know if this is a known issue. https://harmony.pulsewidth.org.uk/release?url=https%3A%2F%2Fopen.spotify.com%2Falbum%2F5gfhI52cbO33uP7uoECGBB>in=®ion=us&musicbrainz=&deezer=&itunes=&spotify=&tidal=&qobuz=
Release 16c6af05-bcb3-42b7-8f2b-a53c11589047 is already linked to this Spotify / iTunes / Qobuz release (add to lookup)
The problem is, that’s a release group MBID, not an release. I kept clicking add to lookup over and over wondering why it wasn’t working… oops. Then I clicked the MBID to see the problem.
Release group “LUMEZX” by LUMEZX - MusicBrainz
I won’t edit the release or RG so you can test with that.
There are all kind of URLs linked to the release group which belong at the release level (or track or artist level even). Harmony happily accepts any MBIDs which are linked to that URL on MB, even if it should only be interested in release-URL relationships.
Because it is impossible to filter by entity type in the MBID resolver itself since we lookup URLs of all entity types at once, we probably would have to store the type inside the MBID cache.
Reported by DontMindMe:
There are all kind of URLs linked to the release group which belong at the release level (or track or artist level even). Harmony happily accepts any MBIDs which are linked to that URL on MB, even if it should only be interested in release-URL relationships.
Because it is impossible to filter by entity type in the MBID resolver itself since we lookup URLs of all entity types at once, we probably would have to store the type inside the MBID cache.