Index Production and OJS: how to automate editorial production without changing Open Journal Systems

The integration of Index Production and OJS shows how to automate editorial production without changing Open Journal Systems or altering the way the journal works. OJS has become an essential tool for thousands of scientific journals, universities and academic publishers, as it lets them manage manuscript submission, peer review, editorial decisions and article publication from a single environment.

However, even when a journal has a well-organised editorial workflow in OJS, the post-acceptance phase is still, in many cases, slow and manual: copyediting, typesetting, PDF preparation, HTML generation, JATS XML creation, proof review and applying changes across different files.

Index Production fits in at this point to make editorial production easier without forcing the journal to leave OJS or change the way it works.

OJS remains at the heart of the editorial workflow

The purpose of Index Production is not to replace OJS. The journal can keep using Open Journal Systems to manage authors, reviewers, editors, submissions, editorial decisions, issues and publication.

Index Production is added as a layer specialised in production, between the accepted manuscript and the final article formats.

This way, each tool does what it was designed for:

  • OJS manages the editorial process and publication.
  • Index Production turns accepted content into professional, publication-ready formats.

The editorial team keeps its procedures, its people in charge and its usual environment. There is no need to rebuild the workflow or move the whole journal to a new platform.

How does Index Production integrate with OJS?

Once the article has passed peer review and been accepted, the final manuscript and its metadata can be brought into Index Production to start the production phase.

Index Production interprets the document structure and identifies its main elements: title, authors, affiliations, abstracts, sections, tables, figures, references and other editorial metadata. It then normalises the content and lets the team review and correct the article before generating the final formats.

From a single structured source, Index Production produces:

  • PDF with the journal’s own design;
  • HTML for online publication and reading;
  • JATS XML for interoperability, preservation and indexing;
  • EPUB and other formats when the project requires them.

Once validated, these files are added back to the article in OJS as publication formats or galleys. The exact exchange method can be adapted to each institution’s technical setup and procedures.

The result is a simple path:

Article accepted in OJS → production in Index Production → editorial review → multi-format generation → publication in OJS.

One correction for all formats

In a traditional process, the PDF, HTML and XML are usually worked on separately. This means a correction made in one format is not always reproduced correctly in the others.

Index Production works from a single source of structured content. The different formats are therefore generated from the same information and stay in sync.

This model reduces duplication, avoids contradictory versions and makes proof review easier. In addition, each journal keeps its visual identity through a custom template that is configured once and can be reused for subsequent articles

Especially useful for universities and publishing groups

Integrating Index Production with OJS is particularly interesting for universities, libraries and publishing services that manage several journals from a single installation.

These teams often face a common challenge: each journal has its own design and guidelines, but the institution needs to maintain consistent technical criteria, control quality and publish without constantly increasing the resources devoted to production.

Index Production makes it possible to standardise the technical side without making the journals uniform. Each publication can keep its masthead, typefaces, styles and editorial structure, while the institution works with a common, scalable production model.

This makes it easier to:

  • produce more articles with the same team;
  • reduce manual, repetitive tasks;
  • keep PDF, HTML and JATS XML consistent;
  • reduce dependence on different providers;
  • prepare structured content for distribution and indexing;
  • better control publication times and quality.

Automating does not mean replacing the editorial team

Index Production does not make scientific decisions or replace the judgement of editors, copyeditors or publication managers. Its role is to reduce the time spent on mechanical operations and prevent the team from having to repeat the same corrections in several formats.

Automation lets professionals focus on the tasks where they really add value: reviewing content quality, ensuring compliance with editorial guidelines, improving metadata and developing the journal’s strategy.

OJS and Index Production: a more complete editorial workflow

OJS provides a solid infrastructure for managing and publishing scientific journals. Index Production extends its possibilities in one of the most complex phases of the process: turning the accepted manuscript into a multi-format digital publication.

It is not about changing platforms, but about adding a specialised tool where the workflow needs most support.

To see how it would work for a specific journal, a demo can be carried out with a real article, turning it into PDF, HTML, JATS XML and EPUB while keeping the publication’s design and editorial criteria.