Open Journal Systems (OJS)

Open Journal Systems – migrations, upgrades, maintenance

Open Journal Systems (OJS) is an open-source platform for publishing scientific journals: from manuscript submission, through peer review and editing, to publishing issues. Many editorial offices run older OJS versions that are complex to upgrade. I help move to a newer version and keep the platform in good shape.

Why an OJS migration is complex

Data and editorial history

Articles, issues, reviews, accounts and roles must move over completely and consistently.

Architectural change

Moving from OJS 2.x to 3.x requires transferring data into a new structure and recreating settings. I know both branches of the system, so I know what changes along the way in data, themes and plugins.

Themes and plugins

Custom themes and plugins from the old version usually have to be recreated or replaced.

Identifiers and URLs

URLs, DOIs and metadata must remain available to preserve citability and visibility.

OJS services

Upgrade from OJS 2.x to 3.x

Audit of the existing installation, migration on a test copy, review with the editorial office, and launch.

Migration from other systems

Moving a journal from another system or website into OJS: articles, issues and metadata.

Hosting and maintenance

Updates, backups, security and support for the editorial office. I offer my own hosting or adapt to the client’s environment.

Themes and appearance

Design and implementation of a journal theme, including responsive layouts.

Plugins and configuration

Selection, configuration and adaptation of plugins, and small feature extensions.

DOI and Crossref

Configuring DOI assignment and metadata export to Crossref in OJS.

Metadata and visibility

Correct configuration of metadata, URLs and content delivery so that publications are well visible online.

Training

Getting editors and administrators up to speed with the platform.

How an OJS migration works

  1. Audit – OJS, PHP and database versions, plugins, custom changes, number of journals and issues.
  2. Plan – scope, schedule, switch-over window.
  3. Test copy – migration in a separate environment, with no effect on the live journal.
  4. Verification – review of content, users, the editorial workflow and appearance.
  5. Launch – switch-over, redirects, post-launch checks.
  6. Aftercare – maintenance after launch (optional).

Experience

I have built OJS sites for scientific journal editorial offices, including Archives of Mechanics, Archives of Acoustics, Engineering Transactions, the Journal of Theoretical and Applied Mechanics, and the publishing platform of the Polish Mathematical Society.

Let's talk about your journal

Tell me which OJS version you use and what you want to achieve. I will propose a plan and a quote.