1 of 42

Advancing

Open Journal Infrastructure

for Open Research Europe

DAY MONTH YEAR

January 23, 2025�8-9 am PT

2 of 42

Introductions

  • Juan Pablo Alperin, Scientific Director
  • Alec Smecher, Development Associate Director / Infrastructure
  • Erik Hanson, Systems Developer / Open Peer Review
  • Vitaliy Bezsheiko, Software Developer / Workflow Lead
  • Parth Sarin, Systems Analyst / XML Production
  • Devika Goel, UI/UX Designer
  • Magnus Lu, Project Manager

3 of 42

Introduction to

Open Research Europe ( ORE )

Juan Pablo Alperin

4 of 42

Introduction to ORE

  • Open Access publishing Platform
    • no fees
    • “diamond”

  • Funded and supported by the EC
    • Horizons Europe (for now)

  • Immediate Publishing
    • Preprints, but not a preprint server

  • Post-Publication Open Peer Review

5 of 42

Diamond Open Access in Europe

6 of 42

EC begins move of ORE to open source

OJS does very well

In parallel…

7 of 42

PKP has been supporting Diamond

52,000+ Journals using OJS

also in parallel…

8 of 42

support for OJS/ORE

support for diamond OA

=

by aligning development for ORE with PKP community priorities

9 of 42

OJS

Enhancements

In Progress

Alec Smecher, Erik Hanson, Vitaliy Bezsheiko, Parth Sarin

10 of 42

ORE and OJS

  • ORE will (re)launch in 2026 using OJS 3.6�
  • It will be a combination of…
    • New features built into OJS and available to all,
    • Configuration of OJS to suit ORE’s requirements, and
    • Limited ORE-specific development (e.g. theming)�
  • Some features will need better-than-basic hosting.
    • These are available to all as FOSS, but will not run on all server environments.
    • Example: Lucene

11 of 42

For Today…

  • Open Peer Review (Erik)
  • Preprints (Alec)
  • Typesetting and XML (Parth & Vitaliy)

12 of 42

Open Peer Review

What’s coming next?

  • Post-publication open peer review
  • Publicly visible author responses
  • Public comments

13 of 42

14 of 42

15 of 42

Preprints in OJS

  • OJS 3.6 will gain a preprint posting workflow
  • This will be built onto the existing versioning tools
  • ...adding NISO JAV (Journal Article Versioning)

16 of 42

Versioning and Stages

Specifications available on Github issue #4860:

https://github.com/pkp/pkp-lib/issues/4860

In OJS 3.5.0 and older: Version 1, 2, 3, …

�With 3.6.0:

  • Every “version” has a stage (e.g. Author’s Original) and a number (1.0, 1.1, 1.2, 2.0)
  • Every version is either “major” or “minor”

17 of 42

18 of 42

19 of 42

20 of 42

21 of 42

What about OPS?

OPS serves a different purpose and we will continue to develop it!

OJS: The research is made available early on a journal website and will later be published there as a full-fledged article.�

OPS: The research is made available early in OPS and will eventually be published as an article elsewhere. Examples: SportRxiv; Jxiv

22 of 42

XML Production

Production of HTML, PDF galleys

Article and metadata upload

Editing and typesetting

23 of 42

Article and Metadata Upload

  • Support for automated import of articles (e.g. from DOCX or PDF format using GROBID or other AI tools)
  • For import procedures that don’t require automated metadata identification, pandoc and similar libraries enable markup of Zotero references, headings, etc.

Production of HTML, PDF galleys

Article and metadata upload

Editing and typesetting

24 of 42

Editing and Typesetting

  • To assist with XML production, OJS 3.6 will include an article editor
    • Journal staff can edit articles in HTML format
    • Export to XML, forwards and backwards compatibility with JATS

Production of HTML, PDF galleys

Article and metadata upload

Editing and typesetting

25 of 42

