EditorialXML

Services

Existing XML correction and rescue

You already have XML — yours or a third party’s — but SciELO, PMC, or your validator returns errors. We diagnose, correct, and remediate markup for the destination, with re-validation and a change note.

Request a diagnosis

The problem

“Almost ready” XML can block an entire issue: broken affiliations, inconsistent refs, incomplete SPS, wrong sub-article models, or misaligned assets. Rebuilding from PDF is often more expensive than rescuing what you have.

Our solution

We start from the current XML and the rejection report (or a pass through the free validator). We deliver corrected XML, validated against the agreed profile, plus a summary of what changed — not an audit that only lists findings.

Rescue process

  1. 01

    Sample and diagnosis

    We review 1–3 articles (or the rejected package) and classify technical vs editorial vs destination errors.

  2. 02

    Scope and quote

    We define whether you need a focused fix, SPS/PMC remediation, or a batch with stable criteria.

  3. 03

    Correction and remediation

    We edit structure, metadata, refs, and asset links; we align the model to the destination (including bilingual cases when needed).

  4. 04

    Re-validation and delivery

    We validate again, deliver XML + change note, and when useful a checklist for platform resubmission.

Deliverables

  • Corrected XML per article
  • Change note (what was fixed and why)
  • Re-validation report for the contracted profile
  • Recommendations to prevent repeat issues in the workflow

How it fits with the rest

FAQ

How is this different from editorial validation?

Editorial validation focuses on a human report and correction list. Rescue delivers corrected XML ready for resubmission. They can combine: audit first, correction second.

Is this the same as the validator professional report?

No. The professional report automates technical findings. Rescue is human editorial work on your XML (with optional adjustment rounds).

Do you have a fixed per-article price?

Rarely without a sample: effort depends on XML origin, error volume, and destination. We start with a sample diagnosis.

What if the XML came from a previous vendor?

We work with third-party XML. We do not need their tools — just the file, the destination, and the rejection message if you have one.

Send a rejected sample

Attach the XML (or package) and, if you can, the SciELO/PMC or validator report. We will return scope, timeline, and a quote.

Request a diagnosis