Automated Review Reminders

Are you responsible for making OCS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, michael, John

Forum rules
The Public Knowledge Project Support Forum is moving to

This forum will be maintained permanently as an archived historical resource, but all new questions should be added to the new forum. Questions will no longer be monitored on this old forum after March 30, 2015.
Posts: 17
Joined: Thu Mar 16, 2006 12:16 am

Automated Review Reminders

Postby garde » Wed May 11, 2011 6:01 am

Dear all,

is it correct that there is only one email template for automatically reminding reviewers to
    a) respond to a review REQUEST and
    b) ask them to submit their review?

In the journal policies setup it says, that
Automated email reminders can be sent to reviewers at two points:
If reviewer has not responded to a review request within X days.
If reviewer has not submitted a recommendation within Y days after review's due date.

We would like to automatically remind reviewers in both cases.
This works, but both reminders seem to use 'REVIEW_REMIND_AUTO_ONECLICK' or 'REVIEW_REMIND_AUTO' (depending on your one click settings).

However, I believe that these reminders need to be quite specific to be useful and a general one that catches both is not really sufficient.

Am I missing something or is there no way to configure different emails for these two events?

Best regards

In addition (just an idea) it may be useful to have a third type of reminder to remind reviewers a day or two BEFORE the review is due.
I am increasingly receiving emails like that (when I am a reviewer somewhere) and I think it is a really polite way of reminding reviewers that their review is due soon (i.e. before they have missed the dealine and thus give them the chance to submit in time)

Posts: 4191
Joined: Tue Feb 14, 2006 10:50 am

Re: Automated Review Reminders

Postby jmacgreg » Fri May 13, 2011 2:20 pm

Hi Garde,

Thanks for your comments! This has already been reported as a feature request (see, although it wasn't added to OJS 2.3.4 and won't be in 2.3.5.

And I think your other suggestion makes sense -- I've submitted it as a feature request as well (see Please feel free to CC yourself to either/both of those reports for future updates.


Posts: 110
Joined: Mon Apr 11, 2011 7:08 am

Re: Automated Review Reminders

Postby aleskl » Fri Oct 28, 2011 8:17 am

I would also very much like to have different email templates for both auto review reminders. The temporary solution I used is that I disabled the email sent to a reviewer that doesn't respond in 5 days.

Posts: 257
Joined: Fri Jun 01, 2007 2:56 am
Location: Aarhus, Denmark

Re: Automated Review Reminders

Postby nef » Fri Nov 08, 2013 1:55 am

It hasn't been fixed in the 2.4.2 edition neither,

Posts: 10015
Joined: Wed Aug 10, 2005 12:56 pm

Re: Automated Review Reminders

Postby asmecher » Wed May 21, 2014 2:11 pm

Hi all,

Bug #5778 has not yet been implemented, and we're currently focusing our attention on the forthcoming OJS 3.0 release. On the other hand, it's a fairly simple modification; code contributions are welcome.

Alec Smecher
Public Knowledge Project Team

Posts: 110
Joined: Mon Apr 11, 2011 7:08 am

Re: Automated Review Reminders

Postby aleskl » Thu Oct 23, 2014 2:44 am

I'm returning to this topic, because I noticed that multiple reminders are probably never sent, regardless if you select them in journal settings!

I was looking at /classes/tasks/ for code modification that would send different reminders for each event, invite reminder and review reminder. It seems that including a second email template is not a big deal, I can do that.

But the problem is setting the DateReminded. If both types of reminders are selected in the journal settings, the setDateReminded sets the date already at the first reminder event (when the reviewer forgets to respond to the invite, default is 5 days after the invite was sent), so the second reminder will not be sent, because the function executeActions() at the end of checks if getDateReminded is not null and cancels the reminder, if one was already sent before. That was indeed the behaviour, when I first enabled automated reminders - the first reminder was sent, but the second didn't get sent. When I look at the code I now understand why. So I guess the solution would be to introduce different variables for DateReminded for different events (maybe even an array, so that the automatic sending can be expanded to multiple reminders)? However, this probably means database modifications and modifications in different places in the code (article, reviewer, section editor)?

So the real issue is how to track at least two different dates for reminder sending. Introducing more variables would be quite invasive, so if anyone has a better idea, please step forward :)


Return to “OCS Technical Support”

Who is online

Users browsing this forum: Baidu [Spider] and 1 guest