Configure Batch Editor Assignment

Editors with permission to assign other Editors may also be granted permission to select multiple submissions and assign them all simultaneously to a specific Editor. This batch-assignment capability is available both for initial assignment/invitation by the Special Relationship Editor and for Editors in the decision chain. This option may also be used to reassign submissions from one Editor to another.

Assign submissions

Users with this permission see a Batch Assign to Editor button. The button may appear in three Editor folders, depending on the Editor role's other permissions:

  1. New Submissions Requiring Assignment: Editor role also has RoleManager permission Receive New Submissions in "New Submissions Requiring Assignment" folder.
  2. Revised Submissions Requiring Assignment: Editor role also has RoleManager permission Receive New Submissions in "New Submissions Requiring Assignment" folder.
  3. New Assignments: Editor role also has RoleManager permission Receive Assignments in "New Assignments" folder.

Editors receiving the batch of submissions may be invited or assigned to handle them (based on RoleManager configuration for their role). Assigned Editors will see the batch of submissions in their New Assignments folder. Invited Editors will see the batch of submissions in their New Invitations folder. Invited Editors must use the applicable Action link to accept or decline the invitation for each submission.

Reassign submissions

The batch approach may also be used for reassignment of previously assigned in-flight submissions. Additional RoleManager permissions are required.

To configure:

Go to RoleManager > Editor Role. Grant permissions to the applicable Editor roles:

  1. Assign Editor: Allows Editor role to make assignments.
    1. Allow Batch Assignment: Allows Editor role to assign batches of submissions.

Additional permissions are required to allow Editor roles to make batch reassignments. Different combinations of permissions allow Editors to accomplish different reassignment actions. For details, see Configure Unassign Editor or Replace Editor (Modify Editor Chain).

Configure letters to notify the Editor being assigned the batch of submissions and, in the case of reassignments, the Editor being replaced. Go to PolicyManager > Email and Letter Policies > Edit Letters.

  1. Letter Family: Assign/Unassign Editor for Submission Batch

Merge field recommendations:

  1. %BATCH_EDITOR_ASSIGNMENT_MS_LIST% inserts a list of all the submissions selected for batch assignment to an editor. This merge field is intended for use only in assignment and unassignment letters.

For details on letter configuration, see Create Letters.

Go to PolicyManager > Editor Assignment Policies > Configure Batch Editor Assignment Pages.

  1. Use the Current Editor Being Unassigned drop-down menu to select a default notification letter.
  2. Use the New Editor Being Assigned drop-down menu to select a default notification letter. The letter selected here will also be the default to send when an Editor is reassigned a batch of in-flight submissions. (The menu displays only letters configured in the Assign/Unassign Editor for Submission Batch family.)
  3. Optional: Edit or enter instructions to be displayed on the Assign Editor for Selected Submission page.
  4. When finished, click Submit.

Note: If multiple batch assignment notification letters are configured, the assigning user will have to click the Send Custom Letter button to open the Batch Assign to Editor – Confirm and Customize Letter page in order to select the appropriate letter from the drop-down list. A publication may have more than one batch assignment letter available if some Editors are invited rather than assigned to handle submissions or if a letter has been configured to notify Editors for a batch reassignment of submissions. If more than one batch assignment notification letter is available, consider including custom instructions to guide the assigning user.

 

To return to previous page click ALT + left arrow