Getting Ready for OJS 3.0: When Should I Upgrade?

August 29th, 2016 by  | 4 Comments

With the upcoming release of OJS 3 on August 31, you will likely be thinking about when you should upgrade. Here’s what you need to know.

Overview

OJS 3.0 contains a lot of new concepts and code, so it’s important to plan your migration from OJS 2.x to OJS 3.x in a way that doesn’t disrupt your publication schedule overmuch. Additionally, some features that are available in OJS 2.x will not be immediately available in OJS 3.0, such as subscription-based access. Similarly, only four language translations — English, German, Portuguese, Spanish — will be available initially.  Most of these features and additional languages will follow in later releases according to community interest; please feel free to inquire about details on our community forum.

OJS 3.0 will include migration tools to upgrade your OJS 2.4.x installation, preserving all content and workflow details. If you are running OJS 2.3.x or older, you will first need to upgrade to OJS 2.4 or later. We recommend performing a test upgrade and exploring the new version of the system before performing a production upgrade. Note that you must make a complete, separate backup copy of your installation; the upgrade process will affect your database and file storage area, and downgrades from 3.0 back to 2.4.x will not be supported.

OJS 3.0 will perform best for open-access publications with small to medium-sized amounts of content. As the new codebase matures with follow-up releases, we will ensure its performance with larger collections and higher traffic volumes. We welcome feedback and bug reports and will support OJS 3.0 as a production release.

Customizations made to your OJS 2.x installation will not easily apply to OJS 3.0, as many underlying concepts have changed considerably. Watch our developer blog for information on developing for OJS 3.0. Much of what has been introduced in OJS 3.0 is based on years of community feedback, so it’s also possible that OJS 3.0 will meet more of your requirements without customization. Certain common customizations have been made much easier, such as theming.

What about OJS 2.x?

We will continue to maintain OJS 2.4.x for the foreseeable future to allow users to migrate at their own pace.

As OJS 3.0 matures and adoption increases, we will decrease development effort on OJS 2.x correspondingly. It will continue to receive minor translation updates, bug fixes, and particularly security updates, at least through 2016 and 2017. An end-of-life has not yet been scheduled.

How do I upgrade?

  1. Read the upgrade documentation. It is included in OJS 3.0 in docs/UPGRADE (also available on github). Ensure, for example, that your server meets OJS 3.0’s requirements, and that your OJS 2.x installation is not too old to be upgraded to OJS 3.0.
  2. Perform a test upgrade. To do this, you will need to make a complete copy of your OJS 2.x journal, including the database and files area. Follow the upgrade instructions on that copy.
  3. Once you’re satisfied with the test upgrade, repeat the upgrade steps with your production installation, making sure to keep a complete backup handy.

Tags:

4 Comments on "Getting Ready for OJS 3.0: When Should I Upgrade?"

  1. Drew says:

    How can i confirm the OJS version I have? I believe is is older than OJS2 but I’m not sure.

  2. Priy brat says:

    Is it possible to have multiple journals in same platform or need separate website for all journals

Comments are now closed.