ScholarOne Manuscript Q3.2020 Release Highlights Video
Our release highlights video gives an overview of some of the exciting features in this release.
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
Sign up to receive release notes, product news, and maintenance alerts below.
Our release highlights video gives an overview of some of the exciting features in this release.
The Q3.2020 release introduced added support for the Unsubmitted Workflow to ScholarOne’s Submission Integration feature set. External submissions sent back to the author (“unsubmitted”) for changes can now be updated in their draft state by the external system which originally sent in the manuscript. Previously, external systems were not able to update unsubmitted manuscripts in draft, only create a new submissions.
.
Users
Configuration required.
Unsubmit features for ScholarOne submission integration allow external systems to update the files and metadata for an unsubmitted manuscript in draft. When configured, manuscripts sent back to the author will be automatically locked in the ScholarOne UI. Neither the author nor journal admins will be able to make edits to the document.
The expected user journey has the author making changes to the manuscript in an external system which then passes the change to ScholarOne via submission integration. If changes must be made in ScholarOne, the manuscript can be unlocked for editing and then locked again from the Manuscript files tab.
Submission Integration and its functionality to support unsubmitted papers must be configured by ScholarOne.
Added pdf support for Submission Prefill. This allows journals to accept pdf submissions through Submission Prefill automatically entering Title, Keywords, Authors, Institutions and Funders for the manuscript from an uploaded file.
Users
Configuration required.
Submission Prefill is configurable under the Add-Ons section of configuration.
Set the File Designation for the Submission Group by selecting from the drop down of available File Designations.
Select the file type to allow by marking the appropriate checkbox. Submission Prefill supports pdf, doc/docx independently or both, together.
Updated the Submission Prefill algorithm matching institutions to Ringgold Ids.
Users
This feature is a part of Submission Prefill. Once Submission Prefill is active, no additional configuration is required.
This update to the matching algorithm ensures a greater number of institutions ingested via submission prefill are automatically matched to their Ringgold ID saving authors time spent in the submission process.
Created internal tools allowing for Clean Slate activation of the Unusual Activity Detector by additional staff.
Users
Configuration required.
The Unusual Activity Detector may be configured so alerts from all time appear in queues, or with a “Clean Slate”, where no alerts from previously processed manuscripts appear in alert queues. Many clients prefer the Clean Slate approach which previously required assistance from our dev teams. With this updated toolset for ScholarOne staff, Publishers can expect to see the wait time for Unusual Activity Detector activation decrease.
For more information on our industry leading Unusual Activity Detector, please contact your usual ScholarOne Manuscripts contact or our Product Support team at s1help@clarivate.com
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.
