A journal article is more than a sequence of paragraphs. It has authors, affiliations, sections, references, figures, and relationships between them. Preparing JATS XML is about making those relationships explicit enough for a publishing system to use.
What JATS adds to the handoff
The Journal Article Tag Suite defines XML elements and attributes for journal articles. Instead of relying only on visual cues, the file identifies parts of the article by their role.
That distinction matters. A superscript number beside an author’s name could refer to an affiliation or a note. A parenthesized number in body text might point to a reference, an equation, or neither. A conversion needs review wherever a visual clue could have more than one meaning.
JATS also has different tag sets. The receiving platform may require a particular version or impose its own rules. Ask for those requirements before preparing a large batch.
Prepare the Word source with consistency
- Make the article hierarchy clear. Use consistent heading styles and verify that the levels reflect the argument. Do not rely only on font size and bold text.
- Separate metadata from the body. Check the title, author names, affiliations, identifiers, abstract, and keywords against the final editorial record.
- Use real tables. A grid simulated with spaces or tabs is difficult to interpret reliably. Check table headings and notes.
- Keep assets identifiable. Match figure labels, captions, and source files. Keep a record of which asset belongs to which figure.
- Review references. Confirm that reference labels and in-text citations are consistent. Resolve incomplete or ambiguous entries before conversion where possible.
- Resolve editorial leftovers. Review tracked changes, comments, duplicated headings, and obsolete captions before producing the final source.
These steps reduce ambiguity; they do not guarantee a perfect conversion. Save a versioned copy so the XML can be traced back to the exact manuscript used.
Review relationships, not just the text
After conversion, compare the visible article with the structured result. Check the section order, author-to-affiliation links, figure and table references, notes, and bibliography. Follow a selection of cross-references and inspect the difficult cases rather than checking only the first item.
Look for missing content as well as incorrect structure. Confirm that abstracts, acknowledgments, supplementary-material references, and back matter are present when required. For mathematics, verify the meaning of expressions and the representation expected by the destination.
Do not infer that an identifier is correct simply because it has the right shape. Check the editorial source. In a multi-author article, a mistaken relationship can be more consequential than an obvious typographical error.
Validate for the system that will receive it
Run the relevant XML validation and inspect the report. Then check the receiving system’s packaging rules: metadata requirements, file names, asset formats, schema version, and any additional profile constraints. A structurally valid document is not a guarantee of platform acceptance.
Trial a representative article through the actual handoff process before scaling. Keep the source version, XML, assets, report, and issue notes together.
DocSpry supports PDF and Word input for journal XML. Word input does not produce EPUB or accessible PDF in this workflow. If those are your required outputs, begin with a supported born-digital PDF instead.
Sources & further reading
General workflow guidance. Product suitability depends on the source document and the receiving system’s requirements.