Publications can configure EM Ingest from a publisher’s Author Portal (AP) or a third-party Manuscript Service Provider (MSP) for use with invited submissions. When this feature is enabled, the "parent" submission (proposal or article for commentary) is linked in the system with the "child" submission submitted via the AP/MSP. The ingested child submission is received in the appropriate folder on the Editor Main Menu and appears on the View Related Submissions page for the parent submission in several folders on the Proposal Menu.
Ingest communication between EM and the AP/MSP may also be configured to allow Authors to accept or decline invitations via the AP/MSP. They can respond to invitations without logging in to EM directly, and the AP/MSP will notify the publication's EM site.
An Invited Authors section may be configured to display on Details pages, enabling an Editor to modify the invitation response date and/or the submission due date. If the response date or due date is changed, the system automatically notifies the AP/MSP of the updated information. This section includes status text indicating the date the API notification was sent. A Resend link enables an Editor to retrigger the notification push to the AP/MSP manually.
The merge field %AUTHOR_INVITATION_ID% is available for use in letters related to invited submissions. The merge field inserts the contents of the unique identifier field from the Invited Authors table for a particular Author.
Push notifications are sent to the AP/MSP. EMail notifications of ingest success, warning, and failure are sent to the AP/MSP and to publication staff. (These must be configured by your Aries Account Coordinator.)
To configure publication ingest notifications (email), contact your Aries Account Coordinator.
Go to AdminManager > Configure Manuscript Service Providers for Ingest Service. For the applicable AP/MSP, check the box next to the appropriate setting(s):
See the tables at the end of this article for details on push notifications governed by these settings.
Note: The system will display a warning if a system administrator tries to enable this setting for more than one AP/MSP.
Go to PolicyManager > General Policies > Define Details Page Layouts. The Invited Authors section may be configured to display on Editorial and Proposals layouts. For details, see Configure Details Page.
The merge field %AUTHOR_INVITATION_ID% is available for use in letters related to invited submissions. For details on letter configuration, see Create Letters.
The merge field %AUTHOR_INVITATION_ID% can also be used as part of a URL created by a Manuscript Service Provider to direct the invited author to a landing page in the MSP portal; the merge field ID as part of the URL will populate in EM letters to the invited author.
This merge field can also be used in combination with the publication code merge field to create a globally unique ID: %JOURNALACRO%%AUTHOR_INVITATION_ID%. When populated, this combination appears as: publication code + author invitation ID. Example: DEMOJ + 224 = DEMOJ224.
This table describes user actions and ActionManager events that will trigger push notifications. | |||
USER ACTION | ACTIONMANAGER EVENT | MSP PUSH NOTIFICATIONS | |
Author Invitations If enabled... |
Accepted Author Invitations If enabled... |
||
Editor invites (or reinvites) Author to submit. |
Invite Authors for Proposals OR Solicit Commentary on Submission |
EM sends a separate notification to MSP for each invited Author. | |
Editor assigns Author to a submission for a proposal or commentary. |
Author Assigned (Not Invited) for Proposal OR Author Assigned (Not Invited) for Commentary |
EM sends a separate notification to MSP for each invited Author. | |
Editor promotes Author from alternates list. |
Promote Alternate Author |
EM sends a separate notification to MSP for each invited Author. | |
Author accepts invitation from EM Author Main Menu or by using an EM deep link. | Author Agrees to Invitation | EM sends final update notification (for this push notification). | EM sends initial notification to MSP. |
Author accepts invitation from within MSP. | N/A | If sub-setting to allow inbound status updates is enabled, MSP sends notification to EM. | EM sends initial notification to MSP. |
Author declines invitation from EM Author Main Menus or by using an EM deep link. | Author Declines Invitation | EM sends final update notification (for this push notification). | |
Author declines invitation from within MSP. | N/A | EM sends final update notification (for this push notification). No additional notifications are sent by EM. | |
Editor uninvites Author. | Uninvite Authors | EM sends final update notification (for this push notification). | |
Editor unassigns Author. |
Author Unassigned after Accepting Invitation OR Author Unassigned after Assignment |
EM sends final update notification (for this push notification). | |
Editor changes due date for invited submission. | Invited Submission Due Date Changes | EM sends update notification to MSP. | EM sends update notification to MSP. |
This table describes metadata updates that will trigger push notifications to the MSP. | |||
USER ACTION | METADATA | ACTIVE MSP PUSH NOTIFICATIONS | |
Author Invitations If enabled... |
Accepted Author Invitations If enabled... |
||
Editor changes Author metadata. |
Author Type Firs tName Middle Name Last Name Rank Personal Identifiers External PeopleID ISO Code Country |
EM sends update notification to MSP when still active. | EM sends update notification to MSP when still active. |
Editor changes Editor metadata. |
First Name Last Name |
EM sends update notification to MSP when still active. | EM sends update notification to MSP when still active. |
Editor changes Parent (proposal/commentary) metadata. |
Invitation Type Parent Article Type Parent Article Title |
EM sends update notification to MSP when still active. | EM sends update notification to MSP when still active. |
To return to previous page click ALT + left arrow