The Public Knowledge Project (PKP) has unveiled one of the most transformative updates to the Open Journal Systems (OJS) platform:
Preprints and Continuous Publication are now natively integrated in OJS 3.6 — a long-awaited step toward faster, more transparent, and flexible scholarly communication.

Developed under the Open Research Europe (ORE) initiative and funded by the European Commission, this release redefines how journals can manage the flow of research—from first submission to final publication.

“With OJS 3.6, journals can publish preprints, release articles continuously, and update versions without losing transparency.”

🚀 Key Advancements in OJS 3.6

1. Preprint Workflow Integration

Editors can now publish submissions before peer review as Author’s Original (AO) versions, and later upgrade them to Version of Record (VoR) once peer review is complete.

How it works:

• Submit → Publish as Preprint (AO)
• Peer review and production → Publish as Version of Record (VoR 1.0)
• Minor correction → VoR 1.1

This unified workflow means journals no longer need separate systems like OPS to handle preprints.

Example: A paper can be made public as a preprint today and officially released as a peer-reviewed VoR version next month, all within the same OJS installation.

🎥 Watch the official presentation: Preprints and Continuous Publication in OJS 3.6 – thanks to OSS ORE and the European Commission.

2. Continuous Publication Model

Traditionally, OJS tied every article to a journal issue.
Now, with Continuous Publication, that limitation is gone.

Editors can:

• Publish articles immediately, without waiting for an issue to close.
• Assign those articles to an issue later, if desired.
• Organize content thematically using categories rather than issues.

“Publish first, organize later — OJS 3.6 makes it possible.”

This model benefits open-access and fast-moving journals that value immediacy and reader access.

🧭 Adopting the NISO JAV Standard

OJS 3.6 introduces formal terminology and structure through the NISO Journal Article Versioning (JAV) standard.
This ensures interoperability between publishers, repositories, and indexing systems.

Each revision is preserved and citable — improving traceability and trust in the scholarly record.

🧩 Three Publishing Models, One Platform

OJS 3.6 allows journals to combine or choose between three workflows:

1. Traditional Issue-Based Publishing
   • Peer review → Issue assignment → VoR 1.0 publication.
2. Hybrid Preprint → VoR Publishing
   • Early Preprint (AO) release → later upgraded to VoR 1.0 (and minor updates like 1.1).
3. Fully Continuous Publishing (No Issues)
   • Articles appear immediately and are organized by categories or thematic collections.
   • Issue-related fields are automatically hidden for simplicity.

Tip: Editors can mix and match — some sections may follow issues, others continuous publication.

⚙️ Simplified Editor Experience

📋 Streamlined Workflow Interface

• The Version Management tool has been moved to a clear sidebar.
• The Schedule for Publication button can now be used from the earliest stages.
• Editors can decide for each article whether it’s a Preprint, VoR, or Continuous Publication item.

🏠 Homepage Display Options

Editors can now select which components appear on the journal’s homepage:

• Current Issue
• Most Recent Articles (for continuous publication)
• Thematic Categories

All can be displayed independently or together.

🔗 DOI, URLs, and Indexing Compatibility

• Each version (AO and VoR) can have a distinct DOI, with cross-links between them.
• Article URLs without version identifiers always point to the latest version—ideal for readers.
• Google Scholar and indexing systems will gradually adapt to versioned metadata as the NISO JAV standard becomes widely recognized.

“Readers always land on the latest version — without losing access to previous ones.”

🧮 Zero-Configuration Philosophy

Gone are the endless checkboxes.
OJS 3.6 introduces a “zero-configuration” approach — editors make decisions at the article level, not in global settings.

Benefits:

• Cleaner setup screens
• More flexibility for hybrid workflows
• Easier long-term maintenance and upgrades

🔮 Roadmap and Performance Outlook

• OJS 3.5 will serve as the Long-Term Support (LTS) version — stable for large datasets.
• OJS 3.6 focuses on innovation and testing new workflows like preprints and continuous publication.
• OJS 3.7 will consolidate these features into the next LTS release.

“3.6 is the testing ground; 3.7 will be the lasting foundation.”

Performance improvements from 3.5 are also being ported to 3.6, ensuring scalability for large journal installations.

🛠️ Coming Soon: In-Platform Typesetting & New Theme

Two major enhancements are in active development:

1. Integrated Typesetting Workflow
   • Edit article body text directly in OJS.
   • Export polished PDFs and HTML versions without external tools.
2. Next-Generation Theme System
   • Built-in version badges and clearer “Preprint / VoR” indicators.
   • Cleaner layout and easier customization via the AI-Theme framework.

🧾 Recommendations for Editors

1. Define Your Publication Policy
   • Clarify how preprints and continuous publication fit into your journal.
2. Establish a Versioning Policy
   • Use structured versioning: 1.0 → 1.1 → 2.0.
3. Manage DOI Strategy
   • Assign separate DOIs for AO and VoR, and link them for indexing.
4. Update Homepage and Theme
   • Highlight version info and preprint notices clearly.
5. Prepare for Indexing Changes
   • Maintain consistent metadata and clean URLs for versioned content.

📆 Release Timeline and Journal Support

OJS 3.6 is expected to be officially released during 2025.
This version will not be marked as LTS, as it primarily focuses on testing and refining new workflows.
The following version, OJS 3.7, will integrate these features as part of a stable LTS release.

These details are preliminary and may evolve as development progresses.
Once these features are fully stable and available, we will contact all journal managers we serve to provide guidance, migration options, and implementation support.

Commitment: At OJS-Services.com, we ensure every journal stays aligned with the latest, most stable, and standards-compliant OJS evolution.

The post Preprints and Continuous Publication in OJS 3.6 first appeared on OPEN JOURNAL SYSTEM SERVICES.

