# Tag for 'releasegroupdisambig'?

**URL:** <https://discourse.beets.io/t/tag-for-releasegroupdisambig/939>\
**Category:** Help\
**Created:** [September 27, 2019, 7:25pm UTC](https://discourse.beets.io/t/tag-for-releasegroupdisambig/939 "2019-09-27T19:25:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Moonbase59](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/moonbase59/32/299_2.png) [@Moonbase59](https://discourse.beets.io/u/Moonbase59)\
**Post date:** [September 27, 2019, 7:25pm UTC](https://discourse.beets.io/t/tag-for-releasegroupdisambig/939/1 "2019-09-27T19:25:13Z")

</div>

I just found out that beets supports release and releasegroup disambiguation, which I also use.

It looks like the tag for ‘releasegroupdisambig’ is ‘RG\_DISAMBIGUATION’, is that correct and consistent for all file types? Also, is it handled case-insensitively?

Unfortunately, Picard calls these ‘\_releasecomment’ and ‘\_releasegroupcomment’ internally, and thus I have tagged many albums with tags ‘releasecomment’ and ‘releasegroupcomment’ (skipping the leading underscore).

Any chance this could be added or somehow unified? Or do I have to rescan and retag my library using ‘R\_DISAMBIGUATION’ and ‘RG\_DISAMBIGUATION’?

---

<div class="post-metadata">

**Author:** ![adrian](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/adrian/32/4_2.png) [@adrian](https://discourse.beets.io/u/adrian)\
**Post date:** [September 28, 2019, 1:29pm UTC](https://discourse.beets.io/t/tag-for-releasegroupdisambig/939/2 "2019-09-28T13:29:24Z")

</div>

Hi—I don’t believe we actually have a tag mapping for the $releasegroupdisambig field. The canonical source of truth for this kind of question, FWIW, is in MediaFile:

> <https://github.com/beetbox/mediafile/blob/master/mediafile.py>

We do have an $albumdisambig mapping, for example:

> <https://github.com/beetbox/mediafile/blob/b6b3520b3f54ccb0a95a10c18366ef857517439d/mediafile.py#L1839-L1845>

But not the one for release groups.

---

<div class="post-metadata">

**Author:** ![Moonbase59](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/moonbase59/32/299_2.png) [@Moonbase59](https://discourse.beets.io/u/Moonbase59)\
**Post date:** [September 29, 2019, 7:50am UTC](https://discourse.beets.io/t/tag-for-releasegroupdisambig/939/3 "2019-09-29T07:50:02Z")

</div>

Thanks for the info. Any objections to involving someone from the Picard team here?

Rationale: I see there is a need for album disambiguation (apart from using the MB album ID), for folder naming use, and I strongly believe everything should be reconstructable from tags, and tags possibly _unified_ so that others could also easily use these, like _Picard_, _Mp3tag_, and _foobar2000_, to name a few.

I’d like to suggest introducing two new ‘pseudo-official’ tags for the Release (=Album) Comment and the Releasegroup Comment. Btw, the reason I decided to use the release group comment is that the release comments are already quite polluted in MB with things like “limited edition” or so, whereas usually a good disambiguation comes from the release group. (Thinking of the [Peter Gabriel albums](https://musicbrainz.org/artist/8e66ea2b-b57b-47d9-8df0-df4630aeb8e5) all named “Peter Gabriel” but nicely separated by the release group comments “Car”, “Scratch”, “Melt” and “Security”, as an example.)

I feel beets’ approach of naming these “the MusicBrainz way” is much better than what I used before, because it clearly puts the tags in the “MusicBrainz” namespace. Ideally, this should of course be supported by the official MusicBrainz tagger, i.e. Picard. And others, if anyhow possible.

I opened ticket [PICARD-1617](https://tickets.metabrainz.org/browse/PICARD-1617) and proposed the same on [Hydrogenaudio](https://hydrogenaud.io/index.php?topic=118230.0) and [Mp3tag](https://community.mp3tag.de/t/tag-mapping-proposed-official-tags-for-album-disambiguation/46576), so this issue can stay in sync.

---

<div class="post-metadata">

**Author:** ![Moonbase59](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/moonbase59/32/299_2.png) [@Moonbase59](https://discourse.beets.io/u/Moonbase59)\
**Post date:** [September 29, 2019, 4:22pm UTC](https://discourse.beets.io/t/tag-for-releasegroupdisambig/939/4 "2019-09-29T16:22:51Z")

</div>

> <https://github.com/beetbox/mediafile/pull/20>

---

<div class="post-metadata">

**Author:** ![adrian](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/adrian/32/4_2.png) [@adrian](https://discourse.beets.io/u/adrian)\
**Post date:** [September 30, 2019, 8:42pm UTC](https://discourse.beets.io/t/tag-for-releasegroupdisambig/939/5 "2019-09-30T20:42:25Z")

</div>

> [@Moonbase59](#):
>
> Thanks for the info. Any objections to involving someone from the Picard team here?

No objection whatsoever! Seems like a good idea. And thanks for opening all those other tickets for relevant software.

---

<div class="post-metadata">

**Author:** ![Moonbase59](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/moonbase59/32/299_2.png) [@Moonbase59](https://discourse.beets.io/u/Moonbase59)\
**Post date:** [September 30, 2019, 9:08pm UTC](https://discourse.beets.io/t/tag-for-releasegroupdisambig/939/6 "2019-09-30T21:08:26Z")

</div>

No problem. I love developing, but combining it with the hobby is best! Insofar I’m also just a user, trying to get the best out of existing software. That’s one of the reasons I love FOSS: working together and improving the world made easy! 🙂