JATS XML Converter Service enables users to convert full-text Open Office (.docx) files into JATS XML (Journal Publishing v1.1) format. The service helps editors and researchers prepare scholarly articles for digital publishing, indexing, long-term preservation, and interoperability with academic publishing platforms and repositories.
Tool ID card
Main purpose: Conversion of scientific and professional journal articles from .docx format into machine-readable JATS XML format for publishing and archiving.
Who is it for? Editors of open access scientific and professional journals, as well as members of the academic and research community.
Converts .docx articles into JATS XML (Journal Publishing v1.1)
Extracts article metadata, references, images, formulas, acknowledgments, and full text
Enables editing of the generated JATS XML directly within the tool
What can I do with it?
Convert journal articles from .docx into standardized JATS XML format
Prepare articles for open access journal publishing platforms
Generate machine-readable XML files including metadata, references and full-text
Export structured article content for indexing and archiving
Good to know
Access requires an active electronic identity within the eduGAIN authentication system
Users are responsible for checking and refining the generated XML files
University of Zagreb University Computing Centre - SRCE as a service provider does not guarantee content accuracy of generated JATS XML files (https://www.srce.unizg.hr/hrcak/jats/terms)
Try it if you…
Edit or manage an open access scientific journal
Need JATS XML files for journal publishing workflows
Want to simplify conversion from Word documents to XML publishing formats
Thank you to Draženko Celjak (@dceljak) and Ljiljana Jertec Musap (@ljiljana) for writing this post!
This looks like a great tool and I’d love to learn more! I sent a mail yesterday about some apparent technical issues on the page, it seems that I can’t load the documentation. Just mentioning it here in case the mail didn’t go through somehow.
Edit: I checked the documentation again today, it’s working now.
Hi, thank you for pointing this out. We have investigated the issue and believe that we have resolved the error. Could you please try again and let us know if it’s working now?
We work extensively with XML-JATS production for Diamond OA journals, and one recurring challenge is not only conversion itself but ensuring consistency between the article metadata, Crossref deposits, platform metadata and the final JATS output.
From our experience, the most valuable automation is often the one that reduces duplication between these different stages rather than treating XML generation as an isolated final step.
It would be interesting to know whether the tool is also considering validation against upstream metadata sources or interoperability with journal management systems.
Hi Carme, the tool integrates journal and article metadata into the JATS output. Concerning the upstream (Crossref) and downstream (publisher platform) metadata compatibility, @ljiljana and @dceljak are better fit to answer, as they operate both the tool and the Portal of Croatian Scientific and Professional Journals - HRČAK platform. In any case the metadata mapping and synergy issues you are mentioning are interesting, would you like to present those in the EDCH “Tools and Technology” Task Force ?
Yes, absolutely — we would be very happy to present this in the Tools and Technology Task Force.
We have recently applied to join the TTTF, as these questions around metadata interoperability, reuse and consistency across publishing workflows are very closely aligned with our work.
We could share some practical experiences from Diamond OA journal workflows, particularly around keeping metadata consistent across journal platforms, Crossref deposits, JATS XML, indexing/discovery services and final publication outputs, as well as where we currently see duplication and opportunities for better interoperability.
Please let us know what format and length would be most useful for the Task Force, and we would be happy to prepare a short presentation or practical use case. We can use tha chat to talb about the presentation!
Hello, here’s another solution (for now specifically tuned for SciELO).
It works as an automatic conversion tool that transforms DOCX files into SciELO-compatible JATS XML. While it is still in its beta version, the tool is fully functional and free to use in self service for non-commercial purposes (up to 5 conversions per month).
I would love to hear your thoughts and receive any suggestions for improvement.
You can test it here: 🧪️ Solutions
For complex journals or high-volume requirements requiring tailored markup, layout, or DOI integration, we provide customized professional services.
