Digital Release with two Bandcamp links: different release, or not?

Tags: #<Tag:0x00007f00bccc1460> #<Tag:0x00007f00bccc12f8>

Recently I noticed that certain releases are available twice on Bandcamp. Examples:

https://paganrecords.bandcamp.com/album/g-d
https://nonopusdei.bandcamp.com/album/g-d

https://godzovwarproductions.bandcamp.com/album/i-i-dalej
https://gruzja.bandcamp.com/album/i-i-dalej

https://godzovwarproductions.bandcamp.com/album/jeszcze-nie-mamy-na-was-pomys-u
https://gruzja.bandcamp.com/album/jeszcze-nie-mamy-na-was-pomys-u

In each case one link from the pair is label.bandcamp.com, and another is bandname.bandcamp.com. The musical content is exactly the same. There can be some subtle differences in artwork, like in the first example.

The question is, should we treat these as different releases in MusicBrainz? Initially I thought these should be separate releases (one on a label, another self-released), but… I don’t know.

What do you think? I guess the question is if the money goes directly to the band or to the label, but how can we know that?

1 Like

If the artwork is (even subtly) different, it should be a new release. I’ve added “double” Bandcamp releases before, one from label and one from artist. (They may also have different barcodes.)

4 Likes

OK, different artwork (even if the difference is slight) clearly makes a distinct release. But what if the attached digital artwork is exactly the same (like both Gruzja albums from my list of examples)?

Another matter: what if the release date in the two Bandcamp pages is the same, but actually it’s not the case? For example, both Bandcamp pages of “I iść dalej” state the release date was February 27th 2019. This is true for the label release, but I know for a fact that the band release appeared fairly recently (a month or two ago).

And how does the concept of a barcode apply to digital releases?

This is not too uncommon, and in general, I’d say this is the same as the album being in both iTunes and Amazon - no need for two releases. That said, if you find out there was an earlier self-release and then the label re-released it, rather than it just being put up on both places with permission of the label, then I’d create a separate release.

4 Likes

With Bandcamp you can find the barcode (when existing) in the source code. Search for upc, here for your examples it’s null.

3 Likes

Can you provide working examples for this? Perhaps we can add it to importer if reliable enough.

5 Likes

Sure, I got this tip from @waxie, see edit #65496559 for example.

4 Likes

Implemented by https://github.com/murdos/musicbrainz-userscripts/commit/f5869e7c95eacf708f914427f3a3063db853ede7

8 Likes

Wow thanks, I feel stupid to don’t ask for it before :slight_smile:

It seems to me it doesn’t work well, I noticed the barcode extracted often matches one “random” release on the page, not a specific one.
So it is very likely UPC prefilled isn’t the one of the release the user is trying to add.

Not that the UPC itself is wrong (it exists, and matches one release), but since we don’t have mean to know which release it matches, I’d rather display it on the page instead of prefilling barcode field.

What do you think?

2 Likes

I’ve already had my suspicion about this before UPC extraction was implemented. TralbumData.current.upc doesn’t necessarily refer to the digital release.

It looks like Bandcamp provides one UPC field only that is used for all sales.

I didn’t finish my observations yet but here is an example:
https://eleniviolaris.bandcamp.com/album/rainstriker
TralbumData.current.upc: "5065002105103"
On CD back cover: 5065002105103

1 Like

I changed the Bandcamp Importer behavior regarding this issue.
It doesn’t add the found UPC in barcode field of the release editor anymore, but it is displayed at the bottom of the release page (near keywords) so the editor can copy it if needed.

3 Likes