# MusicBrainz Field Mappings not Up-to-Date

**URL:** https://community.mp3tag.de/t/musicbrainz-field-mappings-not-up-to-date/18567
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [December 30, 2016, 12:53am UTC](https://community.mp3tag.de/t/musicbrainz-field-mappings-not-up-to-date/18567 "2016-12-30T00:53:50Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![Mihawk90](https://community.mp3tag.de/user_avatar/community.mp3tag.de/mihawk90/32/223_2.png) [@Mihawk90](https://community.mp3tag.de/u/Mihawk90)
#### Post date: [December 30, 2016, 12:53am UTC](https://community.mp3tag.de/t/musicbrainz-field-mappings-not-up-to-date/18567/1 "2016-12-30T00:53:50Z")

</div>

Hey there,

I realised this just now when I tagged some files with MusicBrainz Picard and then tried to use another websource using data from MusicBrainz.

Apparently the tag field mappings used by Mp3tag are a little out of date compared to what MusicBrainz uses now.

Files tagged with Picard look like this:  
🙂

Currently it's kind of a pain to work with both Picard and Mp3tag (I have to use Picard for the scanning from time to time which is why I never noticed before)

Picard's Mappings can be found [here](https://picard.musicbrainz.org/docs/mappings/)

Best Regards

---

_[View the full topic](https://community.mp3tag.de/t/musicbrainz-field-mappings-not-up-to-date/18567)._