To achieve full OpenAIRE compliance, OJS journals must accurately classify their content using the COAR Resource Type system.

What Is the COAR Resource Type Classification System?

In the world of open-access publishing, content is only as visible as the metadata behind it.
The COAR Resource Type Classification System — developed by the Confederation of Open Access Repositories (COAR) — provides a unified way to describe what kind of resource a publication really is.

Whether it’s a research article, dataset, software package, or interactive web resource, this classification ensures that repositories, harvesters, and indexing systems like OpenAIRE, Crossref, or ORCID can accurately recognize and categorize your content.

It’s not just a list of labels — it’s the universal vocabulary of academic content.

Why It Matters

• ✅ OpenAIRE Compliance: Ensures your OJS journal metadata meets European Open Science standards.
• 🌐 Global Discoverability: Makes your publications compatible with international repositories and aggregators.
• ⚙️ Consistent Metadata: Standardizes resource descriptions across OJS, DSpace, Zenodo, and other open repositories.
• 📊 Interoperability: Enables seamless exchange of records via OAI-PMH and other metadata protocols.

How It Works in OJS

The OpenAIRE plugin for OJS integrates COAR Resource Types directly into your journal’s metadata.
When activated, the plugin automatically maps each article type to a corresponding COAR category — ensuring that your repository exports valid and compliant records through the OAI-PMH interface.

This not only saves editorial time but also guarantees that your journal meets the OpenAIRE Guidelines for Literature Repository Managers (v4.0).

COAR Resource Type Categories

Below is a practical overview of the main COAR categories and what kind of materials they typically represent in research publishing.

🎨 Artistic Work

Creative outputs such as performances, exhibitions, digital art, and visual installations — often published by arts faculties or cultural repositories.

🗺️ Cartographic Material

Spatial and geographic representations.

• Map: Topographic or thematic maps used in earth sciences, geography, and urban studies.

📦 Collection

Curated groups of related content, often organized by project, author, or topic.

• Archival Collection: Historical records, correspondence, or digitized archives.
• Court Documents: Legal records or case files.

📊 Dataset

Structured data from research activities — essential for reproducibility and open science.
Examples include:

• Experimental Data: Lab results, measurements, or sensor data.
• Survey Data: Results from questionnaires or social research.
• Genomic Data: DNA sequencing and bioinformatics data.
• Simulation Data: Model outputs and computational analyses.
• Laboratory Notebook: Raw experimental notes and logs.

💡 Design

Creative and technical design outputs.

• Industrial Design: Product or engineering prototypes.
• Layout Design: Publication layouts or digital interface designs.

🖼️ Image

Visual or multimedia content.

• Still Image: Photographs, figures, illustrations.
• Video (Moving Image): Recorded lectures, animations, or documentaries.

🌐 Interactive Resource

Web-based or user-interactive materials.

• Website: Research portals, educational microsites, or project dashboards.

🧭 Knowledge Organization System

Taxonomies, ontologies, and controlled vocabularies used to organize information within repositories and research databases.

🎓 Learning Object

Educational or training materials — including e-learning modules, tutorials, and teaching resources.

💻 Software

Code and computational tools used in research.

• Research Software: Analytical or simulation software developed for scientific studies.
• Source Code: Original programming code in any language (e.g., Python, R, PHP).

📚 Text

The most comprehensive category, covering all text-based academic outputs.
Includes:

• Book / Book Part: Monographs, edited volumes, or chapters.
• Journal Article: Research, review, data, or software papers.
• Thesis: Bachelor’s, master’s, or doctoral dissertations.
• Conference Output: Papers, posters, or presentations.
• Report: Technical, policy, or project deliverables.
• Preprint: Early versions of manuscripts before peer review.
• Review / Commentary / Peer Review: Evaluation or critique articles.
• Working Paper: Preliminary findings shared before formal publication.

🔊 Sound

Audio recordings, interviews, and music compositions — commonly used in ethnography, linguistics, and digital humanities.

⚙️ Workflow

Digital representations of processes, pipelines, or methodological steps.
Useful for documenting AI model training, laboratory procedures, or research automation.

Integrating COAR Resource Types in OJS

OJS users can easily implement the COAR system using the OpenAIRE plugin, ensuring:

• Automatic assignment of resource types to submissions.
• Metadata validation for OpenAIRE harvesters.
• Improved visibility of published content in global repositories.

This integration helps your journal transition from simply open access to openly connected — fully interoperable within the international research ecosystem.

Final Thoughts

The COAR Resource Type Classification System is not just a metadata list — it’s a foundation for international visibility, data interoperability, and research transparency.

For journals powered by OJS, adopting this classification through the OpenAIRE plugin means more than compliance; it means joining a global network of discoverable, machine-readable academic content.

The post COAR Resource Types in OJS: Ensuring OpenAIRE Compliance first appeared on OPEN JOURNAL SYSTEM SERVICES.

At OJS Services, we provide installation, upgrade, hosting, and technical support for Open Journal Systems (OJS) across many countries.
Working with hundreds of journals hosted on different servers — Bluehost, GoDaddy, HostGator, Hetzner, IZAhost, and others — allows us to observe version-specific behaviors very closely.

Recently, after many OJS journals upgraded to OJS 3.4, one issue became increasingly common:

Emails appear to be sent successfully, but never reach the recipient.

The Root Cause

With OJS 3.4, PKP introduced a major change to the email system.
The old PHPMailer library was replaced by Symfony Mailer — a modern, secure framework that enforces strict SSL/TLS and authentication rules.

Unfortunately, most shared hosting providers (especially Bluehost, GoDaddy, HostGator) apply strict limits on outgoing SMTP connections from PHP applications.
As a result:

