Known Limitations

Access to the Author Portal Transfer application and transfer functionality is restricted within a Tenant’s portfolio of journals. For example, submissions cannot be transferred from one publisher to another.

Current limitations:

  • Current supported transfer workflow is administrator-initiated, and not fully automated.
  • Submissions made using administrator-initiated transfer are created as new, direct submissions:
    • They appear in the ScholarOne Admin center in the External Submission in Draft queue, as with all other submissions made using Author Portal, and not in the Manuscripts Transferred IN queue.
    • They do not feature the green stripe used in the ScholarOne UI to distinguish transfers made using the native ScholarOne-to-ScholarOne transfer.
    • They do not automatically retain the previous submission's history or metadata in the ScholarOne audit trail.
    • Unless peer-review reports or other notes are included, transferred submissions are not otherwise readily identifiable inside ScholarOne from other new, direct submissions ingested from Author Portal.
  • Author Portal Transfer does not yet support the native ScholarOne-to-ScholarOne transfer-by-decision functionality, which is triggered by a ScholarOne Reject with Referral decision type and automatically transfers a submission between journals.
    • ScholarOne's submission groups functionality can be used as a workaround in order to allow journals that migrate to Author Portal to continue to receive transfers through the ScholarOne transfer functionality which is not yet supported in Author Portal Transfer. Such submissions do not begin in Author Portal. Instead, authors submit and remain in ScholarOne throughout the submission workflow.
    • If Author Portal Transfer were used to fulfill transfers initiated through the native ScholarOne-to-ScholarOne transfer workflow, the following undesirable results would occur:
      • A duplicate ScholarOne submission would be created. The submission from Author Portal Transfer would not replace the draft created automatically in the Destination Journal as part of the ScholarOne process.
      • There would be no green stripe in the ScholarOne UI to indicate the submission was a transfer.
      • Existing ScholarOne reporting on transfers would be disrupted or broken.