# Add mappings for more MusicBrainz tags

**URL:** https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846
**Category:** Support
**Created:** [December 11, 2018, 11:55am UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846 "2018-12-11T11:55:57Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![phw](https://community.mp3tag.de/user_avatar/community.mp3tag.de/phw/32/11831_2.png) [@phw](https://community.mp3tag.de/u/phw)
#### Post date: [December 11, 2018, 1:33pm UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/5 "2018-12-11T13:33:56Z")

</div>

> [@LyricsLover](#):
>
> What's the difference between this MusicBrainz tags and TXXX tags in general?

I think this is similar to what was already changed for other MusicBrainz defined tags like `MusicBrainz Artist Id`. These are specifically defined tags with a specific meaning, and their casing should be preserved. MP3Tag already contains a fixed mapping of most of those tags, but not for the ones @culinko mentioned above. See also this older discussion:

> [@Problem when entering MusicBrainz IDs (e.g., MusicBrainz Artist ID)](https://community.mp3tag.de/t/problem-when-entering-musicbrainz-ids-e-g-musicbrainz-artist-id/43258/2):
>
> This is due to a change in v2.89 for the internal mapping of MusicBrainz IDs [2018-06-04] CHG: added mappings for special fields with MusicBrainz IDs for ID3v2 and MP4. ([#18405](https://community.mp3tag.de/t/18405)) With this change, I've added an mapping from internal (written to the tag) to external (displayed in Mp3tag) representation of the MusicBrainz ID fields. This was necessary, because other applications (e.g., MusicBrainz Picard) or libraries (e.g., TagLib) are using different names for those identifiers depending on t…

---

_[View the full topic](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846)._