DOAJ Native XML schema

DOAJ maintains its own XML schema — commonly called DOAJ Native XML, and originally issued as a DTD — as one of the ways publishers get article-level metadata into DOAJ’s index. Publishers convert their article records to a file that validates against DOAJ’s published schema (an XSD, referenced from DOAJ’s own XML documentation) and upload it through their DOAJ publisher account; a single file can carry multiple articles, subject to a size limit DOAJ documents alongside the upload form.

Why a DOAJ-specific schema exists. DOAJ does not crawl or scrape journal websites for full bibliographic detail, and it does not require a specific journal platform. A schema DOAJ controls and validates against lets a publisher decide exactly which fields reach the index, in DOAJ’s own field structure, rather than DOAJ inferring article metadata from a format designed for a different purpose. That said, DOAJ’s own editorial history is candid that the original DTD-based approach created real friction for publishers — conversion cost against existing content archives, unfamiliarity with XML tooling among smaller journal teams, and reluctance from larger publishers to support yet another proprietary format. DOAJ’s response was not to abandon its own schema but to add alternatives alongside it: Crossref XML compatibility (Crossref 4.4.2, later Crossref 5.3.1) for publishers who already generate Crossref deposit XML for DOI registration, and an OJS plugin that produces DOAJ-conformant XML automatically for journals on that platform. A publisher today effectively chooses between DOAJ’s own schema, Crossref’s schema, or letting OJS generate the file — DOAJ Native XML is the option that gives a publisher direct control over the submitted record without depending on what a DOI-registration schema happens to carry.

Not to be confused with DOAJ’s OAI-PMH interface. DOAJ also exposes an OAI-PMH provider endpoint, but that runs in the opposite direction from the XML upload methods above: it lets libraries, discovery services, and aggregators harvest DOAJ’s already-indexed metadata back out, on a per-article basis if needed. It is not a channel publishers use to submit records — the only inbound methods DOAJ documents are XML upload (DOAJ Native or Crossref), DOAJ’s API, and the OJS plugin.

Not to be confused with the DOAJ Seal. The DOAJ Seal was a badge applied to a journal’s existing DOAJ record to flag adherence to a further set of best-practice criteria beyond basic inclusion. DOAJ retired the Seal at the end of March 2025 (changes went live 8 April 2025) following a 2024 community consultation that found the Seal was widely misunderstood and no longer serving its original purpose. DOAJ has since begun rolling out individual journal labels in its place — the Subscribe to Open (S2O) label launched in March 2025 was the first — rather than a single blanket quality mark. None of this affects the XML schema: labels and the Seal describe editorial/business-model attributes of a journal’s listing, not the metadata-submission format used to populate article records in the first place.