# Support for ITUNESALBUMADVISORY field

**URL:** https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715
**Category:** General Discussion
**Created:** [January 23, 2021, 10:51pm UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715 "2021-01-23T22:51:48Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![djdizzle](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/d/ed8c4c/32.png) [@djdizzle](https://community.mp3tag.de/u/djdizzle)
#### Post date: [January 23, 2021, 10:51pm UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715/1 "2021-01-23T22:51:48Z")

</div>

In relation to this tag Florian, could you also add support for `ITUNESALBUMADVISORY`  
as well? this is linked to the iTunes/Apple Music API under `collectionExplicitness`

---

<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: [January 24, 2021, 6:44am UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715/2 "2021-01-24T06:44:20Z")

</div>

Is it also stored in the tags of the file or only available via Apple Music metadata? If it's in the tags, I'd need to know the atom id (or get my hands on an example file).

---

<div class="post-metadata">

### Author: ![jackpots](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/j/82dd89/32.png) [@jackpots](https://community.mp3tag.de/u/jackpots)
#### Post date: [January 24, 2021, 6:06pm UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715/3 "2021-01-24T18:06:06Z")

</div>

...  
Error. I use the track specific, ITUNESADVISORY,  
without problems.

---

<div class="post-metadata">

### Author: ![Ouargui](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/o/f17d59/32.png) [@Ouargui](https://community.mp3tag.de/u/Ouargui)
#### Post date: [March 14, 2021, 7:34pm UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715/4 "2021-03-14T19:34:55Z")

</div>

[https://code.google.com/archive/p/mp4v2/wikis/iTunesMetadata.wiki](https://code.google.com/archive/p/mp4v2/wikis/iTunesMetadata.wiki)

---

<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: [March 14, 2021, 9:26pm UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715/5 "2021-03-14T21:26:31Z")

</div>

Thanks for the list. Is the field listed anywhere in there?

---

<div class="post-metadata">

### Author: ![Ouargui](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/o/f17d59/32.png) [@Ouargui](https://community.mp3tag.de/u/Ouargui)
#### Post date: [March 16, 2021, 3:38am UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715/6 "2021-03-16T03:38:09Z")

</div>

i don't believe it actually is a thing, Apple flags an album explicit if at least one track is so, this has the complete list of fields iTunes uses, it would be fantastic if they were added in next updates.

---

<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: [March 16, 2021, 8:15am UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715/7 "2021-03-16T08:15:01Z")

</div>

Most of the fields are actually already supported. Have you checked [Mp3tag Help — Tag field mappings](https://docs.mp3tag.de/mapping), especially the list of fields exclusive to MP4?

Anything specific that's missing for you?

---

<div class="post-metadata">

### Author: ![Ouargui](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/o/f17d59/32.png) [@Ouargui](https://community.mp3tag.de/u/Ouargui)
#### Post date: [March 16, 2021, 5:28pm UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715/8 "2021-03-16T17:28:50Z")

</div>

since im using the Apple Music web source which has some additional fields, Artist ID (atID), Composer ID (cmID), Genre ID (geID), Album ID (plID) and iTunes Country Code (sfID)

Edit: also found ISRC is xid

---

<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: [April 5, 2021, 11:25am UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715/9 "2021-04-05T11:25:06Z")

</div>

I've added support for those fields with [Mp3tag v3.06b](https://community.mp3tag.de/t/455).

---

<div class="post-metadata">

### Author: ![Crissov](https://community.mp3tag.de/user_avatar/community.mp3tag.de/crissov/32/6619_2.png) [@Crissov](https://community.mp3tag.de/u/Crissov)
#### Post date: [April 5, 2021, 8:25pm UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715/10 "2021-04-05T20:25:45Z")

</div>

Is `xid ` used for the verbatim ISRC or with a prefix and scheme as specified in the [iTunes LP Specification](https://www.apple.com/nz/itunes/lp-and-extras/docs/Development_Guide.pdf) quoted below?

> ## XID Structure
> 
> An XID is a string composed of three colon-delimited segments:
> 
> 1. A **prefix** specific to the content provider. Content providers who provide content to the iTunes Store each have a specific prefix assigned for use in this manner. All XIDs identifying content from a given content provider should use the same prefix. If you are testing iTunes LP prior to submitting it to the iTunes Store, and you have not yet finalized the identifiers for your content, you may wish to temporarily use the reserved prefix TEST, and combine it with the uuid scheme, described below. When IDs for the content are finalized, you should replace the TEST XIDs with XIDs using a true provider name as a prefix and an XID scheme based on one of the other schemes.
> 2. A **scheme** specifying the type of identifier being used. Supported schemes are described below, with examples of each.
> 3. An **identifier** conforming to the scheme.
> 
> The following are currently-supported XID schemes:
> 
> - **upc** - For content identified with a UPC code.  
> Example: `buenavista:upc:760894712785`
> - **isrc** - International Standard Recording Code for sound recordings and music videos.  
> Example: `SonyBMG:isrc:USSM19922509`
> - **isan** - International Standard Audiovisual Number for video content.  
> Example: `Paramount:isan:0000-0000-6601-0000-4-0000-0000-P`
> - **grid** - Global Release Identifier standard developed by the recording industry.  
> Example: `Warner:grid:A10302B0000978370N`
> - **uuid** - Universally Unique Identifier (RFC 4122); this is the best choice for temporary use while testing iTunes LP. UUIDs can easily be created on demand; for example, by the uuidgen command-line tool on Mac OS X.  
> Example: `TEST:uuid:6F092637-666F-49F6-9F77-978627D50B5A`
> - **vendor\_id** - A content provider’s custom identifier for a piece of content not identified by any of the standards above.  
> Example: `sonypicturesentertainment:vendor_id:DA_VINCI_CODE_EC_2006`

---

<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: [April 6, 2021, 5:50am UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715/11 "2021-04-06T05:50:22Z")

</div>

It's the XID structure with prefix, scheme, and identifier. With ISRC only, the mapping would have been quite straightforward.

---

<div class="post-metadata">

### Author: ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)
#### Post date: [May 6, 2021, 5:50am UTC](https://community.mp3tag.de/t/support-for-itunesalbumadvisory-field/51715/12 "2021-05-06T05:50:36Z")

</div>

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