Typical <author-notes> include correspondence notes and other notes regarding authors (and potentially about other contributors). Such notes may name one of the authors a corresponding author, provide the author affiliation or current contact information, explain that the person has changed organizations, or provide other contributor-related material. (Source: https://jats.nlm.nih.gov/archiving/tag-library/1.2d1/element/author-notes.html)
<author-notes> must be contained in the <article-meta> element.
<author-notes> is optional.
Any <author-notes> element should have an @id attribute. Every <author-notes> element needs a matching <xref> element in a <contrib> section, with a @ref-type of author-notes and a @rid that matches the appropriate author-notes/@id.
Any non-<corresp> data in <author-notes> must be contained within a <fn> element.
–
<ack> contains acknowledgements: textual material that names the parties who the author wishes to thank or recognize for their assistance in, for example, producing the work, funding the work, inspiring the work, or assisting in the research on which the work is based. (Source: https://jats.nlm.nih.gov/archiving/tag-library/1.2d1/element/ack.html)
<ack> must be contained in the <back> element.
<ack> is optional.
–
See Biography for more information about tagging for biographies.
Provide examples of XML tagging, along with a short description for each example. Examples should be based on live content if possible. Use the “Code Inline” Word style, or include XML files and reference the file name and XPath to the relevant part of the file. It is helpful to include both correct examples and examples of incorrect tagging that should fail validation. Where it may be helpful, examples can include screenshots of renderings and PDFs along with the corresponding XML tagging.
Author Notes
Valid Tagging:
<author-notes>
<corresp id="AN0001">CONTACT John Q Author <email xlink:href="[email protected]">[email protected]</email></corresp>
<fn>
<p>Present affiliation for John Q Author is UNESCO Regional Office for Southern Africa (ROSA), Harare, Zimbabwe.</p>
</fn>
</author-notes>
The above consists of fairly typical author-notes, comprising correspondence details for a corresponding author and a footnote to display. This is valid and correct – the data contained is suitable for an author note – but the data in the <fn> element will not be displayed anywhere online.
Ideal Tagging:
<author-notes>
<corresp id="AN0001">CONTACT John Q Author <email xlink:href="[email protected]">[email protected]</email></corresp>
<fn fn-type="current-aff">
<p>Present affiliation for John Q Author is UNESCO Regional Office for Southern Africa (ROSA), Harare, Zimbabwe.</p>
</fn>
</author-notes>
In an ideal world every
Incorrect Tagging:
<author-notes>
Present affiliation for John Q Author is UNESCO Regional Office for Southern Africa (ROSA), Harare, Zimbabwe.
</author-notes>
Above we have ‘raw’ character data present in the <author-notes> element. This will fail validation because all character data should be contained within either a <corresp>, <fn>, or <p> element.
Ack
Valid Tagging:
<ack>
<title>Acknowledgements</title>
<p>The authors wish to thank Amelia Author for her assistance with the literature search, and John Q Author and Laszlo Cook for giving the researchers access to their personal archives with evaluations, articles, books, reports and correspondence on many of the disasters and crises analysed in this study.</p>
</ack>
All <ack> sections should have a title, containing the text ‘Acknowledgements’ if nothing else is specified. Then text in <p> tags.
Incorrect Tagging:
<ack>
<title>Acknowledgements</title>
<abstract>…</abstract>
<kwd-group>…</kwd-group>
<p>text text text</p>
<sec>…</sec>
<ref-list>…</ref-list>
</ack>
Although <abstract>, <kwd-group>, <sec> and <ref-list> are all valid elements within <ack> under JATS 1.2, from a practical point of view they should be ruled out. Acknowledgements shouldn’t be complex documents in their own right.