• SMTP authentication succeeds,
• OJS reports “Message sent successfully,”
• but the email quietly disappears in the Exim mail queue.

Meanwhile, when sending through webmail (Roundcube), everything works perfectly — because webmail doesn’t use SMTP.
It uses the local sendmail transport instead.

The Reliable Fix: Use Sendmail Instead of SMTP

The simplest and most reliable fix is to switch OJS from SMTP to sendmail.
This makes OJS send mail directly through the local mail transport agent (Exim/Postfix), bypassing all TLS and firewall restrictions.

Open your config.inc.php file and edit the [email] section like this:

[email]
default = sendmail
sendmail_path = "/usr/sbin/sendmail -t -i"

; SMTP settings can stay for reference but will not be used
smtp = On
smtp_server = box1234.bluehost.com
smtp_port = 587
smtp_auth = tls
smtp_username = editor@yourjournal.org
smtp_password = yourPassword

After saving these settings, OJS will start delivering emails instantly — using the same internal channel that webmail already relies on.

Why This Difference Occurs

In OJS 3.3 and earlier versions, both SMTP and sendmail behaved similarly because PHPMailer handled both transports loosely.
But starting with OJS 3.4, Symfony Mailer enforces strict certificate validation and secure transport layers.

On shared servers, these extra security layers often conflict with provider-side restrictions.
The result: the connection appears successful, but the message is dropped.

sendmail, on the other hand, talks directly to /usr/sbin/sendmail on the same server.
It stays local, avoiding SSL negotiation entirely — which makes it both faster and more compatible with cPanel-based servers.

Field-Tested Experience

We first confirmed this issue with several clients hosted on Bluehost and GoDaddy.
Even with valid SPF, DKIM, and correct SMTP credentials, emails were not reaching inboxes.
After switching to sendmail, all notifications — user registration, password reset, submission acknowledgment — started working immediately.

We later verified the same behavior on HostGator, GoDaddy and Namecheap servers.
In OJS 3.4, sendmail is consistently more reliable than SMTP on shared environments.

Technical Note

This isn’t a new feature — it’s the default configuration that OJS has always recommended.
In the template file config.TEMPLATE.inc.php, the line default = sendmail has been there for years.
However, many users switched to SMTP because it “sounded more professional.”

After the 3.4 update, our tests confirm that on shared hosting, sendmail is the safer choice.

Final Recommendation

If you’re using OJS 3.4 and your emails appear to send but never arrive:

• Even if SPF, DKIM, and PTR records are correct,
• Even if your test email shows “Sent successfully,”
  👉 Switch to sendmail first.
  In most cases, that alone solves the issue.

Lessons From Experience

At OJS Services, we provide direct technical support to many academic journals every week.
Our observation is simple: most OJS email problems aren’t caused by the software itself, but by how different hosting providers handle outgoing mail.
Our job is to find the balance between both worlds — reliability and compatibility.

That’s why we now apply this rule for all new OJS 3.4 and 3.5 installations:

“Use sendmail for shared hosting. Use SMTP for dedicated servers.”

It’s simple, stable, and future-proof.

The post Fixing OJS 3.4 Email Sending Issues on Shared Hosting (Bluehost, GoDaddy, HostGator, etc.) first appeared on OPEN JOURNAL SYSTEM SERVICES.

DNB Export Plugin: Strengthening OJS Integration with National Libraries

Open Journal Systems (OJS) has become the world’s most popular platform for managing and publishing academic journals. One of the key reasons behind its success is the rich ecosystem of plugins and integrations that connect journals with indexing services, archiving systems, and research infrastructures worldwide. One such plugin that deserves spotlight is the DNB Export Plugin, maintained by the OJS community (GitHub – ojsde/dnb).

This plugin allows journals to seamlessly deposit their metadata and publications into the Deutsche Nationalbibliothek (DNB) – the German National Library. With this connection, OJS journals benefit from:

• Increased visibility through national library catalogs

• Reliable archiving of scholarly content for the long term

• Stronger compliance with international publishing standards

The DNB integration is a great example of how OJS goes beyond being a journal management tool. It is part of a global network, linking research with repositories, libraries, and indexing platforms. For editors and institutions, this means less manual work, greater discoverability, and a trusted place in the international scholarly landscape.

At OJS-Services, we support journals in making the most of these integrations – from setup to ongoing workflows – so that your research reaches the widest possible audience.

The post DNB Export Plugin first appeared on OPEN JOURNAL SYSTEM SERVICES.

Introduction: Why Journal Metrics Matter

In today’s publishing world, journals compete not only on the quality of the papers they publish but also on how clearly they communicate their credibility, efficiency, and visibility. Readers, authors, and reviewers are increasingly selective. They want to know: How fast does this journal process submissions? What’s the acceptance rate? Is it indexed in trusted databases? How widely is it read and cited?

That’s where journal metrics come in.
Metrics are not just numbers. They are signposts of trust, evidence of performance, and indicators of future growth. When displayed correctly, journal metrics help authors decide where to submit, reviewers where to invest their time, and institutions which journals to recognize and support.

For journal managers, however, a recurring question is: Which metrics should we present? Where should they appear? In this guide, we’ll break down the most important journal metrics, explain why they matter, and offer practical suggestions on how to showcase them—both on the homepage and in a dedicated “Journal Metrics” or “Statistics” section.

This image shows the metrics section from a custom OJS theme we developed, designed to display key journal statistics in a clear and user-friendly format.

1. Publishing Speed & Process Metrics

One of the first things authors look at is how long it takes to publish in your journal. Nobody wants to wait years for their work to appear. Process-related metrics signal efficiency, transparency, and professionalism.

Key examples include:

