Skip to main content

7.10 - Search criteria, system events, referee form, warnings

New criteria for advanced searches

Two newcool date criteria are now available to create dynamic searches:

image.png


New system events

Two system events are now implemented:implemented properly:

  • "Resubmission after technical check": after a technical check, the resubmission is now distinct from a normal submission! This presents several advantages when the author resubmits:
    • the corresponding author will not get the usual acknowledgement of receipt
    • likewise for co-authors
    • and editors will not receive the same e-mail
  • "Peer review complete"
    • this event trigger has been corrected and now works properly: the editor will get notifier when the last scheduled referee provides his report.

For thisthese two events, no default template has been provided,. weWe invitewill youdefinitely toprovide createthem yourshortly own. Concerningfor "Resubmission after technical check", default templates will be provided shortly..


System events: modify the Reply-To header!

In e-mail addressing, the Reply-To header is the address that should be used to reply to thea messagemessage. (different from the original sender). TypicalTypically in Nestor, this mechanism is used forin the typicalthis scenario:

  • Albert Einstein requests a revision from the system
  • The mail is sent to the author with the following headers:following:
  • the author replies to the message: Albert is the recipient (not the system), even though Albert was not the original sender

This mechanism has been extended to specific system events, with the possibility of using Reply-To --> the current editor. Specifically:

  • when the author gets an acknowledgement of receipt (replies to: current editor)
  • when the author isgets automaticallyan remindedautomatic reminder to revise (same)
  • when the referee gets an acknowledgement of invitation (same)
  • when the referee gets an acknowledgement of decline (same)
  • when the referee gets an acknowledgement of report (same)
  • when the referee isgets automaticalllyan cancelledautomatic cancellation (same)
  • when the referee isgets automaticallyan remindedautomatic reminder (same)

By default, ,none of these events have been configured to usereply to the current editor, theywe areinvite easyyou to setconfigure this if relevant to your workflow, this is defined in the template config:

image.png

Referee report form

A long awaited ergonomy update to prevent referees from forgetting to complete their report.

image.png


User warnings (availability, conflict of interest etc)

Following this update, several improvements have been made to user warnings behaviour:

  • the new warning merely links to the article list (screenshot below)
  • any editor can check the whole list, even if unassigned
    • this behaviour has also been extended to users' page
  • common warnings are not displayed when reinviting referees on a revision

image.png



Back to top