IMHO the best solution for all in this case would be if you could add cover art for this release to the cover art archive.
As for Picard and Amazon I am not sure if this could be fixed int this case. Picard is basically just guessing the URL, and I don’t see how this could work in this case. Honestly I think we would probably be better of removing the Amazon cover art provider from core Picard and put it into a plugin.
I really understand what you mean, and I can’t say I don’t share your opinion. But for now, it’s not as easy as putting a link in a field like before.
Could be fixed maybe by implementing the Amazon API instead of the actual URL guessing method ?
Also if Picard Amazon importer becomes deprecated, it’s still possible to add some “king of magic” by adding a button in the website to import the linked Amazon cover into Cover Archive ?
Or maybe just use Cover Archive as a bridge to Amazon, by just referencing the cover art URL in CA ?
As you can see, there’s a lot of things I can imagine to solve the problem. Not to fix Amazon importer in Picard, but to make it easy to use for everyone.
All of those ideas needs to be discuss imo, to find the best way to improve MB and Picard
AFAIK, the reasons this is not already being done, is that using their API means you have to agree to their usage terms, and one those were that the API should be used to promote sales on Amazon or some such (IIRC). I didn’t check whether this is still in there, but this is not something that we’re willing to agree to for Picard currently.