IPTC / XMP fields not mapped

[Erik Bachmann]

I intend to update my photos using JSON templates. But I've come across a couple of puzzles that I cannot understand.

According to TagNames

• Writer-Editor is an IPTC field (122)
• captionWriter is an XMP family 1 group field

But IPTC 2019 Schema states that the name is captionWriter and there is no Writer-Editor


And likewise TagNames

Code Select Expand

120 Caption-Abstract
While IPTC 2019 Schema  states that captions is a part of Description

Apps like xnView writes to:

Code Select Expand

  "Description": "Caption xn",
  "Caption-Abstract": "Caption xn",
And Geosetter writes to:

Code Select Expand

  "ImageDescription": "Caption geo",
  "Caption-Abstract": "Caption geo",
  "Description": "Caption geo",

Is there a way to "map to relevant fields" ??

[StarGeek]

You're looking at only the json schema.  You want to be looking at the full IPTC Photo Metadata Standard.  That will show you the relationships between IPTC IIM/Legacy, XMP, and Json.

[Erik Bachmann]

Thanks, but it does no help me mapping the fields.

According to the spec. the fieldname is

Code Select Expand

Description

Label	Caption/Description
XMP Specs	dc:description
IIM Specs	Caption/Abstract
JSON Specs	description

Does this mean that I have to manually replicate data to the three other variant tags?

[StarGeek]

I have no idea what you're doing with the json file, but if you want to actually write the data into the image file, you would write it to XMP:Description and optionally to IPTC:Caption-Abstract. Though I recommend just writing to XMP tags unless your workflow requires IPTC tags.

There's no standard place in an image file to write json data.

[Erik Bachmann]

I have no idea what you're doing with the json file, but..

  I'm trying to script updates of my pictures. Like inserting standard Copyright, Caption Writer etc. which are the same for all my pictures.

I'm more compfortable with JSON than various CLI tags that requires hacks on qoutes, percent and extened characters as well as problems with character sets in general (Windows does NOT handle UTF-8 well).

But to sum this up: I have to duplicate the tags in JSON to support IPTC, XMP etc.