SFU.CA

OJS, OMP, and OPS 3.6 in a Nutshell

The OJS, OMP, and OPS logos are at the bottom left of the image. The text reads the same as the post title. The photograph is of nuts in their shells set on a background of Fall leaves.
Photo of nuts in their shells by Wouter Supardi Salari.

The upcoming 3.6 release introduces new features and improvements across OJS, OPS, and OMP including flexible publication and revision workflows, improved editorial task management, strengthened scholarly metadata, and new tools for content production, distribution and discovery.

Editorial Workflow and Task Management (OJS, OMP, OPS)

GitHub: #10406

YouTube: Tasks and Discussions

Editors can now create reusable tasks with predefined descriptions that can be edited at any time. Editors can configure the template for automatic creation (#11993) and designate the task to a workflow stage: submission, review, copyediting and production. These scheduled tasks will automatically appear once the submission enters the stage. 

Editors can also create tasks manually and add a task owner, due date, description, start a discussion within the task, and add participants to the discussion. 

Continuous publication (OJS, OMP, OPS)

GitHub: #9295

YouTube: Preprints and Continuous Publication

Continuous publication provides greater flexibility in how content is released. By making the requirement to associate a publication with a journal issue optional, articles can be published as soon as they are ready, giving publishers the flexibility to manage publication schedules and reduce delays between acceptance and publication. Issues can then be assembled using content that has already been published.

Structured Citations (OJS, OMP, OPS)

GitHub: #10692

YouTube: Structured Citations in OJS 3.6

The structured citations feature allows authors and editors to enter multiple references in one open-text field, triggering metadata lookup services such as Crossref. This service lookup attempts to match the reference with DOI and citation metadata and structures the data, if a match is found. References without a metadata match can be manually added. Structured citations are mapped to supported JATS elements (GitHub #10435).

Improvements to Search (OJS, OMP, OPS)

GitHub: #8920, #8915

The goal of the search infrastructure update was to improve search accuracy, performance, and scalability. The new framework uses Laravel Scout and supports OpenSearch as an alternative search backend. The built-in database search engine has also been rewritten, providing an improved default search option without requiring administrators to install a separate search service.

Reader-facing Improvements (OJS, OMP, OPS)

The 3.6 release includes improvements to the presentation of publication metadata, journal content organization, content discovery and search, and gives readers more context about the research and contributors. Examples include:

Journal Article Versioning (OJS *)

GitHub: #4860

YouTube: Preprints and Continuous Publication

OJS 3.6 introduces a versioning system based on NISO’s Journal Article Versioning recommendations. Articles can be identified by standardized lifecycle stages such as Author’s Original (AO), Published Manuscript Under Review (PMUR), and Version of Record (VoR). Revisions can be classified as major or minor and numbering follows semantic versioning. For example, a new lifecycle stage starts at version 1.0. A major revision increments the major number while a minor revision increments the minor number. The version management also allows editors to create an unassigned version before assigning it to a lifecycle stage later in the process.

The implementation of journal article versioning improves the overall clarity of an article’s publication state, review history, and subsequent revisions.

*The underlying publication versioning is shared across the three publishing platforms but the JAV lifecycle stages are specific to OJS.

Open Peer Review (OJS)

GitHub: #11309

YouTube: Peer Review (from PKP Development News Update February 2026)

Journal managers have the option to employ the traditional pre-publication peer review model or adopt the open peer review (OPR) model. OPR allows journals to make reviewer identities and peer review reports public. OPR capabilities include publicly available reviewer reports, transparency of a reviewer’s identity, the ability for editors to edit the author-facing portion of submitted reviews (#13110), and making reviews publicly available following the editor’s confirmation (#12855).

Integrated Text Editor (OJS)

GitHub: #10419

PKP News: Manuscript Editing and Production Under One Roof

Editors and production staff have the option of editing the body text of their submissions with an integrated editor. This reduces reliance on external production services but allows publishers to continue using their existing workflow. 

The resulting file generated by the text editor and saved to OJS is what enables the system to perform the integrated file production.

Integrated File Production (OJS)

GitHub: #48 

PKP News: Inside OJS’ File Production and Toolset

HTML and PDF files can be generated with the click of a button inside the integrated text editor interface. You have the option of downloading the file or adding it to the galley. These files appear on the public-facing site as downloadable files.


We look forward to hearing how the PKP community puts these new capabilities into practice. Stay tuned for news about the 3.6 release.