Q1.2025 Release

Unusual Activity Detector Report Improvements

GLOSSARY UPDATE:

• Revised the glossary to enhance its clarity and usability for editors across various academic fields, including STEM (Science, Technology, Engineering, and Mathematics) and Social Sciences. This revision aims to ensure that terms and definitions are accessible and relevant, facilitating better understanding among a diverse audience of editors.
• Our primary objective is to foster improved comprehension and active engagement among Editors from different disciplines within Academia. By focusing on clarity, we aim to bridge gaps in understanding that may exist due to disciplinary differences.
• In addition, all training materials related to UAD (Unusual Activity Detection tool) are undergoing a thorough review and update process. This will ensure that the revised glossary and related resources are integrated seamlessly into our training programs.
• Furthermore, we will organize and conduct ad-hoc training sessions tailored to specific needs as they arise. These sessions will provide opportunities for editors to deepen their understanding of the revised training materials and engage in discussions relevant to the Unusual Activity Detection tool.

Users:

ScholarOne APIs & Relay

A newly developed API (Application Programming Interface) based on Custom Flags to automatically flag manuscripts whenever an integrity signal is received from any of our Partners launched. This proactive measure ensures that we maintain high standards of integrity and quality in our manuscript handling processes.

Call examples:

getSubmissionInfoCall:

setCustomFlags (POST):

Body:

{

“input”: {

“customFlagsList”: [

{

“documentId”: 2949065,

“customFlagName”: “Alert”,

“setFl”: 1

}

]

}

}

Flag names:

Alert

Caution

OK

Users:

SCHOLARONE RELAY

The first iteration of a newly developed API – receiving the data- will be deployed on the Q1.2025 ScholarOne. We are currently working on the second iteration, which will feature a new Integrity Report displayed on the user interface (UI). Our aim for future iterations is to achieve as much integration as possible for Integrity within the Silverchair Universe partnerships program.

Technical details: It is a generic API endpoint to handle data from different vendors. It is based on JSON files & payloads.

• Streamlined Integration: The new API significantly reduces the time required to incorporate vendors into existing workflows, enabling smoother collaboration and faster implementation.
• Versatile Applications: It is designed to be flexible and can accommodate a variety of use cases, including but not limited to ensuring research integrity.
• Collaborative Pilots: The API supports the execution of research integrity pilot testing with multiple partners, allowing customers to explore and validate their solutions effectively.
• Enhanced Features: With its capability to support in-platform plugins, the API allows quicker updates and improvements, ensuring that users benefit from the latest advancements.
• Simplified Publisher Adoption: Integrating in-workflow add-ons makes it easier for publishers to adopt new functionalities, leading to a more efficient onboarding process.

Users:

API developments

NEW VERSION OF /api/s1m/v2/submissions/full/metadatainfo/documentids API 

New version of getSubmissionInfoFullDocumentId v2 API has been developed by adding authorChoiceTransferOptions field which is a list of all Author Choice Options stated inside authorChoiceTransferOption subfield.

Configuration Settings:

Example of the API call:

URL: https://mc-beta-api.manuscriptcentral.com/api/s1m/v2/submissions/full/metadatainfo/documentids?site_name=xyz&ids=%1234567%27,%12345678%27&environment_name=s1m-1

Body:

{
“input”:  {
“documentId”: 11236789,
“noteTitle”: “Note title here”,
“noteText”: “This is the text of the document note”

}
}

Example of a response:

<authorChoiceTransferOptions>
<authorChoiceTransferOption>Test</authorChoiceTransferOption>
<authorChoiceTransferOption>Test1</authorChoiceTransferOption>
<authorChoiceTransferOption>Test 3</authorChoiceTransferOption>
<authorChoiceTransferOption>Test 4</authorChoiceTransferOption>
</authorChoiceTransferOptions>

NEW API /api/s1m/v3/submissions/full/metadatainfo/submissionids

A new API has been developed /api/s1m/v3/submissions/full/metadatainfo/submissionids

The API contains all the fields as /api/s1m/v3/submissions/full/metadatainfo/documentids

Example of the API call:

https://mc-beta-api.manuscriptcentral.com/api/s1m/v3/submissions/full/metadatainfo/submissionids?site_name=xyz&ids=%123-2024%27&environment_name=s1m-1

Example of a response:

authorChoiceTransferOptions>

<authorChoiceTransferOption>Test 1</authorChoiceTransferOption>

<authorChoiceTransferOption>Test 2</authorChoiceTransferOption>

<authorChoiceTransferOption>Test 3</authorChoiceTransferOption>

<authorChoiceTransferOption>Test 4</authorChoiceTransferOption>

</authorChoiceTransferOptions>

API call error list with error codes: 

1. ids
   • error code  bad array value: “WVLD-11670” Values {1} are invalid for parameter ids
   • error code bad csv list: “WVLD-11671” Value {1} is invalid for parameter ids
   • error code max count exceeded: “WVLD-11672” Maximum count 25 is exceeded for parameter ids
   • error code missing: “WVLD-11673” Value is required for parameter ids
2. site_name
   • error code missing: “WVLD-11674” Value is required for parameter {0}
3. locale_id
   • error code bad type: “WVLD-11675” Value ”{1}” is the wrong type for parameter {0}

NEW POST API TO ADD A NOTE TO MANUSCRIPT

A new POST API has been developed to add document notes to a manuscript.

• Note title limit is 100 bytes.
• Note text limit is 5K.

The note addition is logged in the audit history and the note ‘updated by’ column as being added via the system.  POST API will only be allowed to be added to sites which have the particular API key access.

Example of the API call:

URL: https://mc-beta-api.manuscriptcentral.com/api/s1m/v2/document/addNote?site_name=xyz

Body:

API call error list with error codes:

1. locale_id
   1.1. error code: “WVLD-11592” locale_id is the wrong type for parameter (Integer require type)
   2. documentId
   2.1. error code: “WVLD-11593” documentId is required
   2.2. error code: “WVLD-11594” documentId is too long (40 characters limit)
   2.3. error code: “WVLD-11595” documentId is the wrong type for parameter (Integer require type)
   2.4. error code: “WVLD-11596” Bad value range for documentId (allowed range 0-12,147,483,647)
   3. noteTitle
   3.1. error code: “WVLD-11597” noteTitle is required
   3.2. error code: “WVLD-11598” noteTitle is too long (100 characters limit)
   3.3. error code: “WVLD-11600” Invalid content (e.g. put <script>test</script> as noteTitle)
   4. noteText
   4.1. error code: “WVLD-11599” noteText is too long (10000 characters limit)
   4.2. error code: “WVLD-11600” Invalid content (e.g. put <script>test</script> as noteText)

EXTERNAL ID ADDED TO THE MESSAGE BODY OF THE DUE DATE UPDATED NOTIFICATION

A new element called externalSubmissionId will be present in notification payload with the expected value of an external number when the journal staff change the due date for a manuscript.

Site needs to be configured with notifications and a notification is set up for the System events > Due date updated (Authors / Co-Authors) > Due Date Updated notification.

DEFECT FIX FOR REMINDER EMAILS

Previously, e-mail reminders were not sent when an Editor was reassigned. We have now updated the system to ensure that when an Editor is reassigned, the Editor Pick, Invite, and Assign tasks are reset, automatically rescheduling reminders for the newly assigned Editor.