Is there a reference showing which photo editors preserve specific metadata fields?
Asked 12/23/2017
2 views
2 answers
0
I'm building a workflow to keep metadata in derivative image files synchronized with a master file or its sidecars. For this to work well, I’d like to store a unique identifier in metadata rather than in keywords.
What I’m looking for is a reference or comparison chart showing which metadata fields are preserved, ignored, or rewritten by major photo editing and cataloging applications. Ideally this would cover EXIF, IPTC, and XMP fields, and whether support differs between editors, DAM/catalog tools, and sidecar-based workflows.
Are there any known resources that consolidate this information?
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
8y ago
2 Answers
1
About the unique image ID thing: One solution that could work would be to use a unique number and write it in all files - and perhaps add a f0f0f0 (or something like that) to the original file:
01234567890123456789f0f0f0: the original file01234567890123456789: any of the derivative files
For the unique number, you would either need some kind of database - or any other way to provide unique/consecutive numbers. You could, for example, calculate the hash of the original file - be it SHA1, SHA-256 or even MD5 - and then write that hash into whatever EXIF-/IPTC-/XMP-field you like.
Note that if you change some none-sidecar data (EXIF, IPTC) later on, the hash will change, too - so therefore, it would be best too calculate it as soon as possible, or at least it requires you to know that re-calculating the unique field later on (e.g. because you accidentally deleted it) will lead to a new hash.
As to what field would be best: I do not think there is a definitive answer. Write it to any of the fields that is prominent in all the programs you use at the moment - and perhaps in some of the not-so prominent ones, too. That way, you can always copy it to some other fields later on if needed, and also, you have a backup of the actual data if something bad happens to one field.
I would take one string-able field of each supplied metadata-standard - so one for EXIF, one for IPTC and optionally, one for XMP.
Originally by user69369. Source · Licensed CC BY-SA 4.0
user69369
8y ago
0
Generated from our catalog & community — verify before relying on it.
There doesn’t appear to be a single comprehensive, up-to-date reference covering exactly which metadata fields every major editor or DAM preserves.
From the answers, the closest resources are partial comparisons:
- IPTC’s software support pages for IPTC metadata support
- Wikipedia’s comparison of metadata editors
- Older cataloging software comparison articles
- Real-world reports of metadata conflicts between specific programs
So the practical answer is: no definitive master list was identified; only partial, dated, or tool-specific references exist.
For your unique-ID workflow, one suggested approach is to generate your own unique value—such as a database-assigned ID or a file hash—and write it into a metadata field you control. A hash can work well, but be aware it changes if embedded metadata changes later, so it should be calculated at a stable point in your workflow.
Also, ExifTool and ImageMagick are useful for inspecting and copying metadata across many file formats, which can help you test how specific applications treat your chosen field.
Recommended products
UniqueBot
AI8y ago
Your Answer
Related Questions
What digital asset management software is available on Linux for organizing photos?
What does the EXIF "Image Unique ID" field mean, and what is it used for?
How can I make Darktable reload updated XMP metadata from digiKam?
Where can I find a glossary of EXIF and photo metadata terms?
Which image metadata fields can help identify the camera or creator?