Hi,
How to avoid overwriting IPTC data when using XMP inject?
Best Regards Ulrik
How to avoid overwriting IPTC data when using XMP inject?
-
- Member
- Posts: 93
- Joined: Fri Jul 08, 2011 10:31 am
- Location: The Netherlands
Re: How to avoid overwriting IPTC data when using XMP inject?
Never used XMP-data, but i guess you could first pickup the entire xmp-data. Then modify it and inject it.
Re: How to avoid overwriting IPTC data when using XMP inject?
If you want to add to the existing data just use the existing data as a variable to insert before the new value.
Example:
If the existing dc.subject is "London" and you want to keep that, but add "United Kingdom" the variable to insert would be:
[Metadata.Text:Path="dc:subject/*[1]"], United Kingdom
Example:
If the existing dc.subject is "London" and you want to keep that, but add "United Kingdom" the variable to insert would be:
[Metadata.Text:Path="dc:subject/*[1]"], United Kingdom
Re: How to avoid overwriting IPTC data when using XMP inject?
Apparently there is a bug that prevents my suggested solution from working on Windows. It works fine on Mac, where the injected XMP data is added to the existing. On Windows, however, the existing data is not preserved and only the newly added data will be visible.
It has been reported to Enfocus support and will be fixed in Switch 2019.
As a workaround until this has been fixed, this is what you can do. First read the old value from XMP and store it in job's private data and then use XMP inject element that reads the value from the private data.
It has been reported to Enfocus support and will be fixed in Switch 2019.
As a workaround until this has been fixed, this is what you can do. First read the old value from XMP and store it in job's private data and then use XMP inject element that reads the value from the private data.
Re: How to avoid overwriting IPTC data when using XMP inject?
Thanks for your feedback I will try with private data.
Re: How to avoid overwriting IPTC data when using XMP inject?
Thanks for your feedback I will try with private data.