The following items represent notable improvements made to the platform and tools in this release, as well as key defect fixes and optimizations. The text below also provides information about default configuration values and instructions for configuring each feature. Please note that some features must be activated by an administrator or ScholarOne representative for your users to benefit from the new functionality; contact your publisher team or ScholarOne for questions around permission or configurations.
English | Chinese | French | Japanese | Portuguese | Spanish
Updated Client Configuration Center to include Plagiarism Checking page which will allow users with client configuration center access to adjust iThenticate V2 settings. Previously, admins could only make configuration adjustments from the admin dashboard if the integration was initially set up with admin access. Moving this into the Client Configuration Center will allow more flexibility for power users to update report generation settings without contacting Support.
Users:
|
|
Action required.
iThenticate V2 integration must first be enabled and credentials provided; reach out to ScholarOne support to assist with upgrading from V1 to V2, or enabling V2 on a new site. |
Details & Configuration
NOTE: Do not make changes to the Turnitin URL or API key fields; this will disconnect your site’s integration and Similarity Reports will no longer be generated.
Added a configuration option to auto-save changes in the Similarity Report pop-up window. If this option is checked, all changes made to a given report will save when the window is closed and restore when/if the report is re-opened. All user changes will be saved; the last set of changes made to a report will be the ones to restore when the report is re-opened by any user. Changes to a given report may include adjustments to exclusion filters or search repositories.
Users:
|
![]() |
|
![]() |
Action required.
Configuration will be ON by default for sites with an active iThenticate V2 integration during the release. Configuration will be OFF by default for sites enabling V2 in the future. |
Details & Configuration
Upgraded the search engine technology that ScholarOne Manuscripts uses (called “Elasticsearch”) to a new version. Elasticsearch powers several different searches in S1M, including Research Interest, Keywords, and Duplicate Submission Checker.
Benefits of this upgrade:
Users:
|
![]() |
|
![]() |
|
![]() |
Action required.
Available by default following a transition plan. No configuration required. |
Details & Configuration
Areas that will be improved by the upgrade:
Added pagination to the reviewer list to only display 10 records at a time.
Previously, if a manuscript had large numbers of reviewers, it would be susceptible to repeated gateway timeout errors, preventing editors/admins from accessing the manuscript. Adding this pagination will eliminate the gateway timeout error for this issue and make large lists more manageable.
Users:
|
![]() |
|
![]() |
Action required.
Available by default. No configuration required |
Details & Configuration
If a reviewer list has more than 10 reviewers selected/invited/responded to a manuscript, Editors/Admins will now page through the list instead of seeing all records on one page:
Added auto-refresh functionality for custom questions that are configured with dependencies attached to their responses.
Users:
|
![]() |
|
|
|
![]() |
|
![]() |
Action required.
Available by default. No configuration required. |
Details & Configuration
Custom questions can be configured with dependencies; i.e. if a user selects a certain response to a custom question, the system can then display another question specific to that response (based on the configuration).
Previously, this dependent question would only be displayed after a manual page refresh or on a new page. With the new auto-refresh functionality, upon selection of the response associated with a dependency, the page will refresh immediately and display the dependent question for the user to answer.
Updated “req” display for decision custom questions so that “req” symbol appears next to the question only (no longer appears alongside all response options).
Users:
|
![]() |
|
![]() |
Action required.
Available by default. No configuration required. |
Details & Configuration
If there is more than one answer configured for a checkbox question at the decision task, the “req” symbol or red asterisk will only display next to the question, and not after all answer options.
Added data for task-based custom questions to the getSubmissionFull V6 API.
Users:
|
![]() |
Action required.
To leverage use of this API, you must be a ScholarOne Web Services client and will need to upgrade to V6. If you want to learn more about using this API, reach out to your Account Director. |
Details & Configuration
Sample output:
Added a new System Event notification when a task on a manuscript has been rescinded (only valid for Reviewer Score, Recommendation, and Decision tasks).
Users:
|
![]() |
|
![]() |
Action required.
Visible to all existing Web Service Clients. If you are not a Web Service Client and want to learn more, please contact your Account Director. |
Details & Configuration
From the Integration Dashboard, navigate to Notification Services Subscriptions. Example configuration below:
Added a new System Event notification when an author responds to an invitation to submit
Users:
|
![]() |
|
![]() |
Action required.
Visible to all existing Web Service Clients. If you are not a Web Service Client and want to learn more, please contact your Account Director. |
Details & Configuration
From the Integration Dashboard, navigate to Notification Services Subscriptions. Example configuration below:
For sites with a Submission Integration setup: added the ability to provide external email correspondences to the audit trail in S1M via the external integrated platform.
Users:
|
![]() |
Action required.
Available by default to all customers utilizing Submission Integration. |
Details & Configuration
Example format for XML:
* Submission Integration is a set of features in ScholarOne allowing external systems such as publisher portals and preprint servers to push manuscripts into journal sites.
For sites with a Submission Integration setup: added a padlock symbol that will display next to the manuscript ID when the paper is in a locked state. This will indicate whether the manuscript is locked for changes or is open for editing by the author.
Users:
|
![]() |
|
![]() |
Action required.
Available by default to all customers utilizing Submission Integration. |
Details & Configuration
The padlock symbol will appear next to the manuscript ID on the following pages:
* Submission Integration is a set of features in ScholarOne allowing external systems such as publisher portals and preprint servers to push manuscripts into journal sites.
Note: ScholarOne deploys a number of patches and hotfixes between releases, ensuring that our users experience constant improvements to the platform. Many of these are driven by internal teams to optimize processes and therefore do not affect workflows. If you have questions about any of these changes, however, please reach out to Support.