• Days to First Decision: Example – 14 days. Shows how quickly editors respond initially.
• Submission to Acceptance: Example – 120 days. Communicates the overall timeline authors can expect.
• Acceptance to Publication: Example – 15 days. Highlights production speed once a paper is accepted.
• Average Review Time: Example – 35 days. Transparency about peer review efficiency.
• Time to First Review Assignment: Example – 20 days. Shows how quickly reviewers are engaged.
• Total Publication Time: Example – 135 days. Summarizes the journey from submission to publication.

Why it matters: Shorter times can make your journal more attractive. Publishing speed also signals strong editorial workflows and reviewer management.

“Instead of reading the full text, you can also watch our video on this topic here:

2. Acceptance & Publishing Statistics

Numbers also tell the story of selectivity and productivity. These statistics highlight both your journal’s scale and its editorial standards.

Examples:

• Annual Submissions Received: Example – 500 per year.
• Submissions Accepted: Example – 150.
• Acceptance Rate: Example – 30%. Indicates competitiveness.
• Rejection Rate: Example – 70%. Often paired with acceptance.
• Articles Published per Year: Example – 120. Shows consistency.
• Number of Issues per Year: Example – 6 issues annually.
• Special Issues Ratio: Example – 20%. Shows flexibility in publishing thematic collections.

Why it matters: These numbers help authors gauge how competitive your journal is, and help readers understand output volume. High-quality journals balance a healthy submission flow with thoughtful acceptance.

3. Impact & Citation Metrics

Perhaps the most widely recognized, impact and citation metrics demonstrate scholarly influence.

Common examples:

• Impact Factor (Clarivate): Example – 3.3.
• 5-Year Impact Factor: Example – 4.2.
• CiteScore (Scopus): Example – 2.9.
• Scimago Journal Rank (SJR): Example – 0.65.
• Source Normalized Impact per Paper (SNIP): Example – 1.2.
• H-Index: Example – 45.
• Average Citations per Article: Example – 3.1.

Why it matters: These are the metrics universities, funders, and researchers often consider first. They highlight not just the quality of articles, but the journal’s reputation in its field.

4. Access & Indexing Information

Beyond citations, a journal’s access model and indexing profile are key to visibility and compliance.

Important items:

• Access Type: Open Access vs. Subscription. Example – Open Access.
• License Type: Creative Commons options (e.g., CC BY 4.0).
• Article Processing Charge (APC): Example – 1000 USD, or “No APCs”.
• Indexing Databases: DOAJ, Web of Science, Scopus, PubMed, TR Dizin, EBSCO, Ulakbim.
• Plagiarism Check Tools: iThenticate, Turnitin.

Why it matters: Indexing increases discoverability. Access policies affect author trust. Displaying them openly communicates transparency and alignment with international publishing standards.

5. Author & Reviewer Diversity

Academic publishing is global, and diversity metrics reflect inclusivity.

Examples:

• International Authorship: Example – 60%.
• Number of Contributing Countries: Example – 40+.
• Reviewer Pool Size: Example – *800+.
• Reviewers per Paper: Example – 2.5 on average.
• Editorial Board Countries: Example – 25 different nations.
• Gender Diversity Stats: Example – 45% women authors.

Why it matters: These metrics demonstrate a journal’s reach and inclusivity. Many indexers (such as DOAJ and Scopus) consider international diversity a key criterion.

6. Reader Engagement & Visibility

Finally, journals should not ignore reader-facing metrics, which show impact beyond academia.

Examples:

• Annual Downloads: Example – 150,000+.
• Downloads per Article: Example – 1,200.
• Monthly Unique Visitors: Example – 20,000.
• Altmetric Attention Score: Example – 8.5 average.
• Social Media Mentions: Example – 1,500 total.
• Mendeley Readers: Example – 5,000 total / 40 per article.
• Registered Users or Subscribers: Example – 3,500 members.

Why it matters: These statistics highlight your journal’s visibility, both academically and publicly. They can reassure authors that their work will be widely read and shared.

7. Beyond Numbers: Integrations and Tools

Metrics are powerful, but so are the technical integrations that support visibility and trust. If your journal runs on Open Journal Systems (OJS), you can leverage built-in integrations:

• ORCID: Enables authors and reviewers to link their publications to a verified researcher ID.
• Crossref: Ensures DOIs are assigned, making articles permanent and citable.
• Google Scholar: Increases discoverability.
• iThenticate/Turnitin: Shows commitment to plagiarism-free publishing.
• PlumX Metrics: Offers alternative metrics beyond citations.
• OAI-PMH Protocol: Ensures interoperability with repositories and databases.
• RSS Feeds: Keeps readers updated.
• Sitemaps: Improves SEO and indexing by Google.

Why it matters: These integrations make your journal stand out, signaling professionalism and technical maturity.

8. How to Present Journal Metrics

Now that we know what to show, the question is: where to show them?

• Homepage: Display headline numbers (e.g., Impact Factor, Acceptance Rate, Days to First Decision). Keep it simple and eye-catching.
• Dedicated “Journal Metrics” Page: Present detailed breakdowns—publishing speed, acceptance statistics, diversity, engagement.
• Indexing Information: On homepage, show 2–3 key indexes (e.g., DOAJ, Scopus). For the full list, link to a dedicated “Indexing & Databases” page.
• Always Include “Last Updated” Date: Transparency builds trust. For example: Metrics last updated: March 2025.

9. Why More (Accurate) Metrics = More Visibility

The more accurate and transparent your metrics, the stronger your journal’s profile becomes. Metrics help you:

• Build trust with authors and reviewers.
• Improve discoverability with readers and databases.
• Increase credibility in evaluations and rankings.
• Enhance scalability for future growth.
• Strengthen your competitive edge in attracting quality submissions.

