The script seems to tend to create NEW release groups, instead of locating EXISTING release-groups (which discogs calls ‘masters’), to file the individual release into.
Is this avoidable?
If I need to edit the data, after the submission, and MERGE two release groups, or MOVE a release into a different release-group — can you point me to the documentation on how to do this?
(I see the documentation for how to merge two releases, but I want to merge two release-groups, which seems like a different task. Maybe I just missed it.) Thank you.
Let the script the time to search for a MusicBrainz release group that would be linked to its master release.
When it finds one, there is a release group icon next to All versions of this release:
I don’t know who actively develops the Discogs importer, now.
But, it’s very true that most duplicate release groups I see nowadays are created by this.
Maybe the script should wait for the release group search to have ended before enabling the Import button?
I’ve never seen the MB icon appearing next to the MR link on the Discogs release pages using the Linux or Win desktops. Maybe it used to, before the latest discogs release page freaked update? But I can’t remember ever seeing it.
When already at MB import/edit page, the RG box going green automagically is a matter of hit and miss. Just need to be careful and keep checking until we get a warning feature
Try to go to a famous artist release Discogs page you have never been before (because MB links are cached) and wait that all Discogs entities get an MB icon, one after the other each 1 second.
After a while, there should be either a purple icon of just a grey search icon if this Discogs stuff is not linked anywhere in MB.
