Editorial Technology Workflow
JournalsHQ works with academic journals through a structured technical workflow: from initial review and metadata checks to OJS support, XML/JATS preparation, academic HTML, EPUB, QA diagnostics and final delivery packages.
The goal is simple: reduce improvisation, make technical work reviewable, and give journal teams clear outputs they can inspect before publication or platform changes.
1. Submit journal, DOI, ISSN or article files
The process begins with the journal's current materials: ISSN, DOI records, OJS information, published articles, final PDFs, metadata exports or platform access when required.
For article-format services, the final PDF or editorial source files are treated as the main input for conversion and quality-control workflows.
2. Technical review
JournalsHQ reviews the technical condition of the journal, including platform structure, metadata consistency, DOI signals, article formats, identifiers, public pages and possible risks before work begins.
3. Metadata and platform check
DOI, ISSN, title, publisher, license, references, ORCID and Crossref-related signals can be reviewed to identify gaps before deeper technical processing.
For OJS journals, this stage may include configuration review, plugin status, public visibility, journal structure and editorial workflow readiness.
4. XML/JATS, HTML and EPUB processing
When multi-format publishing is requested, article content is prepared as structured outputs such as JATS XML, academic HTML, EPUB, assets, tables, references and metadata files.
Outputs are prepared for review, not treated as invisible black-box conversion. The journal keeps a clear view of what was generated and what still needs editorial or technical verification.
5. QA diagnostics
JournalsHQ prepares diagnostics and quality-control notes to identify missing metadata, structure problems, asset issues, validation concerns or publication risks that require final review.
6. Delivery package
Depending on the service, the journal may receive organized packages containing XML/JATS files, HTML, EPUB, PDFs, figures, assets, metadata files, manifests and QA reports.
7. Human final review
Automated and semi-automated processing is not a substitute for editorial judgment. Final publication decisions, content approval and editorial validation remain with the journal team.
JournalsHQ supports the technical preparation layer so that human review can focus on clear, organized outputs.
Need a structured workflow for your journal?
Request an editorial technology diagnosis or contact JournalsHQ to review the current state of your journal platform, metadata or article-format workflow.
Request editorial diagnosis Contact JournalsHQ