Put simply: A journal without visible metrics is like a shop without a signboard. People may walk past, but few will come in.

10. Guidance for Journal Managers

Not all journals are at the same stage.

• New journals: Focus on process metrics (speed, acceptance rates), access policy, and integrations (DOIs, ORCID, iThenticate).
• Established journals: Add citation-based metrics (Impact Factor, CiteScore), diversity stats, and reader engagement data.
• All journals: Keep metrics updated and clear. Outdated or missing data damages credibility.

At the end of the day, the right mix of metrics depends on your journal’s maturity, scope, and audience.

11. Extended Checklist of Journal Metrics

Since every journal is unique, here is a broad list of possible metrics. Journals can select the ones most relevant to their scope and maturity:

• Publishing Speed & Process: Days to first decision, review time, acceptance to publication, total publication time.
• Acceptance & Publishing Statistics: Submissions received, accepted, acceptance/rejection rate, articles published, number of issues, special issues.
• Impact & Citations: Impact Factor, CiteScore, SJR, SNIP, H-Index, citations per article.
• Access & Indexing: Access type, license, APCs, indexing databases, plagiarism tools.
• Diversity: International authorship, contributing countries, reviewer pool size, gender diversity.
• Engagement: Downloads, unique visitors, Altmetrics, social media mentions, Mendeley readers.
• Technical Integrations: ORCID, Crossref, Google Scholar, iThenticate, PlumX, OAI-PMH, RSS, sitemap.

Note: These metrics vary between journals. Newer journals may not yet have citation metrics, while established ones can showcase both quantitative and qualitative indicators. Pick what’s relevant, but keep expanding as your journal grows.

Conclusion

Journal metrics are more than just numbers—they are a communication tool. They tell authors that your journal is efficient, respected, and trustworthy. They reassure reviewers that their time is valued. They show readers that published research is widely read and cited.

By strategically presenting metrics on your website—highlighting a few on the homepage, and listing a comprehensive set on a dedicated page—you can strengthen your journal’s visibility, impact, and reputation.

At OJS Services, we help journals achieve exactly that. From new journal setup to OJS upgrades, from plugin integrations to custom theme development, we provide the technical and strategic support you need to present your journal at its very best.

The post Journal Metrics: Why They Matter and How to Present Them in Your Journal Website first appeared on OPEN JOURNAL SYSTEM SERVICES.

Open Journal Systems (OJS) is a powerful, flexible, open-source journal management platform trusted by tens of thousands of academic journals worldwide. By digitizing the entire scholarly publishing workflow, OJS makes life easier for both publishers and researchers.

But like any system exposed to the internet, OJS can also be vulnerable to cyber threats if not configured and maintained properly. The majority of security breaches don’t stem from OJS itself, but rather from poor server setups, outdated software, weak user practices, or simply a lack of security awareness. Remember: even the strongest fortress can fall if its doors are opened from the inside.

In this guide, we’ll cover practical steps that everyone—server administrators, site managers, and journal editors—should take to ensure their OJS-based journal remains safe and secure.

1. The Foundation of Security: Server-Level Safeguards

Security begins with the server itself—the home of your journal. A solid, well-configured hosting environment is the first and most important step.

a. Choose OJS-Optimized Hosting

Generic shared hosting plans rarely provide the security and performance settings OJS requires. Because of OJS’s specific file structure, database access needs, and workload demands, you should use an OJS-optimized hosting environment. Providers such as ojs-services.com specialize in tuning servers for these exact requirements.

b. Set File Permissions Correctly

Misconfigured file and folder permissions are one of the most common security risks.

• config.inc.php – This file contains your database credentials and other critical settings. It should never be accessible from the web and must have permissions set to 600 or 400.
• public folder – This is the only directory that should be publicly accessible (for logos, CSS, etc.). Other OJS system files must not be writable by everyone.
• cache, public, files_dir – These must be writable by the web server but locked down so that arbitrary code cannot be executed from them.

c. Move “files_dir” Outside the Web Root

Your files_dir stores sensitive article files and submission documents. If this folder is inside public_html or www, a server misconfiguration could expose private files to the public. Update your config.inc.php so that files_dir points to a location outside the web root.

d. Harden the PHP Environment

Disable risky PHP functions (exec, shell_exec, passthru) using disable_functions. Configure session handling securely (session.cookie_httponly = On) to prevent session hijacking.

e. Enforce HTTPS/SSL

SSL is not optional—it’s mandatory. An SSL certificate encrypts traffic between users and your journal, protecting passwords, submissions, and author data. Enable it fully by setting force_ssl and force_login_ssl to On in config.inc.php.

f. Back Up Regularly

Even the best security can’t guarantee you’ll never face an attack. Daily or weekly backups of both files and the database are essential. Always store them in a secure, separate location.

2. The Site Manager’s Role: OJS Settings and Maintenance

Once the server is secure, attention shifts to how OJS itself is managed.

a. Keep OJS Updated—With the Right Version

The PKP team continuously releases updates to fix bugs and patch security vulnerabilities.

• Prefer stable, tested releases. Use long-term support (LTS) or stable versions (e.g., 3.3.0-14, 3.4.0-5) rather than early .0 releases.
• Avoid betas or development versions on live journals.
• Leave updates to professionals. Updating OJS is not just copying files; it involves database migrations. A mistake can break your entire site. Consider expert support from providers like ojs-services.com.

b. Enforce Strong User and Password Policies

• Set minimum password length and complexity requirements (uppercase, lowercase, numbers, symbols).
• Assign roles carefully: give users only the permissions they need. Avoid giving unnecessary Site Admin or Journal Manager access.
• Delete old, unused accounts.
• Enable reCAPTCHA on registration forms to block spam accounts.

