To enable anybody in testing a software’s interoperability IPTC defines three tests and what IPTC expects as results – find all below.<\/p>\r\n\r\n\r\n
Executing the tests and comparing the results with IPTC’s expectations helps to evaluate the metadata reliability of a software in a supply chain.<\/p>\r\n\r\n\r\n
How the IPTC Interoperability Tests can be used<\/h3>\r\n\r\n\r\n\r\n\t- Select a piece of software that you want to test and you can use for testing purposes.<\/li>\r\n\t
- Execute the tests #1, #2, #3 as you are interested in the results.\r\n\r\n
\r\n\t- Test #1<\/a>: Do field labels align to the IPTC definition?<\/li>\r\n\t
- Test #2<\/a>: Does the software read and write embedded metadata correctly?<\/li>\r\n\t
- Test #3<\/a>: Which IPTC fields are supported by the software – and which are not?<\/li>\r\n<\/ul>\r\n<\/li>\r\n\t
- Compare your results of each test with the “what IPTC expects as test result” section of the test description, and draw your conclusions about the interoperability quality of the software.<\/li>\r\n\t
- You may contact the maker of the software and ask about differences between your test results and IPTC’s expectations.<\/li>\r\n\t
- You may also contact IPTC: Use the Contact Us page<\/a> on this site.<\/li>\r\n<\/ul>\r\n\r\n\r\n
Terminology used show\/hide more details of this section<\/a><\/small><\/h3>\r\n\r\n\r\n\r\n\r\n\t- software<\/strong>: an application used for viewing and\/or editing IPTC photo metadata. This could be an application on a computer or software on a server and on a client computer to be considered as a single software system – typically Digital Asset Management (DAM) or Media Asset Management (MAM) systems. And it could be a web content management system rescaling image files which may have an impact on embedded photo metadata.<\/li>\r\n\t
- metadata user interface<\/strong> and\/or metadata panel<\/strong>: the full user interface or a part of the user interface of the software showing metadata fields (labels and their values) and supporting to edit the values.<\/li>\r\n<\/ul>\r\n<\/div>\r\n\r\n\r\n
Metadata field <\/strong>or metadata property<\/strong>: an element of metadata made for a specific purpose, e.g. to hold the date and time of creating the image, name of who created the image, describing what the image shows or who owns the copyright of the image. Field <\/em>is the term used primarily by users of the software, property <\/em>is the term primarily used by metadata standards and makers of the software, in fact they are synonyms.
\r\nFor the test guideline below we use the term field<\/em>.<\/p>\r\n\r\n\r\nTest #1: Do field labels align to the IPTC definition?<\/h2>\r\n\r\n\r\n
For filling in the value of a metadata field a user should know for what kind of information this field is made. For IPTC fields this is defined by the IPTC Photo Metadata Standard<\/a>. The first – and in many cases the only – helper on a metadata user interface is the field label. It is shown close to where you can see or fill in the value and tells with a single or a few words what should be filled into the field or what the field shows.
\r\nThis test checks if the label of a field in the tested software aligns with the IPTC definition.<\/strong><\/p>\r\n\r\n\r\nTest outline<\/h3>\r\n\r\n\r\n
The IPTC has created a reference image file with all metadata fields defined by the IPTC standard and almost each field has its IPTC name as value (only very short or numeric values are different). This name is also used in the IPTC standard document. You should load this file in the to-be-tested software and check with your eyes on the software’s metadata panel(s): does the shown field value – the IPTC field name – tell (almost) the same as the label of this field on the panel.<\/p>\r\n\r\n\r\n
Test procedure, step by step show\/hide this section<\/a><\/small><\/h3>\r\n\r\n\r\n\r\n\r\n\r\n\r\n\t- Download the Standard 2021.1 Reference Image file <\/a> (see also the IPTC Photo Metadata Standard page<\/a>).<\/li>\r\n\t
- Load, import, ingest this file into the to-be-tested software.<\/li>\r\n\t
- Activate the photo metadata panel(s) of the to-be-tested software. Select, if required, the IPTC fields.<\/li>\r\n\t
- Compare for each field: does the field’s label tell the same, or at least something very similar, as the shown value of the field, this is the name of the field defined by IPTC.
\r\nThis may look like: ![\"\"](\"https:\/\/iptc.org\/wp-content\/uploads\/2021\/07\/UIpanel_propLabelValue_AdobeLR-01.jpg\")
<\/li>\r\n\t - Record if the field’s label and the IPTC name in the value do not <\/span>align:
\r\n– by writing down the field’s label and the IPTC name shown as the field’s value
\r\n– by taking a screenshot of the whole metadata panel or at least this region of the panel.<\/li>\r\n<\/ol>\r\n<\/div>\r\n\r\n\r\n <\/p>\r\n<\/div>\r\n<\/div>\r\n\r\n\r\n
What IPTC expects as test result<\/h3>\r\n\r\n\r\n
Each IPTC Photo Metadata field has a definition of its semantics and a corresponding recommended label in English. Therefore IPTC expects that any label of an IPTC property is either identical to the the field’s name or label in English as defined by IPTC or only a slight modification of it<\/strong>. For a label in a different language the translation should reflect what IPTC defined as kind of information of the field.<\/p>\r\n\r\n\r\nTest #2: Does the software read and write embedded metadata correctly?<\/h2>\r\n\r\n\r\n
Each software supporting photo metadata implements a small metadata workflow: the embedded metadata is read from the image file, the read field values are assigned to corresponding fields on the metadata panel. If the field values can be edited each one has to be assigned to the corresponding IPTC field(s) and finally all fields should be embedded into the image file correctly.
\r\nThis test checks if software used for this metadata workflow is reading and writing values correctly.<\/strong>
\r\n(Note: some desktop software and most DAM\/MAM systems read the metadata into a local database and the metadata is embedded into in image file only by an export action. IPTC considers this as the internal metadata management of software which should align to this outlined metadata workflow: the metadata fields should be read and saved correctly.)<\/p>\r\n\r\n\r\nTest outline<\/h3>\r\n\r\n\r\n
IPTC has a reference image file with all metadata fields defined by the IPTC standard and each field has a specific value. You should load this file in the to-be-tested software, edit (= change) the values of some fields and save all metadata to the image file. This file should be uploaded to the IPTC Interoperability Test site and “Test #2” should be executed there. The generated test result shows:
\r\n1. If the intentionally edited IPTC files have a value different to the IPTC reference image file, as expected, or still the same.
\r\n2. If other IPTC fields than the ones edited by you have unexpectedly a value different to the IPTC reference image file. (Possible cases: changed value, no value.)<\/p>\r\n\r\n\r\n
Test procedure, step by step show\/hide this section<\/a><\/small><\/h3>\r\n\r\n\r\n\r\n\r\n\t- Download the Standard 2021.1 Reference Image file <\/a>\u00a0– Note as of 6 June 2022: if you have a previously downloaded Reference Image file download it again now<\/span>, a few details were improved and using the old version on the Interoperability Test site would show wrong results!
\r\n(See also the IPTC Photo Metadata Standard page<\/a>). Create a copy of the file and rename it to something like “softwareA-test2-1.jpg”.<\/li>\r\n\t- Load, import, ingest this file into the to-be-tested software.<\/li>\r\n\t
- Activate the photo metadata panel(s) of the to-be-tested software. Select, if required, the IPTC fields.<\/li>\r\n\t
- Change the values of some fields. The IPTC Interoperability Test site supports changed values of these fields in the test result:\r\n\r\n
\r\n\t- Description\/Caption (an IPTC Core field with a text value)<\/li>\r\n\t
- Keywords (an IPTC Core field with optionally multiple occurrences, each with a text value)<\/li>\r\n\t
- Rights Usage Terms (an IPTC Core field with a text value)<\/li>\r\n\t
- Image Creator (an IPTC Extension field with sub-fields, not the same as the Creator field)<\/li>\r\n\t
- Location Created (an IPTC Extension field with sub-fields)<\/li>\r\n\t
- Copyright URL\/Web Statement of Rights (an IPTC Extension field with a text value)<\/li>\r\n<\/ol>\r\n<\/li>\r\n\t
- Save the metadata to this loaded image file. (May require an export action.)<\/li>\r\n\t
- Go to the IPTC Photo Metadata Interoperability Test site<\/a><\/li>\r\n\t
- Select as “local image file” the file you have saved\/exported in step 5.<\/li>\r\n\t
- Select as test “Test #2”<\/li>\r\n\t
- Below this selection: check the field names – same as in step 4 above – of the fields you have changed.<\/li>\r\n\t
- Press “Test the Photo Metadata of the Local Image” – the test is executed and a few moments later the test result will be shown.<\/li>\r\n\t
- View the test result – we recommend to record it by e.g. printing it out or creating a PDF file with the browser.
\r\nThe details of what is shown there is explained on the Test 2 – RESULT page.<\/li>\r\n\t - Interpret the test result – see below What IPTC expects as test result<\/em><\/li>\r\n\t
- You can do the same test with different sets of changed fields. Copy the downloaded IPTC reference image file again and rename it to e.g. “softwareA-test2-2<\/span><\/strong>.jpg” and “softwareA-test2-3<\/span><\/strong>.jpg” etc.
\r\nThen start the next test with step 2.<\/li>\r\n<\/ol>\r\n<\/div>\r\n\r\n\r\nWhat IPTC expects as test result<\/h3>\r\n\r\n\r\n
Test #2 on this site compares the values of the IPTC reference image with the values in the uploaded test image file which is initially a copy of the IPTC reference image.
\r\nIPTC expects only the values of the intentionally changed fields in the test image file are different from the IPTC reference image file.<\/strong><\/p>\r\n\r\n\r\nIf:
\r\n– only a field or some fields listed in step 4 above have been changed and
\r\n– if these field(s) have been checked on the page for uploading the local image
\r\nthis field is\/these fields should be highlighted in green in the test result showing “… value CHANGED”. This is telling “the change of this value is ok, it was done intentionally”. This is an expected change of values.
\r\nCheck if all fields with values changed by you are shown with “… value CHANGED” in green. <\/span>
\r\nBad result:<\/strong> if such fields do not show “… value CHANGED”, the software did not save the changed value(s) correctly<\/strong>.
\r\nIf “… value CHANGED – but NOT the … value!” is shown:<\/span> for this IPTC field the use of the XMP and the IIM format is specified; if the the value of this field is changed then both the XMP value and the IIM value must be changed. This “- but NOT the … (XMP\/IIM)” tells the value was changed only in one format but not in the other one – field values are partially not saved correctly and the values are inconsistent now!<\/strong><\/p>\r\n\r\n\r\nWithout changing a metadata field value in the test image the value must stay as the one in the IPTC reference image.
\r\nTherefore the Test #2-Result should not <\/em>show “… value CHANGED” or “… is MISSING” <\/span>for fields you have not changed! If this is the case the tested software modified values on its own or even removed some metadata fields. This is a serious violation of metadata interoperability.<\/strong><\/p>\r\n\r\n\r\nIf “… value is MISSING – NOT the … value!” is shown<\/span>: this indicates that for this IPTC field the XMP and the IIM format is specified, but only the value of one format is missing, the correct value in the other format still exists – field value(s) of one format have been stripped.<\/strong><\/p>\r\n\r\n\r\nTest #3: Which IPTC fields are supported by the software – and which not?<\/h2>\r\n\r\n\r\n
The IPTC Photo Metadata Standard defines a set of about 57 metadata fields, some of them have a structured value with a set of sub-fields. Unfortunately not all the software claiming to support IPTC fields supports all of them. For metadata interoperability it is quite essential that a specific IPTC field edited with software A can also be shown and edited with software B.
\r\nThis test investigates and lists which of the IPTC defined fields are supported, and which not.<\/strong><\/p>\r\n\r\n\r\nTest outline<\/h3>\r\n\r\n\r\n
IPTC provides an image file without<\/em> any embedded metadata – IPTC, Exif or any other. You should load this file in the to-be-tested software and fill in values for all fields available on the metadata panel(s).
\r\nFinally all the filled in values should be saved to this image file.\u00a0
\r\nNext this file should be uploaded to the IPTC Interoperability Test site and \u201cTest #3\u201d should be executed there. The generated test result shows all fields and sub-fields defined by the IPTC Photo Metadata Standard and for each one if a value in the XMP format was found and – if specified by the standard – also a value in the IIM format was found. If the values of a field in XMP and IIM were found the result also shows if the values are the same, if they are in sync.<\/p>\r\n\r\n\r\nTest procedure, step by step show\/hide this section<\/a><\/small><\/h3>\r\n\r\n\r\n\r\n\r\n\t- Download the IPTC NOmetadata image file<\/a> (from the IPTC web site). Create a copy of the file and rename it to something like \u201csoftwareA-test3-1.jpg\u201d.<\/li>\r\n\t
- Load, import, ingest this file into the to-be-tested software.<\/li>\r\n\t
- Activate the photo metadata panel(s) of the to-be-tested software. Select, if required, the IPTC fields.<\/li>\r\n\t
- Fill in a value for any shown field and – if available – any sub-fields. (E.g. the Image Creator field has the sub-fields Name and Identifier, both should be filled with a value.) If a field allows to fill in multiple values fill in at least two.<\/li>\r\n\t
- After all <\/strong>shown fields have been filled in save the metadata to this loaded image file. (May require an export action.)<\/li>\r\n\t
- Go to the IPTC Photo Metadata Interoperability Test site<\/a><\/li>\r\n\t
- Select as \u201clocal image file\u201d the file you have saved\/exported in step 5.<\/li>\r\n\t
- Select as test \u201cTest #3\u201d. (Ignore the checking of changed fields below, this is made for Test #2 only.)<\/li>\r\n\t
- Press \u201cTest the Photo Metadata of the Local Image\u201d \u2013 the test is executed and a few moments later the test result will be shown.<\/li>\r\n\t
- View the test result \u2013 we recommend to record it by e.g. printing it out or creating a PDF file with the browser.<\/li>\r\n\t
- Details of what is shown is explained on the Test 3 \u2013 RESULT page.<\/li>\r\n\t
- Interpret the test result \u2013 see below What IPTC expects as test result<\/em><\/li>\r\n\t
- You can do the same test with different values or a different count of multiple values. Copy the downloaded IPTC reference image file and rename it to e.g. \u201csoftwareA-test3-2<\/span><\/strong>.jpg\u201d and \u201csoftwareA-test3-3<\/span><\/strong>.jpg\u201d etc.<\/li>\r\n\t
- Then start the next test with step 2.<\/li>\r\n<\/ol>\r\n<\/div>\r\n\r\n\r\n
What IPTC expects as test result<\/h3>\r\n\r\n\r\n
Test #3 on this site checks for each IPTC field if a value in XMP format, and if the IIM format is also specified a value in IIM exists.
\r\nThe best test result <\/strong>shows in all rows of the IPTC-defined fields that XMP and IIM Values were found<\/span><\/strong> – not a single MISSING<\/span> result is shown, ignore the “not spec” in the IIM Value column. The only exception is the Image Region\/Other Metadata Property row, having a metadata field in this structure is not required by the IPTC Standard.
\r\nIf all results in the XMP Value column are shown as MISSING<\/span> the software apparently does not support the XMP format.
\r\nIf results in the IIM Value column show only MISSING<\/span> or “not spec” the software apparently does not support the IIM format.
\r\n
\r\nA bad result is this mix<\/strong>: the XMP Value cell of a metadata field row shows found<\/span> and the IIM Value cell in this row shows MISSING<\/span> – and IIM Value cells in other rows show found<\/span>. Apparently for this field only the XMP format is supported but not the IIM format.
\r\nThe same applies vice versa: the IIM Value cell shows found<\/span> and the XMP Value cell shows MISSING<\/span>.
\r\nIn these cases the Sync Values cell of this row shows NOT in sync<\/span>: one value exists, the other one should exist too but does not.
\r\n
\r\nIf both the XMP Value and the IIM Value cells of a row show found<\/span> a value in both formats exists. In this case the Sync Values column should show “in sync”, telling the values are the same, they are in sync<\/em>. If NOT in sync<\/span> is shown XMP and IIM values exist but they are different – a very bad case as nobody knows which value is the correct one<\/strong>.<\/p>\r\n\r\n\r\nIt is not bad if these fields are shown as MISSING<\/span>:<\/strong>
\r\n– Embedded Encoded Metadata Rights Expression: IPTC recommends to set the values of this structure by software and not by hand.
\r\n– Digital Image GUID: IPTC recommends to set the value of this field by software, not by hand.
\r\n– Image Region: should be used by a user interface feature integrated into imaging software, if the feature is not available setting the Image Region data by hand would be very hard.<\/p>\r\n\r\n\r\nAfter the tests …<\/h3>\r\n\r\n\r\n
… you may want to contact the maker of the tested software to discuss unexpected or bad results. We suggest to contact the support of the software maker.<\/p>\r\n\r\n\r\n
… you may want to discuss the results with other photo metadata people. IPTC runs a public email list at https:\/\/groups.io\/g\/iptc-photometadata\/<\/a>, join it and raise your questions or share your comments. You are highly welcome.<\/p>\r\n\r\n\r\nAll the best for running our interoperability tests,
\r\nDavid Riecks<\/span><\/em> and Michael Steidl<\/span><\/em>, Leads of the IPTC Photo Metadata Working Group<\/a><\/p>\r\n\r\n\r\n\r\n
- \r\n\t
- Test #1<\/a>: Do field labels align to the IPTC definition?<\/li>\r\n\t
- Test #2<\/a>: Does the software read and write embedded metadata correctly?<\/li>\r\n\t
- Test #3<\/a>: Which IPTC fields are supported by the software – and which are not?<\/li>\r\n<\/ul>\r\n<\/li>\r\n\t
- Compare your results of each test with the “what IPTC expects as test result” section of the test description, and draw your conclusions about the interoperability quality of the software.<\/li>\r\n\t
- You may contact the maker of the software and ask about differences between your test results and IPTC’s expectations.<\/li>\r\n\t
- You may also contact IPTC: Use the Contact Us page<\/a> on this site.<\/li>\r\n<\/ul>\r\n\r\n\r\n
Terminology used show\/hide more details of this section<\/a><\/small><\/h3>\r\n\r\n\r\n
\r\n- \r\n\t
- software<\/strong>: an application used for viewing and\/or editing IPTC photo metadata. This could be an application on a computer or software on a server and on a client computer to be considered as a single software system – typically Digital Asset Management (DAM) or Media Asset Management (MAM) systems. And it could be a web content management system rescaling image files which may have an impact on embedded photo metadata.<\/li>\r\n\t
- metadata user interface<\/strong> and\/or metadata panel<\/strong>: the full user interface or a part of the user interface of the software showing metadata fields (labels and their values) and supporting to edit the values.<\/li>\r\n<\/ul>\r\n<\/div>\r\n\r\n\r\n
Metadata field <\/strong>or metadata property<\/strong>: an element of metadata made for a specific purpose, e.g. to hold the date and time of creating the image, name of who created the image, describing what the image shows or who owns the copyright of the image. Field <\/em>is the term used primarily by users of the software, property <\/em>is the term primarily used by metadata standards and makers of the software, in fact they are synonyms.
\r\nFor the test guideline below we use the term field<\/em>.<\/p>\r\n\r\n\r\nTest #1: Do field labels align to the IPTC definition?<\/h2>\r\n\r\n\r\n
For filling in the value of a metadata field a user should know for what kind of information this field is made. For IPTC fields this is defined by the IPTC Photo Metadata Standard<\/a>. The first – and in many cases the only – helper on a metadata user interface is the field label. It is shown close to where you can see or fill in the value and tells with a single or a few words what should be filled into the field or what the field shows.
\r\nThis test checks if the label of a field in the tested software aligns with the IPTC definition.<\/strong><\/p>\r\n\r\n\r\nTest outline<\/h3>\r\n\r\n\r\n
The IPTC has created a reference image file with all metadata fields defined by the IPTC standard and almost each field has its IPTC name as value (only very short or numeric values are different). This name is also used in the IPTC standard document. You should load this file in the to-be-tested software and check with your eyes on the software’s metadata panel(s): does the shown field value – the IPTC field name – tell (almost) the same as the label of this field on the panel.<\/p>\r\n\r\n\r\n
Test procedure, step by step show\/hide this section<\/a><\/small><\/h3>\r\n\r\n\r\n
\r\n\r\n\r\n- \r\n\t
- Download the Standard 2021.1 Reference Image file <\/a> (see also the IPTC Photo Metadata Standard page<\/a>).<\/li>\r\n\t
- Load, import, ingest this file into the to-be-tested software.<\/li>\r\n\t
- Activate the photo metadata panel(s) of the to-be-tested software. Select, if required, the IPTC fields.<\/li>\r\n\t
- Compare for each field: does the field’s label tell the same, or at least something very similar, as the shown value of the field, this is the name of the field defined by IPTC.
\r\nThis may look like:<\/li>\r\n\t- Record if the field’s label and the IPTC name in the value do not <\/span>align:
\r\n– by writing down the field’s label and the IPTC name shown as the field’s value
\r\n– by taking a screenshot of the whole metadata panel or at least this region of the panel.<\/li>\r\n<\/ol>\r\n<\/div>\r\n\r\n\r\n<\/p>\r\n<\/div>\r\n<\/div>\r\n\r\n\r\n
What IPTC expects as test result<\/h3>\r\n\r\n\r\n
Each IPTC Photo Metadata field has a definition of its semantics and a corresponding recommended label in English. Therefore IPTC expects that any label of an IPTC property is either identical to the the field’s name or label in English as defined by IPTC or only a slight modification of it<\/strong>. For a label in a different language the translation should reflect what IPTC defined as kind of information of the field.<\/p>\r\n\r\n\r\n
Test #2: Does the software read and write embedded metadata correctly?<\/h2>\r\n\r\n\r\n
Each software supporting photo metadata implements a small metadata workflow: the embedded metadata is read from the image file, the read field values are assigned to corresponding fields on the metadata panel. If the field values can be edited each one has to be assigned to the corresponding IPTC field(s) and finally all fields should be embedded into the image file correctly.
\r\nThis test checks if software used for this metadata workflow is reading and writing values correctly.<\/strong>
\r\n(Note: some desktop software and most DAM\/MAM systems read the metadata into a local database and the metadata is embedded into in image file only by an export action. IPTC considers this as the internal metadata management of software which should align to this outlined metadata workflow: the metadata fields should be read and saved correctly.)<\/p>\r\n\r\n\r\nTest outline<\/h3>\r\n\r\n\r\n
IPTC has a reference image file with all metadata fields defined by the IPTC standard and each field has a specific value. You should load this file in the to-be-tested software, edit (= change) the values of some fields and save all metadata to the image file. This file should be uploaded to the IPTC Interoperability Test site and “Test #2” should be executed there. The generated test result shows:
\r\n1. If the intentionally edited IPTC files have a value different to the IPTC reference image file, as expected, or still the same.
\r\n2. If other IPTC fields than the ones edited by you have unexpectedly a value different to the IPTC reference image file. (Possible cases: changed value, no value.)<\/p>\r\n\r\n\r\nTest procedure, step by step show\/hide this section<\/a><\/small><\/h3>\r\n\r\n\r\n
\r\n- \r\n\t
- Download the Standard 2021.1 Reference Image file <\/a>\u00a0– Note as of 6 June 2022: if you have a previously downloaded Reference Image file download it again now<\/span>, a few details were improved and using the old version on the Interoperability Test site would show wrong results!
\r\n(See also the IPTC Photo Metadata Standard page<\/a>). Create a copy of the file and rename it to something like “softwareA-test2-1.jpg”.<\/li>\r\n\t- Load, import, ingest this file into the to-be-tested software.<\/li>\r\n\t
- Activate the photo metadata panel(s) of the to-be-tested software. Select, if required, the IPTC fields.<\/li>\r\n\t
- Change the values of some fields. The IPTC Interoperability Test site supports changed values of these fields in the test result:\r\n\r\n
- \r\n\t
- Description\/Caption (an IPTC Core field with a text value)<\/li>\r\n\t
- Keywords (an IPTC Core field with optionally multiple occurrences, each with a text value)<\/li>\r\n\t
- Rights Usage Terms (an IPTC Core field with a text value)<\/li>\r\n\t
- Image Creator (an IPTC Extension field with sub-fields, not the same as the Creator field)<\/li>\r\n\t
- Location Created (an IPTC Extension field with sub-fields)<\/li>\r\n\t
- Copyright URL\/Web Statement of Rights (an IPTC Extension field with a text value)<\/li>\r\n<\/ol>\r\n<\/li>\r\n\t
- Save the metadata to this loaded image file. (May require an export action.)<\/li>\r\n\t
- Go to the IPTC Photo Metadata Interoperability Test site<\/a><\/li>\r\n\t
- Select as “local image file” the file you have saved\/exported in step 5.<\/li>\r\n\t
- Select as test “Test #2”<\/li>\r\n\t
- Below this selection: check the field names – same as in step 4 above – of the fields you have changed.<\/li>\r\n\t
- Press “Test the Photo Metadata of the Local Image” – the test is executed and a few moments later the test result will be shown.<\/li>\r\n\t
- View the test result – we recommend to record it by e.g. printing it out or creating a PDF file with the browser.
\r\nThe details of what is shown there is explained on the Test 2 – RESULT page.<\/li>\r\n\t- Interpret the test result – see below What IPTC expects as test result<\/em><\/li>\r\n\t
- You can do the same test with different sets of changed fields. Copy the downloaded IPTC reference image file again and rename it to e.g. “softwareA-test2-2<\/span><\/strong>.jpg” and “softwareA-test2-3<\/span><\/strong>.jpg” etc.
\r\nThen start the next test with step 2.<\/li>\r\n<\/ol>\r\n<\/div>\r\n\r\n\r\nWhat IPTC expects as test result<\/h3>\r\n\r\n\r\n
Test #2 on this site compares the values of the IPTC reference image with the values in the uploaded test image file which is initially a copy of the IPTC reference image.
\r\nIPTC expects only the values of the intentionally changed fields in the test image file are different from the IPTC reference image file.<\/strong><\/p>\r\n\r\n\r\nIf:
\r\n– only a field or some fields listed in step 4 above have been changed and
\r\n– if these field(s) have been checked on the page for uploading the local image
\r\nthis field is\/these fields should be highlighted in green in the test result showing “… value CHANGED”. This is telling “the change of this value is ok, it was done intentionally”. This is an expected change of values.
\r\nCheck if all fields with values changed by you are shown with “… value CHANGED” in green. <\/span>
\r\nBad result:<\/strong> if such fields do not show “… value CHANGED”, the software did not save the changed value(s) correctly<\/strong>.
\r\nIf “… value CHANGED – but NOT the … value!” is shown:<\/span> for this IPTC field the use of the XMP and the IIM format is specified; if the the value of this field is changed then both the XMP value and the IIM value must be changed. This “- but NOT the … (XMP\/IIM)” tells the value was changed only in one format but not in the other one – field values are partially not saved correctly and the values are inconsistent now!<\/strong><\/p>\r\n\r\n\r\nWithout changing a metadata field value in the test image the value must stay as the one in the IPTC reference image.
\r\nTherefore the Test #2-Result should not <\/em>show “… value CHANGED” or “… is MISSING” <\/span>for fields you have not changed! If this is the case the tested software modified values on its own or even removed some metadata fields. This is a serious violation of metadata interoperability.<\/strong><\/p>\r\n\r\n\r\nIf “… value is MISSING – NOT the … value!” is shown<\/span>: this indicates that for this IPTC field the XMP and the IIM format is specified, but only the value of one format is missing, the correct value in the other format still exists – field value(s) of one format have been stripped.<\/strong><\/p>\r\n\r\n\r\n
Test #3: Which IPTC fields are supported by the software – and which not?<\/h2>\r\n\r\n\r\n
The IPTC Photo Metadata Standard defines a set of about 57 metadata fields, some of them have a structured value with a set of sub-fields. Unfortunately not all the software claiming to support IPTC fields supports all of them. For metadata interoperability it is quite essential that a specific IPTC field edited with software A can also be shown and edited with software B.
\r\nThis test investigates and lists which of the IPTC defined fields are supported, and which not.<\/strong><\/p>\r\n\r\n\r\nTest outline<\/h3>\r\n\r\n\r\n
IPTC provides an image file without<\/em> any embedded metadata – IPTC, Exif or any other. You should load this file in the to-be-tested software and fill in values for all fields available on the metadata panel(s).
\r\nFinally all the filled in values should be saved to this image file.\u00a0
\r\nNext this file should be uploaded to the IPTC Interoperability Test site and \u201cTest #3\u201d should be executed there. The generated test result shows all fields and sub-fields defined by the IPTC Photo Metadata Standard and for each one if a value in the XMP format was found and – if specified by the standard – also a value in the IIM format was found. If the values of a field in XMP and IIM were found the result also shows if the values are the same, if they are in sync.<\/p>\r\n\r\n\r\nTest procedure, step by step show\/hide this section<\/a><\/small><\/h3>\r\n\r\n\r\n
\r\n- \r\n\t
- Download the IPTC NOmetadata image file<\/a> (from the IPTC web site). Create a copy of the file and rename it to something like \u201csoftwareA-test3-1.jpg\u201d.<\/li>\r\n\t
- Load, import, ingest this file into the to-be-tested software.<\/li>\r\n\t
- Activate the photo metadata panel(s) of the to-be-tested software. Select, if required, the IPTC fields.<\/li>\r\n\t
- Fill in a value for any shown field and – if available – any sub-fields. (E.g. the Image Creator field has the sub-fields Name and Identifier, both should be filled with a value.) If a field allows to fill in multiple values fill in at least two.<\/li>\r\n\t
- After all <\/strong>shown fields have been filled in save the metadata to this loaded image file. (May require an export action.)<\/li>\r\n\t
- Go to the IPTC Photo Metadata Interoperability Test site<\/a><\/li>\r\n\t
- Select as \u201clocal image file\u201d the file you have saved\/exported in step 5.<\/li>\r\n\t
- Select as test \u201cTest #3\u201d. (Ignore the checking of changed fields below, this is made for Test #2 only.)<\/li>\r\n\t
- Press \u201cTest the Photo Metadata of the Local Image\u201d \u2013 the test is executed and a few moments later the test result will be shown.<\/li>\r\n\t
- View the test result \u2013 we recommend to record it by e.g. printing it out or creating a PDF file with the browser.<\/li>\r\n\t
- Details of what is shown is explained on the Test 3 \u2013 RESULT page.<\/li>\r\n\t
- Interpret the test result \u2013 see below What IPTC expects as test result<\/em><\/li>\r\n\t
- You can do the same test with different values or a different count of multiple values. Copy the downloaded IPTC reference image file and rename it to e.g. \u201csoftwareA-test3-2<\/span><\/strong>.jpg\u201d and \u201csoftwareA-test3-3<\/span><\/strong>.jpg\u201d etc.<\/li>\r\n\t
- Then start the next test with step 2.<\/li>\r\n<\/ol>\r\n<\/div>\r\n\r\n\r\n
What IPTC expects as test result<\/h3>\r\n\r\n\r\n
Test #3 on this site checks for each IPTC field if a value in XMP format, and if the IIM format is also specified a value in IIM exists.
\r\nThe best test result <\/strong>shows in all rows of the IPTC-defined fields that XMP and IIM Values were found<\/span><\/strong> – not a single MISSING<\/span> result is shown, ignore the “not spec” in the IIM Value column. The only exception is the Image Region\/Other Metadata Property row, having a metadata field in this structure is not required by the IPTC Standard.
\r\nIf all results in the XMP Value column are shown as MISSING<\/span> the software apparently does not support the XMP format.
\r\nIf results in the IIM Value column show only MISSING<\/span> or “not spec” the software apparently does not support the IIM format.
\r\n
\r\nA bad result is this mix<\/strong>: the XMP Value cell of a metadata field row shows found<\/span> and the IIM Value cell in this row shows MISSING<\/span> – and IIM Value cells in other rows show found<\/span>. Apparently for this field only the XMP format is supported but not the IIM format.
\r\nThe same applies vice versa: the IIM Value cell shows found<\/span> and the XMP Value cell shows MISSING<\/span>.
\r\nIn these cases the Sync Values cell of this row shows NOT in sync<\/span>: one value exists, the other one should exist too but does not.
\r\n
\r\nIf both the XMP Value and the IIM Value cells of a row show found<\/span> a value in both formats exists. In this case the Sync Values column should show “in sync”, telling the values are the same, they are in sync<\/em>. If NOT in sync<\/span> is shown XMP and IIM values exist but they are different – a very bad case as nobody knows which value is the correct one<\/strong>.<\/p>\r\n\r\n\r\nIt is not bad if these fields are shown as MISSING<\/span>:<\/strong>
\r\n– Embedded Encoded Metadata Rights Expression: IPTC recommends to set the values of this structure by software and not by hand.
\r\n– Digital Image GUID: IPTC recommends to set the value of this field by software, not by hand.
\r\n– Image Region: should be used by a user interface feature integrated into imaging software, if the feature is not available setting the Image Region data by hand would be very hard.<\/p>\r\n\r\n\r\nAfter the tests …<\/h3>\r\n\r\n\r\n
… you may want to contact the maker of the tested software to discuss unexpected or bad results. We suggest to contact the support of the software maker.<\/p>\r\n\r\n\r\n
… you may want to discuss the results with other photo metadata people. IPTC runs a public email list at https:\/\/groups.io\/g\/iptc-photometadata\/<\/a>, join it and raise your questions or share your comments. You are highly welcome.<\/p>\r\n\r\n\r\n
All the best for running our interoperability tests,
\r\nDavid Riecks<\/span><\/em> and Michael Steidl<\/span><\/em>, Leads of the IPTC Photo Metadata Working Group<\/a><\/p>\r\n\r\n\r\n\r\n
- metadata user interface<\/strong> and\/or metadata panel<\/strong>: the full user interface or a part of the user interface of the software showing metadata fields (labels and their values) and supporting to edit the values.<\/li>\r\n<\/ul>\r\n<\/div>\r\n\r\n\r\n
- Test #2<\/a>: Does the software read and write embedded metadata correctly?<\/li>\r\n\t
![Standard 2021.1 Reference Image file <\/a> (see also the](\"https:\/\/iptc.org\/std\/photometadata\/examples\/IPTC-PhotometadataRef-Std2021.1.jpg\"){kind=link}