Article Corrections

If an article is published with errors, then a corrected version of the article will need to be published. Broadly speaking, errors are classed as ”major” or ”minor”.

If a major error has occurred, then a corrected version of the article is published and is linked to a separate correction notice article (see Related Articles for more information). A footnote is added to the first page of the article PDF containing the following text that should include a DOI link to the correction notice:

This article was originally published with errors, which have now been corrected in the online version. Please see Correction https://doi.org/[insert DOI]

If a minor error has occurred, then a separate correction notice article is not required. Instead, the article is corrected, and a footnote is added to the first page of the article PDF containing the following text:

This article has been corrected with minor changes. These changes do not impact the academic content of the article.

The correction statement should be tagged in a backmatter notes section using a <sec> element within a <notes> element within the <back> element of the article. The section should be assigned an attribute sec-type="correction-notice-major" for a major correction or sec-type="correction-notice-minor" for a minor correction. This special section should be given the <title> “Correction Statement”.

In some cases the correction statement may be tagged as a footnote instead of as a section (although tagging as a backmatter notes section is preferred). In such cases, the footnote should be assigned an attribute fn-type="correction-notice-major" for major corrections or fn-type="correction-notice-minor" for minor corrections.

Note 1: The attribute value correction-notice may be used for correction notices that are not classed as major or minor.

Note 2: Previously, the attribute value correction-statement was used for both minor and major corrections.

Major Correction

A correction statement for a major correction should be tagged as a backmatter notes section using the DOI of the correction notice.

<notes> 
    <sec sec-type="correction-notice-major"> 
        <title>Correction Statement</title> 
        <p>This article was originally published with errors, which have now been corrected in the online version. Please see Correction <ext-link ext-link-type="doi" xlink:href="https://doi.org/[insert DOI]">https://doi.org/[insert DOI]</ext-link>.</p>
    </sec> 
</notes> 

A correction statement for a major correction may be tagged as a footnote using the DOI of the correction notice.

<fn id="an0001" fn-type="correction-notice-major">
    <p>This article was originally published with errors, which have now been corrected in the online version. Please see Correction <ext-link ext-link-type="doi" xlink:href="https://doi.org/[insert DOI]">https://doi.org/[insert DOI]</ext-link>.</p> 
</fn>

The separate correction notice article should be to the corrected article using a related-article link. See Related Articles for more information.

Minor Correction

A correction statement for a minor correction should be tagged as a backmatter notes section.

<notes> 
    <sec sec-type="correction-notice-minor"> 
        <title>Correction Statement</title> 
        <p>This article has been corrected with minor changes. These changes do not impact the academic content of the article.</p>
    </sec> 
</notes> 

A correction statement for a minor correction may be tagged as a footnote.

<fn id="an0001" fn-type="correction-notice-minor">
    <p>This article has been corrected with minor changes. These changes do not impact the academic content of the article.</p>
</fn>

Incorrect examples

The examples in this section show common tagging errors. Schematron validation errors may be reported for some of these tagging errors.

In this incorrect example:

<sec> 
    <title>Correction Statement</title> 
    <p>This article has been corrected with minor changes. These changes do not impact the academic content of the article.</p>
</sec> 
  1. The sec-type attribute is missing.
  2. The <notes> element is missing.

In this incorrect example:

<fn id="an0002">
    <p>This article was originally published with errors, which have now been corrected in the online version. Please see Correction http://dx.doi.org/10.1080/00103624.2022.2047516.</p>
</fn>
  1. The fn-type attribute is missing.
  2. The DOI URL should be tagged as using <ext-link ext-link-type="doi">.
  3. The DOI link should begin with “https://doi.org/" instead of the old URL prefix “http://dx.doi.org/" which should not be used in new content.

In this incorrect example:

<fn id="an0002">
    <p>Color versions of one or more of the figures in the article can be found online at <ext-link ext-link-type="uri" xlink:href="http://www.tandfonline.com/UESO">www.tandfonline.com/ueso</ext-link>.This article was originally published with errors, which have now been corrected in the online version. Please see Correction <ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.1080/15567036.2019.1688016">http://dx.doi.org/10.1080/15567036.2019.1688016</ext-link>.</p>
</fn>
  1. This correction statement should not be combined with another footnote.
  2. The fn-type attribute is missing.
  3. The DOI link should be tagged using ext-link-type “doi” instead of “uri”.
  4. The DOI link should begin with “https://doi.org/" instead of the old URL prefix “http://dx.doi.org/" which should not be used in new content.

Additional information