Journal Publishing Guide

Each piece of information is called a Block. We use a plugin for this, called Custom Blocks Manager. To update the text go to Website → Plugins tab.

Find Custom Block Manager about halfway down the page, and click on the left-hand triangle to show you the option Manage Custom Blocks. If you select the block you want to edit, click Edit, you will get a pop-up box with the text in question.

There are 2 main ways to contact all users registered for your journal: make an Announcement or send a Bulk Email (new feature).

Announcement

Announcements may be turned on or off under Website → Setup → Announcements → Checkbox toggle: Enable announcements. Once turned on, an Announcements button will appear on your Dashboard.

Depending on your journal settings, announcements may also appear on your journal homepage or dedicated Announcements page.

You have the option to send announcements to every registered user (unless they've opted out) by going to Announcements → Add Announcement → fill in details → Checkbox Send an email about this to all registered users.

Announcements are appropriate for content such as Call for Papers, recruitment for Reviewers, and other informational content.

Bulk Emails

This is a new optional feature. When this feature is enabled, a journal manager will be able to send an email to all users registered with their journal (and bypass anyone who has opted out of notifications). Misuse of this feature to send unsolicited email may violate anti-spam laws in some jurisdictions and may result in your server's emails being blocked as spam.

Before requesting this feature, we encourage you to familiarize yourself with Canada's Anti-Spam Legislation.

Please consult with us if you want to add this feature, by contacting library.publishing@ualberta.ca.

A few things may be causing this issue:

Scenario 1: Wrong username / email address

Make sure that the user's email address (the one attached to their current account) is the correct one, and correctly spelled. OJS does not verify email addresses, and typos happen! Users also often inadvertently create multiple accounts under different usernames.

Scenario 2: Notification settings

Secondly, if the email is a notification, make sure that the user's notifications are set correctly. Users can opted out of receiving OJS notifications (including email notifications) for Discussion-related activities. The user may have done this a while ago, and forgotten. Since this setting is controlled at the individual user-level, we recommend asking the user to make these changes. While editors can technically "log in as" users to make changes, we recommend against this, as most users are unaware of this and some may be alarmed when actions are taken without their knowledge/permission.

That said, you can log in as the user to check their Notification Settings: Users & Roles → Users → Search → Log in As → Hover over username (top right corner) → View Profile → Notifications → Checkbox for each notification.

Scenario 3: Spam filter

Check the spam filter: OJS emails are packaged in a way that even though emails are sent out by University of Alberta servers, the Sender is listed as your own email address (or the journal's main contact). A small number of institutional email servers may flag this as suspicious.

That said, every institutional email server is configured differently, so ask the user to check their Spam folder. Ask the user to mark the legitimate email as "not Spam" or adding your journal's email addresses as "Safe" can help future cases.

DOIs are intended to be permanent, unique identifiers that stay with a piece of content (such as an article) for its entire history.  DOIs are designed to be machine-readable, and do not need to be human-readable.

How are DOIs created?

DOI creation involves two steps:

1. Assigning a DOI: This is when you create a new DOI for a unique work, but the DOI is not active yet.  New DOIs should unique, and usually follows a pre-set formula.  Within OJS, DOIs are generated under Submission # > Publication > Identifier
2. Registering a DOI: This is the process of sending information about the DOI to a registration agency (we use CrossRef). After it's registered, a DOI will be active. This is set to happen automatically within 48 hours of publication

What should I do, if I want to include DOIs in my full-text galley file?

It's highly recommended that you add DOIs to your article files, in full-text galleys.  However, it's critical that you avoid typos.  Here are some best practices:

DO:

• DO always copy & paste the DOI from OJS's Publication > Identifier field
• DO add a URL prefix to help readers navigate more easily.  The preferred URL prefix is https://doi.org/
• DO always check and verify that your DOIs are working, after 48 hours past publication

DO NOT:

• DO NOT attempt to enter DOIs manually, or predict them. Human errors happen, and typos are likely to cause future problems
• DO NOT add any punctuation after the DOI, which will be interpreted as a part of the DOI itself (e.g. unnecessary periods at the end cause the most frequent DOI errors)
• DO NOT add any extra punctuation or spaces, when hyperlinking
• DO NOT use the legacy URL prefix https://dx.doi.org/  (use https://doi.org/ instead)

It's been 48 hours, and my DOI still doesn't work, what do I do?

Firstly, make sure that there is a DOI in the Publication > Identifier field.

Please email us at library.publishing@ualberta.ca, with the article's URL.

About the plugin

The newest version of the ORCID plugin allows for the configuration of 2-way communication between OJS and ORCID. Not only will an author’s ORCID appear in their article’s information, but upon publication, the article citation data will also automatically appear in the author’s ORCID profile (if they give permission). In order to prevent fraudulent use of a researcher’s identity, OJS’s ORCID plugin requires “authorization” from the researcher for every Submission, even if they’ve already linked their ORCID to their OJS user profile.

How to turn on plugin

Please contact library.publishing@ualberta.ca, so we can enter and verify the configurations. We use our University of Alberta Library credentials to send information securely to ORCID.

How the plugin works

Editors can verify whether an ORCID is authorized by the iD-holder, by going into each submission’s contributor metadata, to check: Submission → Publication → Contributors → Edit. 

If the ORCID is authorized, it will have an expiry date.

If the ORCID is not entered (or authorized), the message will say "ORCID not authenticated! Please request authentication from the contributor."

How to request authentication

There are a few ways in which an author might receive an invitation to authorize their ORCID:

1. At the time of Submission, a Submitter can choose to send an invitation to their co-authors or themselves, while they input contributor information.

2. An editor can send the invitation any time pre-publication. They can do so by editing the Contributor metadata on the Submission (as described above)

3. For all authors who have not yet authorized their ORCID, they may get an automatic email invitation upon the publication of their article. (This auto-invitation is optional; you can turn off the automated option and do it manually instead).

Because of these multiple ways, it is possible to generate multiple competing links. The latest link usually overwrites the older ones, so authors should avoid using any outdated email links!

Deleting an ORCID

If there is an error, the editor can remove the token and try again using the checkbox "Delete ORCID iD and access token!" and Save. The ORCID will disappear from the submission metadata.

Recently, the Delete button was hidden, because it was deemed too prominent for this irreversible task, which makes it too easy to make a mistake (with no undo option). It was also too easy to conflate the permanent "delete" with "decline," which archives a submission but retains it in the system.

That said, we understand that some submissions should be deleted because they're spam, duplicates, or tests.

In this case, Editors have to first Decline a submission (it's possible to Decline without notifying the author) and then a delete option will be available from the dashboard. If a submission is incomplete, you will have to complete all of the mandatory fields, decline it before you can delete it. 

Once Deleted, a submission will no longer be counted in the editorial statics.

For more detailed instructions go to: PKP's Learning OJS Guide
For help, contact library.publishing@ualberta.ca