c. Manage Plugins Wisely

• Install plugins only from the official PKP Plugin Gallery or trusted developers.
• Remove unused plugins.
• Always check that plugins are updated and compatible with your OJS version.

3. Editors and Journal Staff: Everyday Security Awareness

Even with strong technical safeguards, human error remains the weakest link. Editors, section editors, and reviewers all play a role in preventing security issues.

a. Watch for Suspicious Submissions

Attackers may try to upload malicious files disguised as manuscripts.

• Only open standard formats (.docx, .pdf, .tex). Be suspicious of unusual file types like .exe, .php, .js, or unverified .zip archives.
• If a submission’s title, abstract, or content looks nonsensical or irrelevant, it could be spam.

b. Stay Alert to Spam Users and Comments

Malicious users may register accounts to post irrelevant links or scams. If you notice suspicious profiles or activities, report them immediately to the site manager.

c. Don’t Fall for Phishing

Be cautious of emails claiming to be from “OJS Support” asking you to reset your password or verify suspicious activity. PKP and OJS service providers will never ask for your password via email. Always access your journal by typing its URL directly into your browser.

d. What to Do if You Suspect a Threat

• Do not download suspicious files or click suspicious links.
• Take a screenshot and report it to your Journal Manager.
• The manager should escalate the issue to technical support (e.g., ojs-services.com) or the hosting provider.

Conclusion: Security is a Team Effort

When properly configured and maintained, OJS is a highly secure publishing system. But journal security is not the job of just one person—it requires shared responsibility:

• Server administrators must provide a strong, OJS-ready infrastructure.
• Site managers must keep the platform updated, correctly configured, and monitored.
• Editors and staff must remain alert to suspicious activity.

If you don’t have the technical expertise or time to manage all this, don’t worry. At ojs-services.com, we provide OJS hosting, installation, upgrades, maintenance, and security consulting. With our professional support, your journal site is in safe hands.

👉 Don’t leave your journal’s security to chance—contact us today and let us help protect your publication.

We also offer OJS Secure Scan, a fast, automated checkup that finds vulnerabilities and provides actionable fixes.

The post OJS Security Guide: Essential Practices to Protect Your Journal Site first appeared on OPEN JOURNAL SYSTEM SERVICES.

The latest iThenticate Plagiarism Detector Plugin (versions 1.0.7.0 and 1.0.8.0) brings powerful improvements for journals using OJS:

Key Highlights

• Control Over File Checks: Editors can choose which files to submit for plagiarism detection—no more unnecessary checks on title pages or forms.

• Automatic or Manual Submission: Enable automatic submission for all files, or switch to manual mode to select only the main manuscript.

• Integrated Reports in OJS: Similarity scores and detailed reports can be viewed directly within the OJS interface.

• EULA Compliance: Authors and editors must agree to the iThenticate End User License Agreement before checks are performed, with multilingual support.

• iThenticate 2.0 Support: The plugin now requires API credentials. Journals must upgrade from username/password to API key authentication.

As shown in the screenshot, journal managers and site administrators can configure advanced similarity check settings directly within the iThenticate plugin. Options include excluding quotes, bibliographies, citations, abstracts, or methods from the analysis, as well as setting thresholds for small matches. These settings give editors more control and ensure that plagiarism reports focus on the most relevant parts of a manuscript.

Download: https://github.com/pkp/plagiarism

Why It Matters

These updates streamline editorial workflows, ensure research integrity, and give journals greater flexibility in managing plagiarism checks.

Need help upgrading OJS or its plugins?
We provide full support for OJS updates, plugin configuration, and integration. Contact us today to make sure your journal runs smoothly with the latest features.

The post iThenticate Plagiarism Detector Plugin for OJS first appeared on OPEN JOURNAL SYSTEM SERVICES.

OJS Blog Plugin: Bring Editorial Voice to Your Journal

Academic journals are no longer just platforms for publishing articles. Staying relevant today means keeping readers engaged, sharing timely updates, and building a stronger editorial voice within the scholarly community. This is exactly where the OJS Blog Plugin comes in — transforming your journal into a hub of communication and interaction.

With this plugin, editors and administrators can go beyond research articles to share comments, videos, journal news, editorial notes, academic events, and publishing tips. It allows you to maintain your journal’s academic identity while offering a more dynamic, accessible, and interactive experience for your community.

The OJS Blog plugin brings a powerful and flexible blogging system to Open Journal Systems (OJS).
It enables editors and administrators to publish posts, share updates, and engage readers beyond scholarly articles.

Key Features

• Post Management: CKEditor integration, featured & inline images, draft/published/archived status, SEO-friendly slugs & metadata
• Categories: Categories, filtering with post counts, safe reassignment on delete
• Layouts & Appearance: Single or double column layouts, top/left category menus, theme-friendly CSS styling
• Multi-Language Support: English & Turkish included, fully synchronized with OJS locales
• Performance & Security: DAO-compliant, optimized queries, caching, CSRF & XSS protection, secure file uploads

👉 [Buy Now] – [DEMO]

Why Choose OJS Blog?

This plugin is ideal for journals that want to:

• Publish announcements, news, congresses, conferences, seminars, and editorial updates
• Engage readers with insightful blog posts
• Improve visibility with SEO-friendly content
• Provide a more dynamic user experience alongside research articles

License & Support

• License Type: Commercial Proprietary License
• Scope: Single Journal License, Multi-Journal License
• Support: Free technical support included
• Special Offer: Included free with OJS Hosting Advanced Pro and OJS Hosting Ultimate Pro packages

🔗 View OJS Blog Plugin – License Terms

Compatibility

Works seamlessly with OJS 3.3+ versions.

🛒 Get Started Today

