{"id":7860,"date":"2025-01-29T15:59:28","date_gmt":"2025-01-29T15:59:28","guid":{"rendered":"https:\/\/iptc.org\/?page_id=7860"},"modified":"2025-01-29T15:59:28","modified_gmt":"2025-01-29T15:59:28","slug":"adobe-custom-metadata-panel-iptc-user-guide","status":"publish","type":"page","link":"https:\/\/iptc.org\/standards\/photo-metadata\/adobe-custom-metadata-panel-iptc-user-guide\/","title":{"rendered":"Adobe Custom Metadata Panel: IPTC User Guide"},"content":{"rendered":"

Guide to Adobe Custom Metadata Panel IPTC fields<\/h1>\n

Last updated: Wednesday 29 January 2025<\/em><\/p>\n

Introduction<\/h2>\n

This document helps using the IPTC Photo All view of the Adobe extension\u00a0Custom Metadata Panel<\/a>. This IPTC view is included in release 2.0.2 and later of this extension.<\/p>\n

The Custom Metadata Panel extension provides a generic technical framework for viewing and editing metadata. A user can install one to many different sets of metadata fields into the Custom Metadata Panel, such a set of fields is called\u00a0view<\/em>\u00a0by the extension. This term is also used in this User Guide.<\/p>\n

About IPTC Photo Metadata<\/h2>\n

The IPTC Photo All<\/strong> view covers all fields of the IPTC Photo Metadata Standard<\/a>, version 2024.1.<\/p>\n

This is the most widely used standard to describe photos, because of its universal acceptance among news agencies, photographers, photo agencies, libraries, museums, and other related industries. It structures and defines metadata properties that allow users to add precise and reliable data about images. Read more about the standard<\/a>.<\/p>\n

Help for some specific fields in the IPTC Photo All view<\/h2>\n

Text fields<\/h3>\n

Three types of text field are used in the IPTC Photo All view:<\/p>\n

    \n
  1. A “simple text field”: Above the field only the field label is shown: type in a text expressing what the field covers – e.g. a headline text into the Headline field.
    \nThis is an example:
    \n\"cmp<\/span><\/li>\n
  2. A “Language Alternative\u00a0*)<\/sup>\u00a0field with x-default only”: Above the field the field label and next to it\u00a0(Default)<\/span>\u00a0(in blue) is shown: this is a field supporting a single text in any language. As only\u00a0(Default)<\/span>\u00a0is shown only a single\u00a0default<\/em>\u00a0text can be set, in the embedded metadata the generic x-default language identifier is associated with the text. Currently this is how such a Language Alternative field is used by a vast majority of imaging software.
    \nThis is an example:
    \n\"cmp<\/span><\/li>\n
  3. A “Language Alternative1<\/sup><\/a>\u00a0field with at least one specific language, one of them is the default language”: Above the field the field label and next to it\u00a0(en)(Default)<\/span>\u00a0(in blue) shown: this is a field supporting text values in different languages in practice. This field requires a text in English and this language is considered as default language among texts in multiple languages.
    \nThis is the Alt Text field as example of the basic look of such a field:\u00a0\"cmp<\/span>
    \nIf you click on “LANGUAGE ALTERNATIVES FOR \u2026\u200b” below this field (if available) a group of additional fields is shown, each one has the same label but a different language identifier: fr = French, es = Spanish, de = German, pt = Portuguese. Fill in a text in the associated language having the same content as the text of (en)(Default).
    \nThis is the same Alt Text field after clicking “LANGUAGE ALTERNATIVES FOR \u2026\u200b”: \"cmp<\/span>
    \nIf “LANGUAGE ALTERANTIVES FOR \u2026\u200b” is not shown, only a single specific language is supported.<\/li>\n<\/ol>\n

    <\/a>1<\/sup>Language Alternative fields – defined by the XMP standard – are able to hold the same textual information in different languages. Each of these texts needs a language identifier like “en” for English or “fr” for French. A special variant is if only the identifier “x-default” is supported: any language can be used, only a single text can be applied.<\/p>\n

    Selecting a value with a drop down<\/h3>\n

    A field supports only a specific value out of a defined list of values (a controlled vocabulary).
    \nSuch a field may show a button like this one\u00a0\"cmp<\/span>\u00a0to the right of the field. Clicking on this button opens the list of defined values: select a single one of them, the selected text will be shown in the field. Beware: you cannot type in a text.<\/p>\n

    Selecting a value from a list of radio buttons<\/h3>\n

    A field supports only a specific value out of a defined list of values (i.e. a controlled vocabulary).<\/p>\n

    Such a field may show below the label a list of radio buttons like:<\/p>\n

    \"cmp<\/span>
    \nEach one is associated with the text of a defined value. You should select one of them. This value will be set as field’s value.<\/p>\n

    GPS Altitude field<\/h3>\n

    This field is used with the structured fields Location Created and Location Shown. By the specification of the underlying XMP format the value is an integer number but it must be expressed as a fraction by 1.<\/p>\n

    Example: you want to save an altitude of 190 metres. You must type in 190\/1<\/em>!<\/p>\n

    Below this field you have to set whether this altitude is above sea level or below sea level (rare, but it may be the case).<\/p>\n

    \"cmp<\/div>\n

    GPS Latitude and GPS Longitude fields<\/h3>\n

    Both fields are used within the structured fields Location Created and Location Shown. These fields express a GPS coordinate using a special format defined by the underlying XMP standard.<\/p>\n

    Example:<\/em> you want to express the longitude coordinate of 16.33064 degrees east of the Greenwich meridian.<\/p>\n

    First you must transform the decimal value to a degrees-minutes-seconds value. The web provides some tools for this purpose, search for “transform decimal coordinates to minutes”.<\/p>\n

    By such a tool 16.33064 degrees are converted to 16 degrees, 19 minutes and 50.3 seconds. This value has to be written in such a GPS field as 16,19.503 and you have to append N for north, S for south, E for east and W for west. Be aware of the different separators: after the degrees a comma, after the minutes a dot.
    \nFinally you have to type in\u00a016,19.503E<\/em><\/p>\n

    \"cmp<\/div>\n

    Help on the best use of IPTC Photo Metadata fields<\/h2>\n

    If you want to know more about how to use all the fields of this Custom Metadata view properly please have a look at the\u00a0IPTC Photo Metadata User Guide<\/a><\/p>\n

    Feedback and Questions<\/h2>\n

    If you want to share feedback on the IPTC Photo All view, or if you want to raise a question about it, please join the\u00a0IPTC Photo Metadata public email forum<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Guide to Adobe Custom Metadata Panel IPTC fields Last updated: Wednesday 29 January 2025 Introduction This document helps using the IPTC Photo All view of the Adobe extension\u00a0Custom Metadata Panel. This IPTC view is included in release 2.0.2 and later of this extension. The Custom Metadata Panel extension provides a generic technical framework for viewing […]<\/p>\n","protected":false},"author":311,"featured_media":0,"parent":22,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"template-two-col.php","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"class_list":["post-7860","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/iptc.org\/wp-json\/wp\/v2\/pages\/7860","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/iptc.org\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/iptc.org\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/iptc.org\/wp-json\/wp\/v2\/users\/311"}],"replies":[{"embeddable":true,"href":"https:\/\/iptc.org\/wp-json\/wp\/v2\/comments?post=7860"}],"version-history":[{"count":5,"href":"https:\/\/iptc.org\/wp-json\/wp\/v2\/pages\/7860\/revisions"}],"predecessor-version":[{"id":7865,"href":"https:\/\/iptc.org\/wp-json\/wp\/v2\/pages\/7860\/revisions\/7865"}],"up":[{"embeddable":true,"href":"https:\/\/iptc.org\/wp-json\/wp\/v2\/pages\/22"}],"wp:attachment":[{"href":"https:\/\/iptc.org\/wp-json\/wp\/v2\/media?parent=7860"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}