Editing and Typesetting

  • Shortlisted ten editor packages
    • Two JATS editors, five HTML editors, one low-level editor infrastructure package, and two scholarly HTML editors
  • Met with the developers of three
  • Events to engage the PKP community in October & November 2024:
    • PKP sprint in Turin, Italy
    • Virtual meeting of the PKP Production Workflows Working Group

26 of 42

Editing and Typesetting

  • “Low fidelity” typesetting — a robust solution for basic JATS elements rather than a more sophisticated editor that could handle the entire JATS vocabulary
    • Phased-in options to improve the production fidelity with plugins
  • Core elements for “low-fidelity” JATS based on an analysis of JATS corpora from ORE, SciELO, Redalyc, Coalition Publica — and requirements for PubMed Central and JATS4R

27 of 42

Editing and Typesetting

Elements to support in the article body:

  • block elements: paragraph, list, section, heading, table/row/cell, figure, caption, footnote, equation
  • inline elements: bold, italic, underline, link, citation

28 of 42

Editing and Typesetting

  • Customizable templates for PDF and HTML production
  • Currently investigating tools for templated export from the editor, including mPDF, PagedJS, Vivliostyle, Weasyprint.

Article and metadata upload

Editing and typesetting

Production of HTML, PDF galleys

29 of 42

User Testing & Feature Development

Devika Goel

30 of 42

Feature Development Process for ORE

Issue Identification & Specification

UX/UI Design & Validation

Feature Development

Quality Assurance & Deployment

Review by the "Three Amigos"

31 of 42

Opportunities For User Testing

Issue Identification & Specification

UX/UI Design & Validation

Feature Development

Quality Assurance & Deployment

Review by the "Three Amigos"

32 of 42

Opportunities For User Testing

Issue Identification & Specification

UX/UI Design & Validation

Feature Development

Quality Assurance & Deployment

Review by the "Three Amigos"

You can provide your feedback or suggestions on how the feature should work by commenting on the GitHub issue or reaching out to me directly.

33 of 42

Opportunities For User Testing

Issue Identification & Specification

UX/UI Design & Validation

Feature Development

Quality Assurance & Deployment

Review by the "Three Amigos"

You can provide your feedback or suggestions on how the feature should work by commenting on the GitHub issue or reaching out to me directly.

Sign up via the sheet on our website to participate in user testing and share your feedback.

34 of 42

ORE Roadmap

Magnus Lu

35 of 42

ORE Roadmap

Deliverables

Target Completion

Design

Q4 2025

Development & Testing

Q1 2026

Platform Handover

Q3 2026

Final code, manuals, and documentation

Q3 2026

36 of 42

ORE 2024/2025 Timeline

Q2 2025

DEVELOPMENT & TESTING

Infrastructure

Typesetting & JATS

Distribution / Integration

Theming

Iterative testing

Q1 2025

STUDY, DESIGN & DEVELOPMENT:�

Infrastructure

Typesetting & JATS

Distribution / Integration

Theming

Iterative testing

Q4 2024

STUDY:�

Infrastructure

Typesetting & JATS

Integration points

Q3 2025

DEVELOPMENT & TESTING

Typesetting & JATS

Distribution / Integration

Theming

Iterative testing

37 of 42

References

38 of 42

ORE Alignment with Existing Community Priorities

  • Restrict Editor Access to Settings; GitHub #5504
  • Journal-wide UI for tracking deposits & distributions; GitHub #5980
  • Suggest reviews on submission; GitHub #4787
  • Allow a journal to define a limited set of keywords and reviewer interests; GitHub #1550
  • Continuous publication; GitHub #9295
  • Customizable reviewer recommendations; GitHub #1660
  • Support version type & summaries; GitHub #4860
  • Multiple file uploads in HTML galleys #4947

39 of 42

References

40 of 42

Q&A

41 of 42

Thank you!

42 of 42

Except where otherwise noted, this presentation is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License