Bring your editorial voice to life and keep your community engaged with the OJS Blog Plugin.

👉 [Buy Now]

📌 The OJS Blog plugin is compatible with OJS 3.3+ versions.

OJS Blog Plugin – Screenshots & Feature Preview

OJS Blog Plugin

You can choose to display the posts in a single column or two columns, and place the categories either at the top of the page or on the left side, depending on your preference.

Blog Post Example
An example blog post with indexing updates and rich text formatting.

Blog Category View
Easily organize your content by creating categories such as Journal News, Editorial Notes, or Publishing Tips. Readers can quickly filter posts by category, making it simple to find the information that matters most to them.

Blog Management Panel – Posts
The administrative panel for managing blog posts with options to add, edit, or delete entries.

Blog Management Panel – Categories
Manage categories such as Journal News, Editorial Notes, and Academic Events directly from the admin panel.

Blog Settings
Comprehensive settings panel for customizing layout, categories, language, cover images, and display options.

The post OJS Blog Plugin first appeared on OPEN JOURNAL SYSTEM SERVICES.

The post Comprehensive List of OJS Plugins first appeared on OPEN JOURNAL SYSTEM SERVICES.

Ensuring your journal content remains available and intact in the long run is just as important as publishing it in the first place. This is where digital preservation systems like LOCKSS, CLOCKSS, and the PKP Preservation Network (PKP PN) come into play. Each system provides a safeguard against data loss and ensures persistent access to scholarly work.

🔐 Why Does Archiving Matter in Academic Publishing?

• Guarantees uninterrupted access to your articles—even in case of server or hosting failure.
• Supports compliance with best practices in open-access publishing.
• Meets requirements of major indexing services like DOAJ, Scopus, and Web of Science.
• Improves trust and transparency with authors, readers, and libraries.
• Recommendation: Publish your archiving policy on the “About” page of your journal.

✅ PKP Preservation Network (PKP PN)

• Who can use it? Journals using OJS 3.1.2 or later
• Cost: ❌ Free
• Application Required? ❌ No
• How to activate: Enable from OJS dashboard:
  Settings → Distribution → Archiving → PKP Preservation Network (PN)

Once enabled, your journal content is automatically queued for secure replication in the PKP preservation network. No manual intervention is needed.

🔄 LOCKSS (Lots of Copies Keep Stuff Safe)

• Purpose: Decentralized storage across library systems
• Cost: ⚠️ Often free, but cooperation with institutions is required
• Application Required? ✅ Yes
• OJS Setting Enough? ❌ No

Simply enabling LOCKSS in OJS displays your intent—it doesn’t enroll your journal. You must also create a LOCKSS Publisher Manifest and work with libraries running LOCKSS nodes.

🌐 lockss.org
📧 lockss-support@lockss.org

🕒 CLOCKSS (Controlled LOCKSS)

• Purpose: Long-term “dark archive” preservation
• Cost: ✅ Paid (based on journal size)
• Application Required? ✅ Yes
• OJS Setting Enough? ❌ No

To use CLOCKSS, publishers must establish a formal agreement. CLOCKSS releases content to the public only if the journal becomes inactive, making it ideal for long-term assurance.

🌐 clockss.org
📧 contact@clockss.org

📌 Understanding the Archiving Settings in OJS

In OJS (3.3+), go to Settings → Distribution → Archiving and you’ll see options to enable LOCKSS, CLOCKSS, and PKP PN. These checkboxes:

• Display archiving affiliations in the “About” section of your journal
• Inform readers and indexing services of your archiving policy

Note: Checking LOCKSS or CLOCKSS does not activate actual preservation. External registration is still required.

📝 What Should You Include in Your Archiving Policy?

It’s best practice to clearly communicate your archiving systems under:

• About the Journal → Archiving

Sample policy statement:

This journal utilizes the PKP Preservation Network (PKP PN) to ensure long-term preservation of its published content. Additionally, it supports LOCKSS and CLOCKSS archiving protocols for eligible library networks.

🎯 Comparison Table

🧩 Final Takeaways

• PKP PN is the easiest and fastest preservation solution for OJS journals.
• LOCKSS and CLOCKSS require external coordination and setup.
• Transparent archiving builds trust and supports indexing applications.
• Digital preservation is an essential part of sustainable publishing practices.

The post Long-Term Content Preservation in OJS: A Guide to LOCKSS, CLOCKSS and PKP PN first appeared on OPEN JOURNAL SYSTEM SERVICES.

OJS (Open Journal Systems) is a popular open-source platform for managing academic journals—from submission through to peer review and publication. It’s robust and flexible, but like any software, it depends on server environment and configuration to function smoothly.

Sometimes your journal may suddenly stop working or show error pages. One frequent culprit is the dreaded “HTTP ERROR 500” – an “Internal Server Error.” When this happens, your users likely see a blank page or a generic message instead of your journal content.

Let’s look at why this happens and what you can do about it—no guesswork, just tested advice.

What Does “HTTP ERROR 500” Mean?

This error indicates the server encountered something unexpected it couldn’t handle. In OJS, it may occur when loading the homepage, accessing the backend, or using plugins.

Common Causes & Fixes

1. Server Environment Issues

• PHP version or missing extensions
  OJS generally requires PHP 7.x or 8.x, along with extensions like xml, gd, intl, pdo_mysql, and fileinfo. If an expected function is missing (for example, xml_parser_create()), PHP throws a 500 error.
  Fix: Check your PHP environment and install missing modules. On many Linux systems:

  sudo apt install php-xml php-gd php-intl
  

  Then restart PHP and your webserver.

