Ingested submissions do not have a system PDF when they are first received into a publication's EM site. A PDF must be built and approved before the submission can move forward into the editorial workflow.
When initially ingested (from an Author Portal or Manuscript Service Provider), a submission goes to the New Ingested Submissions folder. A publication may choose to have an Editor/editorial staff manually send the new ingested submission back to the Author to build and approve the system PDF, or staff may edit the submission metadata and build and approve the PDF.
Alternatively, publications have the option to automatically direct ingested submissions to the Corresponding Author's Submissions Sent Back to Author folder and to trigger a notification letter to the Corresponding Author. This also moves the submission to the Editor's Submissions Sent Back to Author for Approval folder.
When ingested, a revised submission goes to the Revised Ingested Submissions folder. Publications may also automatically direct ingested revised submissions back to the Corresponding Author. This triggers a notification letter to the Corresponding Author. The submission moves to the Author’s Revisions Sent Back to Author folder and the Editor's Submissions Sent Back to Author for Approval folder.
Go to AdminManager > Configure Manuscript Service Providers for Ingest Service Confirmation.
Make settings for each Manuscript Service Provider as needed.
Note: If the setting, Automatically build and approve PDF, is enabled in addition to either or both of the Send Back to Author settings, the automatic PDF build takes precedence. If the build succeeds, the Send Back to Author action is not triggered. See Automatic PDF Build for Ingested and Transferred Submissions
If necessary, create a notification letter to the Corresponding Author and associate it with the ActionManager event, Submission Sent Back to Author. For details on letter configuration, see Create Letters.
To return to previous page click ALT + left arrow