Legacy IPTC Data Appearing

[PandDLong]

Somewhere I must have accidentally changed a setting after upgrading... 

I looked at the dashboard and it identifies a number of files with Legacy IPTC data.  I click through and it is all of the files that I have worked on and written back since I upgraded to iMatch 2023.  They are not old files nor from odd cameras, and I checked my "pre-upload to iMatch" copies and they do not have any legacy data.

They are simple JPEG files.   I checked my preferences in Metadata 2 under the JPEG file format and it is still set to "Use Default Settings".

Other suggestions on why this occurred (and thus how I stop it from happening).

Thanks in advance

Michael

[Mario]

IMatch never creates legacy IPTC data but it maintains it, when the target file contains legacy IPTC data.
Make sure you don't accidentally add legacy IPTC data, e.g. via a metadata template, an app or a legacy IPTC tag in a custom Metadata Template layout. Hard to tell what's causing this.

[jch2103]

That can also happen if you get images from 'outside' sources (i.e., not ones you took), and some other software may also add Legacy IPTC metadata. 

[Mario]

Good point.

Basically, when writing back, IMatch checks the metadata of the target file to see if there are any legacy IPTC tags (tags from the IPTC group). If it finds one, it will tell ExifTool to copy XMP->IPTC during write-back.

You can use the "Browser" layout in the Metadata Panel to check for legacy IPTC tags (not confuse them with XMP IPTC / IPTCExt). Or you run the ExifTool command processor on the file with the "list metadata" preset and then search for [iptc] to see if there are any legacy IPTC tags in the file.

[PandDLong]

IMatch never creates legacy IPTC data but it maintains it, when the target file contains legacy IPTC data.
Make sure you don't accidentally add legacy IPTC data, e.g. via a metadata template, an app or a legacy IPTC tag in a custom Metadata Template layout. Hard to tell what's causing this.

This made sense as the cause of the issue.  I went through and looked at every line in panels and templates I used on these files.  Couldn't find anything.

I loaded a few of the same files (from my "pre-iMatch copies") and then went through the process step-by-step.  I first confirmed these files have no legacy data after indexing.

I found the problem line in a metadata template.

When I assign a value to XMP::dc\Rights in a template, the IPTC Application Record for Copyright also gets populated (and then on a write-back, iMatch nicely populates many legacy fields to give the legacy data a rich set of info).

As a further test, I added this tag to a panel and entered it manually - which again populated the legacy data field for Copyright.

Michael

[Mario]

The XMP::dc\rights\Rights, Composite\MWG-Copyright\Copyright and IPTC::ApplicationRecord\116\CopyrightNotice are linked and IMatch should synchronize them.
But IMatch also checks whether or not a file has legacy IPTC data before mapping into legacy IPTC - or at least it should. I'll have a look. Thanks for the info.

[Mario]

I've found an issue that may have caused IMatch to create a legacy IPTC tag when propagating changes between linked tags. I have fixed that for the next release. Thanks for notifying me about this.