• File permissions
  OJS needs to read and write to certain files—particularly config.inc.php, cache folders, and your files_dir. If these aren’t writable, errors occur. The core config.inc.php file must exist—it lives at your OJS installation root, not in a “config” folder. Permissions like 644 for files and 755 for directories are usually enough. Certain directories (cache, files dir) may require 775 or 777.
• Error logs
  You won’t fix what you can’t see. Check your PHP-FPM logs (like /var/log/php‑fpm/www-error.log) or Apache/Nginx logs. They often contain hints like “permission denied” or “undefined function” messages.

2. OJS Configuration & Caching

• config.inc.php settings
  All key options—database credentials, files_dir path, and security settings—live here. Errors in this file are a major source of HTTP 500s. The file must be present, correct, and readable by the webserver.Check:

  ; [files]
  files_dir = /full/path/to/ojsdata
  

  And verify this directory exists and is writable.

• Plugin conflicts
  A recently installed or updated plugin may break OJS and trigger a 500. Disable the plugin via the database or temporarily rename its folder to test.
• Corrupted cache
  Old files in cache/, cache/t_cache, cache/t_config, or cache/t_compile can cause issues. Clear them manually and reload your site to let OJS rebuild fresh cache.

3. Server Limits & SSL

• Resource limits
  Tasks like upgrading OJS or exporting issues may exceed time or memory limits (max_execution_time, memory_limit). Too much and the server aborts with a 500.
  Fix: Raise these limits in php.ini or .htaccess, or run heavy tasks from the command line.
• SSL or HTTPS misconfiguration
  Enabling SSL means updating server certs and also adjusting OJS’s config.inc.php (force_ssl = On). A mismatch or missing certificate can also cause a 500.

Quick Fix Checklist

1. Check logs—PHP‑FPM and web server logs for error messages.
2. Confirm PHP modules—especially XML, GD, intl, PDO.
3. Validate config.inc.php—exists, readable, correct paths (especially files_dir).
4. Fix permissions—ensure OJS folders & files are writable by the PHP user.
5. Clear cache—empty all cache directories.
6. Disable suspect plugins.
7. Increase resource limits—for heavy operations.
8. Check SSL settings—ensure SSL is set up cleanly.

Still Stuck?

If you’ve tried all of the above and the site still shows a 500 error, we’re here to help. Reach out to us via our contact page and let our team help get your journal back online.

The post Troubleshooting “HTTP ERROR 500” in OJS (Open Journal Systems) first appeared on OPEN JOURNAL SYSTEM SERVICES.

📌 What Is ROR?

The Research Organization Registry (ROR) is a global, open, and community-led initiative that provides unique persistent identifiers for research organizations — much like ORCID for researchers or DOI for articles.

Each institution is assigned a unique ROR ID. This allows scholarly systems to store, recognize, and retrieve affiliation data consistently, regardless of spelling variations or language differences.

ROR records include:

• The official name and alternative names in different languages

• Location and website of the institution

• Cross-linked identifiers like ISNI, GRID, Crossref, and Wikidata

• Relationships with other organizations (e.g., hospitals, research centers)

🎯 Why Is ROR Important?

In most publishing systems, authors manually type their institution names during manuscript submission. While this seems simple, it often leads to inconsistencies due to:

• Typing errors

• Local language differences

• Personal or unofficial naming conventions

These inconsistencies can:

• Break metadata quality

• Mislead statistical analysis

• Disrupt institutional reporting

• Hinder indexing and discovery

By using ROR, systems ensure that all affiliations point to a single, accurate, and standard identity — improving interoperability, searchability, and reporting accuracy.

🏛 Let’s See This in Action: Gazi University’s ROR Record

To understand how ROR helps solve these problems, let’s explore a real example — Gazi University in Turkey.

🔗 https://ror.org/054xkpr46

On this ROR profile, you’ll find:

• Official name: Gazi University

• Other names: Gazi Üniversitesi (tr), Qazi Universiteti (az)

• Location: Ankara, Türkiye

• Website: http://gazi.edu.tr

• Linked identifiers:

  • GRID: grid.25769.3f

  • ISNI: 0000 0001 2169 7132

  • Crossref Funder ID, Wikidata

• Related organizations: Gazi Hastanesi

In a manual system, authors might enter any version of this name — from “Gazi University” to “Gazi Üniv.” to “Qazi Univ.” — all of which the system might treat as separate institutions.
But with ROR, all these variations are unified under one consistent institutional identity.

🔌 How Does This Work in OJS?

The ROR Plugin is available in the OJS Plugin Gallery starting with version 3.2. Once installed and enabled:

• Authors are prompted to select their institution from the ROR-powered list during submission.

• The system fetches standardized metadata from ROR, ensuring consistency.

• Multiple affiliations can be added if needed.

• The selected ROR ID is stored in the metadata and displayed on the article page.

This is especially helpful for multilingual journals, where the same institution may be entered in English, Turkish, Spanish, or other languages.

💡 Key Benefits of Using ROR in OJS

✅ Prevents human errors in affiliation names
✅ Unifies institution data across languages
✅ Supports multiple affiliations for one author
✅ Improves indexing and interoperability
✅ Helps generate accurate institutional reports
✅ Enhances metadata quality for repositories and funders

🛠 Ready to Future-Proof Your Journal?

At OJS-Services.com, we specialize in helping journals implement powerful tools like the ROR Plugin. Whether you’re just starting out or managing a large publishing platform, we can support you with:

• ✔ OJS installation and setup

• ✔ Plugin integration (ROR, ORCID, Crossref, more)

• ✔ System updates and theme customization

• ✔ Hosting and long-term support

📧 Get in touch with us today to bring your journal up to international standards — clean, consistent, and ready for the future of scholarly publishing.

The post Why ROR IDs Matter? first appeared on OPEN JOURNAL SYSTEM SERVICES.