Skip to main content

Services · OJS and OMP

Your journal system, up to date, secure and correctly configured

OJS and OMP are PKP's open source publishing management systems. They are easy to install, but upgrades, security updates and sending metadata to external systems take regular work. Silsile does this on the institution's own server or with the hosting provider it chooses; the system and data always stay with the institution.

What the service covers

Items can be ordered separately; for most journals we agree the scope in the first call.

Installation
Installing OJS or OMP, setting up languages and email, user roles, and the submission and review workflow.
Upgrades
Moving from older versions to the current long-term support release, migrating content, users and files in full, with a full backup and a trial run beforehand.
Regular maintenance
Following and applying security updates, regular backups with restore tests, and removing fake users and spam registrations.
Plugins and integration
Settings for Crossref, ORCID, ROR, DOAJ, Google Scholar and the PKP Preservation Network, so that metadata reaches external systems in full.
Themes
Accessible, multilingual themes that fit the institution's identity and work on phones; adapting existing themes to the current version.
Troubleshooting
Finding and fixing problems such as email delivery, slowness, failed DOI deposits and broken links.

How an upgrade is done

The upgrade is tried on a copy before the live system is touched.

  1. Assessment

    Version, plugins, theme, data size and server conditions are reviewed; the upgrade path and timetable are set out in writing.

  2. Backup and trial

    A full backup of the database and files is taken, and the upgrade is first run on a copy.

  3. Upgrade

    The live system is upgraded on the agreed date, with plugin and theme adjustments.

  4. Checks

    Submission, review, publication, DOI deposit and email are tested, and editors get a short summary of what changed.

For journals on OJS 3.3

According to PKP's download page, OJS 3.3 is a long-term support release that will be supported until at least 1 January 2027. The current long-term support release is OJS 3.5. Because 3.3 support is time-limited, journals using it are advised to plan their upgrade in advance.

OJS 3.4 brought DOI management into a single screen, so an upgrade is also a good moment to review Crossref records.

Crossref DOIs for a journal: guide

Frequently asked questions

Do you move our system to your server?

No. The system stays on the institution's own server or with the hosting provider it chooses; Silsile carries out installation, maintenance and upgrades there.

Will the journal go offline during the upgrade?

Because the upgrade is first tried on a copy, downtime on the live system is kept short, and the timetable is agreed in advance.

Can we move from DergiPark to our own OJS site?

Yes. Keeping the earlier DOIs and choosing a DOI route for new content are planned separately; the details are in our Crossref DOI guide.

How is the price set?

Each job gets a separate written proposal. Installation and upgrades are priced once; maintenance is priced annually.

Requesting a proposal

Tell us briefly which system you use (OJS or OMP), its version, your site address and what you need.

Request a proposal