# 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:** 7
**Page:** 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

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [December 30, 2016, 8:32am UTC](https://community.mp3tag.de/t/musicbrainz-field-mappings-not-up-to-date/18567/2 "2016-12-30T08:32:30Z")

</div>

> [@Mihawk90](#):
>
> ... data from MusicBrainz.... tag field mappings used by Mp3tag are a little out of date compared to what MusicBrainz uses now....

THis is how the web source script writes the tags.

There is no "mapping".

MP3tag displays theses field names:  
The standard ones as suggested by the standard  
The user-defined ones that you used  
The ones that you used for manipulation and got imported e.g. by a web-source.

If you reset the field list e.g. in the Convert-Tag-Tag function (click on the button with the right-arrow and select "reset list"), you will see that the non-standard field names are gone.

IMHO this is not a bug but a request to modify the web source.

---

<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, 4:08pm UTC](https://community.mp3tag.de/t/musicbrainz-field-mappings-not-up-to-date/18567/3 "2016-12-30T16:08:46Z")

</div>

Ah OK so the tag-tag converter just shows whatever Field Names have been used previously then, ok 🙂

So this is indeed an "issue" with the websource 🙂

Thanks, I'll post it there and/or update the websource myself to the latest "official" field names 🙂

Didn't even see the "reset list", never needed it so far.

---

<div class="post-metadata">

### Author: ![Douzeju](https://community.mp3tag.de/user_avatar/community.mp3tag.de/douzeju/32/480_2.png) [@Douzeju](https://community.mp3tag.de/u/Douzeju)
#### Post date: [January 10, 2017, 4:21pm UTC](https://community.mp3tag.de/t/musicbrainz-field-mappings-not-up-to-date/18567/4 "2017-01-10T16:21:33Z")

</div>

I was about to create a topic about my problem but after some thoughts it might be linked to what you reported...

I wanted to tag an album of Air using the import tool for MusicBrainz. It worked all well, except it didn't import the year nor the cover of the album, which i found suspect, as it's quite a well known album. ![<_<](https://community.mp3tag.de/uploads/default/original/1X/5996dbb474c88b8f9fc49f09dc3858d081055a2d.gif "<\_<")  
So i gave a look at the web page from which the tool had imported the tags ([here](http://musicbrainz.org/release/25d4d542-bbb8-4f8d-8572-692c6ceab44d)), on which you can see the release year and cover are preset. So i guess this problem comes somewhere from MP3tag, perhaps from where Mihawk90 pointed at !

So yeah.

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [January 10, 2017, 5:48pm UTC](https://community.mp3tag.de/t/musicbrainz-field-mappings-not-up-to-date/18567/5 "2017-01-10T17:48:42Z")

</div>

I think that reports on the benefits and shortcomings of web sources are no bug reports but should be discussed in the web sources part of this forum.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [June 8, 2018, 9:35am UTC](https://community.mp3tag.de/t/musicbrainz-field-mappings-not-up-to-date/18567/6 "2018-06-08T09:35:51Z")

</div>

I've fixed this with the latest [Development Build](https://community.mp3tag.de/t/455) Mp3tag v2.88b.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2018, 2:09pm UTC](https://community.mp3tag.de/t/musicbrainz-field-mappings-not-up-to-date/18567/7 "2018-12-28T14:09:04Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
