# How to handle re-release by a different label

**URL:** https://community.metabrainz.org/t/how-to-handle-re-release-by-a-different-label/154797
**Category:** MusicBrainz
**Tags:** release, musicbrainz
**Created:** [October 16, 2016, 10:05am UTC](https://community.metabrainz.org/t/how-to-handle-re-release-by-a-different-label/154797 "2016-10-16T10:05:20Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![iantresman](https://community.metabrainz.org/user_avatar/community.metabrainz.org/iantresman/32/4510_2.png) [@iantresman](https://community.metabrainz.org/u/iantresman)
#### Post date: [October 16, 2016, 10:05am UTC](https://community.metabrainz.org/t/how-to-handle-re-release-by-a-different-label/154797/1 "2016-10-16T10:05:21Z")

</div>

This CD “Towards The Light” was:

1. [First released in 1998 by Eclectic Music Productions](https://www.discogs.com/Rob-Buckland-Towards-The-Light/release/5653038)
2. [Re-released in 2005 by Quartz](http://www.robbuckland.com/content/towards-light)

- Do I create two separate releases, and duplicate their tracks, just changing the label information? I don’t think there has been any re-mastering.
- Is there a relationship option to relate one to the other?

---

<div class="post-metadata">

### Author: ![HibiscusKazeneko](https://community.metabrainz.org/letter_avatar_proxy/v4/letter/h/3da27b/32.png) [@HibiscusKazeneko](https://community.metabrainz.org/u/HibiscusKazeneko)
#### Post date: [October 16, 2016, 11:59am UTC](https://community.metabrainz.org/t/how-to-handle-re-release-by-a-different-label/154797/2 "2016-10-16T11:59:02Z")

</div>

Yes, you should create 2 releases, reusing any data that is the same between the two (track listings, recordings, etc.).  
[Here is the list of release-release relationships we have.](https://musicbrainz.org/relationships/release-release) We don’t have a “reissue” relationship in large part because it really isn’t necessary to link simple reissues together via a relationship: if they’re in the same release group, one can easily tell that they’re reissues.

---

<div class="post-metadata">

### Author: ![reosarevok](https://community.metabrainz.org/user_avatar/community.metabrainz.org/reosarevok/32/69228_2.png) [@reosarevok](https://community.metabrainz.org/u/reosarevok)
#### Post date: [October 17, 2016, 3:22pm UTC](https://community.metabrainz.org/t/how-to-handle-re-release-by-a-different-label/154797/3 "2016-10-17T15:22:00Z")

</div>

Keep in mind that they should share the same recordings 🙂 But that’s the default when duplicating releases, so it should be ok!

---

<div class="post-metadata">

### Author: ![iantresman](https://community.metabrainz.org/user_avatar/community.metabrainz.org/iantresman/32/4510_2.png) [@iantresman](https://community.metabrainz.org/u/iantresman)
#### Post date: [October 17, 2016, 3:54pm UTC](https://community.metabrainz.org/t/how-to-handle-re-release-by-a-different-label/154797/4 "2016-10-17T15:54:58Z")

</div>

> [@reosarevok](#):
>
> duplicating releases

It would be nice to have a Duplicate option, which begins a “Create Release” populated with the selected release.

---

<div class="post-metadata">

### Author: ![aerozol](https://community.metabrainz.org/user_avatar/community.metabrainz.org/aerozol/32/116_2.png) [@aerozol](https://community.metabrainz.org/u/aerozol)
#### Post date: [October 17, 2016, 8:58pm UTC](https://community.metabrainz.org/t/how-to-handle-re-release-by-a-different-label/154797/5 "2016-10-17T20:58:25Z")

</div>

If you go into the release group, and hit ‘add release’, it should fill the title field, and then you are later given the option of using the tracklist/recordings from existing releases.

What other fields would you like to see filled? Stuff like ‘label’ and ‘release date’ I would prefer not to pre-fill as it’s going to vary, and people are going to accidentally duplicate it.

It’s probably more an issue of the UI not really making it clear that you can re-use a lot of elements easily?

---

<div class="post-metadata">

### Author: ![iantresman](https://community.metabrainz.org/user_avatar/community.metabrainz.org/iantresman/32/4510_2.png) [@iantresman](https://community.metabrainz.org/u/iantresman)
#### Post date: [October 17, 2016, 9:14pm UTC](https://community.metabrainz.org/t/how-to-handle-re-release-by-a-different-label/154797/6 "2016-10-17T21:14:05Z")

</div>

Ah ha! That’s what that does! Just what I wanted. It duplicates nicely.

---

<div class="post-metadata">

### Author: ![jesus2099](https://community.metabrainz.org/user_avatar/community.metabrainz.org/jesus2099/32/36_2.png) [@jesus2099](https://community.metabrainz.org/u/jesus2099)
#### Post date: [October 18, 2016, 6:43am UTC](https://community.metabrainz.org/t/how-to-handle-re-release-by-a-different-label/154797/7 "2016-10-18T06:43:51Z")

</div>

> [@iantresman](#):
>
> > [@reosarevok](#):
> >
> > duplicating releases
> 
> It would be nice to have a Duplicate option, which begins a “Create Release” populated with the selected release.

There is this feature in that user script called [SUPER TURBO](https://community.metabrainz.org/t/big-script-called-mb-super-mind-control-x-turbo/63568), check out its settings panel, look for CLONE\_RELEASE 3 or 4 options, then it appears in the **Editing** menu. But it will not clone releases relationships.
