SciELO XML Markup

What is SciELO XML Markup?

SciELO XML markup is the process of converting scientific articles to JATS XML (Journal Article Tag Suite) format, the standard required by the SciELO library and other international indexing databases such as PMC/PubMed and Redalyc.

This structured format allows article metadata — such as title, authors, abstract, references and body text — to be correctly read and indexed by search systems and scientific databases, increasing the visibility and reach of your publication.

How the SciELO XML conversion workflow works

Our production workflow is designed to reduce rework and speed up approval. We start with a technical diagnosis of source files (Word, PDF, images, metadata and references) to identify gaps, citation patterns and journal-specific requirements. This avoids frequent issues such as incomplete affiliations, inconsistent metadata fields and missing mandatory tags.

Next, we perform JATS XML markup with semantic consistency across front matter, body, references, tables, figures and supplementary materials. After markup, we run automated validation and a manual technical review to catch issues that rule-based checks may miss.

The final stage is approval support. We deliver a validated package and remain available for correction cycles during submission. This is especially useful for journals moving into new indexing databases or consolidating internal editorial workflows.

We also coordinate with editorial teams on communication routines, version control and delivery checkpoints. This operational layer is essential when multiple stakeholders are involved, because small metadata changes after validation can break consistency and require a full recheck. A controlled workflow preserves quality across issues.

Quality checklist to reduce validation rejections

In SciELO XML projects, approval speed depends heavily on pre-submission quality control. We run a checklist per article and per issue covering mandatory metadata, language consistency, reference normalization and coherence between source files and final XML output.

We also review editorial context, not only XML structure. Common issues include inconsistent institutional naming, metadata that does not match the PDF, and keyword sets that diverge from abstract content. These gaps often survive basic reviews and surface only during indexing.

For journals with continuous production, we recommend lightweight governance: standardized file naming, centralized metadata sheet, clear issue-closing criteria and technical validation before final handoff. This approach reduces recurring errors and improves publication predictability.

Another best practice is to define acceptance criteria before production starts: mandatory metadata fields, reference style rules, multilingual policy, and procedures for supplementary files. When this is documented, teams make faster decisions, approvals are smoother and turnaround remains stable even under peak publication cycles.

Expected outcomes for editorial teams

With a stable XML workflow, journals gain predictable production cycles, faster communication with indexers and fewer last-minute technical revisions. This allows editors to focus on scientific quality and issue planning.

Consistent metadata also improves discoverability. Articles become easier to retrieve in search engines, directories and academic platforms, which supports broader dissemination and citation tracking.

In the medium term, the impact is both operational and strategic: less rework, stronger deadline control and a technical foundation ready for expansion into additional indexing databases.

Teams also benefit from clearer accountability across editorial, production and validation steps, which improves handoff quality and reduces hidden bottlenecks in high-volume publication cycles.

This consistency supports better planning for future issues and strengthens long-term indexing performance.