What Is OJS and Why Do Universities Use It?
Open Journal Systems — universally abbreviated OJS — is an open-source journal management and publishing platform developed by the Public Knowledge Project (PKP) at Simon Fraser University. OJS is used by tens of thousands of peer-reviewed journals across more than 140 countries, making it the single most widely adopted journal management system in the world. For universities and research institutions launching a new peer-reviewed journal, OJS is the effective global standard — required by DOAJ's best practice criteria, compatible with Google Scholar's indexing requirements, and freely available to any institution without licensing fees.
What does OJS actually do?
OJS manages the entire lifecycle of a peer-reviewed article — from the moment an author submits a manuscript to the moment the published article appears on the journal website. It handles author registration and submission, editorial assignment, peer reviewer invitation and tracking, editorial decision-making, revision management, copyediting, layout, and final publication. Everything a journal needs to run a professional peer review process is built into OJS.
Beyond workflow, OJS also generates the machine-readable metadata that enables indexing. It produces an OAI-PMH feed — the protocol DOAJ uses to harvest article records — and outputs Dublin Core and other metadata formats that Google Scholar and library systems read automatically. A correctly configured OJS installation is not just a management tool; it is the technical backbone that connects a journal to the global scholarly infrastructure.
Why do universities choose OJS over alternatives?
OJS is free, self-hosted, and owned entirely by the institution that installs it. There are no per-article fees, no subscription costs, and no dependency on a commercial vendor who can change pricing or discontinue the service. For universities in the UAE, Saudi Arabia, Qatar, and across the Gulf — where institutional control over research infrastructure is a priority — OJS's open-source, self-hosted model is a significant advantage over subscription platforms.
OJS is also the platform most explicitly supported by the global indexing ecosystem. DOAJ's own technical guidance specifically references OJS when explaining OAI-PMH feed configuration. PKP, the organization that develops OJS, also develops PKP Preservation Network — a free long-term digital preservation service that is available only to OJS-hosted journals. No commercial competitor offers equivalent preservation infrastructure at no cost.
- Free to install — no licensing or per-article fees
- Fully self-hosted — the institution owns all data
- Built-in OAI-PMH feed for DOAJ, Google Scholar, and library discovery systems
- PKP Preservation Network — free digital archiving (OJS journals only)
- Used by tens of thousands of journals — largest global support community
- DOAJ's technical documentation is written for OJS by default
What does a correct OJS installation include?
A bare OJS installation — downloaded from pkp.sfu.ca and placed on a web server — is not a functional journal. It requires configuration of the journal's sections, peer review workflow, author guidelines, editorial policies, and all the public-facing pages (About, Editorial Board, Aims and Scope, Peer Review, APC policy) that DOAJ requires to be present and accurate before an application can be submitted.
Critical plugins must also be configured: the DOI plugin (to assign permanent identifiers to articles), the OAI-PMH plugin (to enable metadata harvesting), and the PKP Preservation plugin (to activate long-term archiving). Unconfigured plugins leave the journal technically incomplete even if the website looks finished.
The custom theme — replacing OJS's default visual design with the journal's branding — is another required step. DOAJ reviewers specifically check that the journal does not present with default OJS styling, which they interpret as a signal that the journal is not genuinely operational.
How does OJS connect to DOAJ and Google Scholar?
OJS connects to DOAJ through its OAI-PMH feed — a standardized protocol that allows DOAJ's servers to automatically pull article metadata (title, authors, abstract, DOI, issue, date) from the journal without any manual upload. Once a journal is listed in DOAJ and the feed URL is registered, every new article published in OJS is automatically indexed in DOAJ's database within days.
Google Scholar indexes OJS journals through a different mechanism: Scholar's crawlers look for specific meta tags in each article's HTML — the citation_title, citation_author, citation_doi, and related tags that OJS generates automatically when the metadata plugin is active. If these tags are missing, Scholar will not index the journal even if it can access the website.
Which version of OJS should you install?
As of July 2026, the current stable release is OJS 3.4. TRIM Global installs OJS 3.4 for all new journals. Earlier versions (3.2 and below) have reached end-of-life for security updates and are no longer compatible with the most recent versions of critical plugins. A journal running OJS 3.1 or earlier is both a security risk and progressively less compatible with the current DOAJ and Google Scholar technical requirements.
What goes wrong with self-managed OJS installations?
The most common problems TRIM Global encounters when auditing self-installed OJS journals are: OAI-PMH feed disabled (making DOAJ article harvesting impossible), DOI plugin inactive (so articles are published without permanent identifiers), default OJS theme still active (triggering DOAJ rejection), and SMTP email not configured (so peer review notifications never reach reviewers). All four are invisible to the editor looking at the journal website but cause real operational failures.
Server configuration issues are the other major failure point. OJS requires specific PHP settings, database configuration, and file permissions that differ from standard WordPress or static-site hosting setups. An OJS installation on incorrectly configured shared hosting will appear to work normally until a large file upload triggers a PHP memory limit error, or until a scheduled task — like automated email reminders to reviewers — silently fails because cron jobs are not configured.
Every plugin configured. Every policy page written and live. DOAJ-ready from the day we hand it over. 1,000+ journals launched across the Gulf, Europe, and North America.