Main Menu

old IPTC fields?

Started by carlseibert, July 31, 2018, 07:33:56 PM

Previous topic - Next topic

carlseibert

Does anybody remember IPTC fields called "Content Location Code", or "Reference Number"?

Exiftool understands these fields, but they don't appear in the current IPTC standard. They have come up in the context of a developer I'm helping.

I'm, thinking that they are very old fields that have gone from meaningful to deprecated to just plain deleted over the years. In any case, if anybody knows what they might still be good for, I'll hold off on advising my friends to just delete them from their app.

Otherwise, it's the bit bucket for them. :-)

StarGeek

While I don't have any actual source on details about them, it looks like they weren't part of the IPTC standard when it came to photo metadata.  You can find reference to both them (and a few related fields) in the IPTC Standard Information Interchange Model (IIM) (dated 2008-07-16), they don't appear in the IPTC Standard Photo Metadata 2008  (dated 2008-07-18).

If you do some further searching, you might find something to map it to in XMP.  The namespace according to the first document is Iptc4xmpIIM, but I can't find much useful searching for that.

The IPTC Spec directory appears to be an open directory, so one can dig further into the various specs without search through the IPTC website.
"It didn't work" isn't helpful. What was the exact command used and the output.
Read FAQ #3 and use that cmd
Please use the Code button for exiftool output

Please include your OS/Exiftool version/filetype

carlseibert

Thank you StarGeek!  Especially for that directory address. That will come in very handy.

"Identifies the Envelope Number of a prior envelope to which the current object refers "  Wow. To call these fields obscure would be belittling normal obscure stuff. I think we can live productive lives without these two fields.

That said, I have dealt with a situation where one set of physical envelopes migrates to a different set of physical envelopes and then to a database. So I actually get that. But in 2018, in a streamlined DAM  - nah.