Integrations with ScholarOne and Editorial Manager

The integrations for ScholarOne and Editorial Manager are built into Oversight. They create Submissions and send reports back as configured by Clear Skies staff.

These integrations create Submissions and Checks, which display in Oversight. Note that both platforms have some details around which IDs are unique and stable (and suitable for use as external_submission_id), and which ones are shown to users, but not unique (and suitable for display_external_id).

Customers or Service Providers may list submissions via the API and get the report and status, as usual.

Service Providers are able to register for callbacks for given sites to get status updates. See Service Providers.

Editorial Manager

A Submission is created for each Editorial Manager Submission.

The external_id is taken from the publication_code:document_id in the Editorial Manager schema. The document_id is known to be unique within the publication_code. This is not shown to the user in Editorial Manager.

The display_external_id is taken from manuscript_number in the Editorial Manager schema. This is optional and not unique, but it is what is shown to the user in Editorial Manager.

Note that, as manuscript_number is optional depending on the configuration of the Editorial Manager site, it may not be present on the Submission at the time of creation. Users may therefore see the external_id in the Oversight UI sometimes. This is a known limitation.

ScholarOne

A Submission is created for each ScholarOne Submission.

When there is a new Author Submission event, a new Submission is created with the new Submission ID. We internally link it to the prior version.

The external_id is taken from documentId in the ScholarOne API.

The display_external_id is taken from submissionId in the ScholarOne API.