The publication staff person who receives a new submission (or revision) is responsible for assigning an Editor to handle that submission. The act of assigning the Editor creates a special relationship between the staff person and the submission.
This special relationship means that the staff person is connected to the submission, even though the staff person is not assigned to the submission. This person may be referred to as the Special Relationship Editor or Attached Editor.
This Special Relationship Editor is able to receive certain types of correspondence in order to monitor the progress of the submission through the peer review process. The correspondence includes any letters configured in ActionManager for the staff person's role for events related to:
If more than one staff person is responsible for receiving and assigning new submissions (and new revisions) to Editors, then each staff person creates a special relationship only with those submissions s/he assigns.
Many publications prefer to create a single user record for the publication staff as a whole. (Everyone on the staff uses the same username and password to log into the system.) This user record can have multiple email addresses, so that staff members can each check their own email; all staff members receive all emails directed to the publication staff identity.
Alternatively, some publications opt to place certain publication staff members in charge of certain Editors. Staff members assign new submissions and new revisions to their designated Editors and then follow up with those Editors (and the Reviewers assigned by those Editors).
If the first assigned Editor assigns another (subordinate) Editor, the Attached Editor continues to have the special relationship with the submission.
The Attached Editor relationship works differently for proposals. If a letter is configured to go to the Editor role of the staff person who assigns the first Editor on a proposal, only that individual staff person receives the letter, not all users assigned to the same Editor role. The correspondence includes any letters configured in ActionManager for the staff person's role, for the following events:
For example:
Publication XYZ has two people in the editorial office (User 1 and User 2) with the Editor role, Publication Staff. User 1 creates a proposal and assigns the first Editor. The first Editor invites an Author. A letter is configured to go to the Publication Staff role at the ActionManager event, Author Invited. User 1 receives the letter. User 2 does not, because User 2 does not have a special relationship with the submission.
For commentaries, both the Attached Editor and the Handling Editor for the parent submission (i.e., the submission on which the commentary is being requested) are able to receive letters configured for their roles for the following events:
For example:
Publication XYZ has two people in the editorial office (User 1 and User 2) with the Editor role, Publication Staff. User 1 assigns the first Editor to a regular submission. The first Editor uses the Solicit Commentary function to invite some Authors to comment on the submission. A letter is configured to go to the Publication Staff role at the ActionManager event, Solicit Commentary. User 1 receives the letter. User 2 does not, because User 2 does not have a special relationship with the submission.
Publication staff with this special relationship to a submission may also receive notifications about changes in due dates (for Authors and Reviewers) as well as information about payment of publication charges and submission transfer.
For more information on events, see descriptions in ActionManager Events Quick Reference Guide.
To return to previous page click ALT + left arrow