Display of non-standart XMP-Data

[voronwe]

Hi
I have some files which includes XMP-Metadata which starts with "xGMG".
I can see this Data in the Raw Data viewer of Photoshop, as well as in the XMP-Viewer of XnView

However, I do not see them in the MetaData-Browser of IMatch and so far I could not find a way to enter a tag manually (not taken from a dropdown-Menu).
Is there a way to add such Tags to the Viewer?

Attached is a file with these entries.
It is zipped because it is a *.tiff

[Mario]

IMatch knows all XMP namsepaces ExifTool knows about: https://exiftool.org/TagNames/XMP.html, which are currently about 80, including many proprietary XMP namespaces introduced by applications and services.

When I ingest the TIFF file, I see the data from the (unknown) xGMG namespace in XMP::other when I switch the Metadata Panel to the Browser layout. So the data has been ingested, whether it is useful or not.

This means that ExifTool did not deliver the namespace or the tags in that namespace when IMatch queried information about all supported groups and tags. Which is the base for the Tag Manager and how IMatch imports and stores metadata in the database.

I have never heard about xGMG or where it comes from or what it contains.
If you want ExifTool to support another proprietary XMP namespace, contact Phil via the ExifTool community and provide information about the namespace, the vendor/creator, documentation etc.

[voronwe]

Thanks for the fast answer.

I do not see this XMP::other. in the Metadata Panel. Is there some special setting I'm missing?

I see only

• EXIF
• IPTC ApplicationRecord
• IPT EnvelopeRecord
• XMP Dublin Core
• XMP Media Management
• XMP Photoshop
• XMP TIFF
• XMP exif
• XMP x
• XMP xmp

Is there some setting I have missed?

GMG is entered by me, we are using it for some special recordings. It is nothing which needs to be put to ExifTool (especially as I can already read it with the command-line Exif-Tool).
But as this is the benefit of XMP, that you can write into the file whatever Data you want, I would only like to see what is the best way to get such data displayed in IMatch.
There is a lot of stuff out there which is only needed for a very limited circle of people.
And the point here is not what to do with data, it is just showing it

[voronwe]

Thanks for the fast answer.

I do not see this XMP::other. in the Metadata Panel. Is there some special setting I'm missing?

I see only

• EXIF
• IPTC ApplicationRecord
• IPT EnvelopeRecord
• XMP Dublin Core
• XMP Media Management
• XMP Photoshop
• XMP TIFF
• XMP exif
• XMP x
• XMP xmp

Is there some setting I have missed?

GMG is entered by me, we are using it for some special recordings. It is nothing which needs to be put to ExifTool (especially as I can already read it with the command-line Exif-Tool).
But as this is the benefit of XMP, that you can write into the file whatever Data you want, I would only like to see what is the best way to get such data displayed in IMatch.
There is a lot of stuff out there which is only needed for a very limited circle of people.
And the point here is not what to do with data, it is just showing it

PS: I'm still using 2023.14.2. - so if this can only be shown in the lastest Version, I'm also fine with it

[Mario]

Please don't quote so much or yourself. It makes your posts hard to read.

Make sure XMP other is enabled in Tag Manager See help system for details.
XMP other is a "data dump" and not imported by default, I believe.

GMG is entered by me, we are using it for some special recordings.

You add user-defined XMP tags, on top of the thousands of XMP tags already available for all kinds of images, video and audio recordings? All supported and documented?

For audio recordings and similar, the Adobe Dynamic Media namespace in XMP is usually the first choice.

But as this is the benefit of XMP, that you can write into the file whatever Data you want, I

Maybe. But should you?
You see already that inventing your own tags causes issues. ExifTool will list your user-defined tags by their name in the command line product, but since they are not standardized, ExifTool has no knowledge about their meaning, data type, whatever, it will not list them as supported groups and tags, IMatch does not know them and ExifTool probably throws them just into XMP other:x as text to somehow provide them to IMatch.

There is a lot of stuff out there which is only needed for a very limited circle of people. 

But then these people should not expert support for their custom metadata in applications, I guess.

Even such rare namespaces like GUANO metadata, which is used by a quite small number of scientists, is documented and supported by ExifTool.

There are dozens of XMP namespaces for the image industry, audio, video and film industry, news industry. All well-documented and widely supported. I find it better to use one of these.

[voronwe]

That works, thanks

To point it out: It is not important that IMatch knows what this data mean, it was only to know whether it can be found and displayed - And that is working now.

I do not want to go deeper into this discussion. There are reasons why we do it exactly that way, the data is only needed in a hyperspecific area for one specific software.
The point is:

• xmp has this feature
• If we store data that way, it will not harm the image itself, if a software can not read the tag, it just ignores it
• There is a way that we can read this data with tools like ExifTool and IMatch, even if this tool does not understand the underlaying data at all - Isn't that nice?
• It would probably leads to more problems when I would re- (and probably misuse) XMP-Tags which were defined for other reasons - this way we keep it clean and live in our small little box not harming the outside

My point was only: Is it possible for IMatch to display some completely unknown XMP-Tags? And here we are: It is possible and that is great.
Thanks