Also and as always with file metadata, “File or Roon or Edit” means your file data gets overwritten should the metadata provider actually provide data for that field unless the field gets fixed to “Prefer file” (Import Settings). Abusing metadata fields to provide content other than the one indicated by it’s name is always at the users risk – what works now, might brake at any time in the future.
Back when I was ripping all my CDs, I started using “Barcode” over the use of UPC or EAN because it can include both, opposed to having to use separate tags depending on if you are using a 12-digit UPC or 13- digit EAN. The only difference is that a UPC is 12 digits because it drops the leading zero from the 13-digit EAN so I it was easier to use “Barcode”. Roon also recognizes Barcode and applies it as the Product Code.
ISRC codes are track identifiers while the UPC/EAN applies to the whole album. Each track on an album has a different ISRC code, so they would not work well for album identifiers. Most of my tracks have ISRC codes already tagged when I purchase an album so I leave them, but they don’t show up in Roon.
I’ve read that thread before also the description of the meta data model, which says under headline ALBUM, that field “Product Code text File or Roon or Edit ISRC, UPC, ASIN, etc.” could be used.
I tried PRODUCTCODE, PRODUCT CODE, PRODUCT - wrong classification is shown unter credits / release information. my import settings for “product code” is “prefer file”.
This is the reason for that topic here …