What a delivery includes exactly

Per article (or per batch, depending on the contract) the standard delivery includes:

• JATS XML in the agreed Tag Set and version (e.g. Journal Publishing + SciELO SPS rules, or a PMC profile)
• Normalized metadata in the XML (authors, affiliations, DOI, ORCID when available)
• Associated assets: figures, exported tables when applicable, and other files linked from the XML
• Validation report(s) for the contracted profile
• Brief handoff note (what to check on receipt / how to resubmit to the platform)

We organize the handoff so an editorial team can archive and resubmit without blind renaming. Typical issue layout:

issue-2026-01/
  00-manifest.txt
  articles/
    e012345/
      e012345.xml
      figures/
        e012345-f01.tif
        e012345-f02.tif
      tables/          (when applicable)
      reports/
        validation.txt
  html/                (only if in the contract)
    e012345.es.html
    e012345.en.html

• Stable article identifier (DOI suffix, elocation-id, or journal internal ID — agreed at kickoff)
• XML: `{id}.xml` (or the pattern SciELO/PMC / the journal’s OJS requires)
• Figures: `{id}-f{nn}.{ext}` matching the ids in the XML
• Reports: `validation.txt` or `validation-{profile}.txt` beside the article
• If the platform imposes another scheme, we document it in the proposal and apply it consistently

We deliver quality-control evidence aligned to the destination, not only generic “valid XML”:

• Schema validation for the contracted JATS Tag Set
• When SciELO is the destination: SPS-oriented checks in addition to Publishing
• When PMC is the destination: the profile agreed with the publisher
• Residual findings (if any) prioritized with recommended action

Per-article or per-language HTML is not in the baseline unless stated in the proposal. When contracted:

• HTML derived from the agreed XML (not a redesign of the journal site)
• One file per language when the bilingual policy requires it
• Asset paths consistent with the delivered XML

• Baseline: one correction round on findings attributable to our production (markup errors, broken links to assets we delivered, inconsistencies vs the approved source)
• Author content changes or a new PDF after source freeze are usually quoted separately
• Batch timelines are set in the proposal (articles/week or issue date); partial handoff is possible on large projects

You can request your SciELO/OJS naming, a CSV manifest, or a different ZIP layout. We write it into the proposal so the RFP and the delivery match.

For confidentiality, retention, and submission channels, see Security and confidentiality.