Define One-Way Transfer Relationships

By default, confirmed transfer relationships between publications are bidirectional, meaning either publication may transfer submissions to and receive submissions from the other publication. Once a transfer relationship is confirmed, the sending publication may further configure that relationship to suppress outgoing transfers to the target publication.

When outgoing transfers to a target publication have been suppressed, that publication will not be presented as a transfer option to Editors or Authors in the following locations:

Select Transfer Target Publications page: Shown when an Editor submits a decision in the Reject and Transfer family (if the page is configured to display).
Transfer Submission page: Shown when an Author agrees to transfer the submission. (The full list of available transfer target publications is shown on this page if the page above is not configured to display to Editors.)
%TRANSFER_TARGETS% merge field in a Reject and Transfer decision letter.
Transfer recipient drop-down list: Shown on Set Final Disposition page when an Editor selects a final disposition of Transfer.

Establishing transfer relationships and defining one-way transfer relationships are slightly different for each of the three types of transfers:

Between two publications in a People-Sharing Group, aka Inter-Journal Resource Sharing (IJRS) Group: Transfer relationship is automatically confirmed when group transfer is enabled on the home publication; then either publication may suppress transfer to the other, thus defining a one-way relationship.
Between two publication sites using Editorial Manager (EM-to-EM): Transfer relationship must be confirmed by both publications; then, either publication may suppress transfer to the other, thus defining a one-way relationship.
Between a publication using EM and a publication not on EM (EM-to-non-EM): No confirmation required. Transfers to the non-EM publication can be restricted by one-way transfer configuration; however, incoming transfers cannot be suppressed.

TO CONFIGURE:

Transfer relationships must be confirmed before one-way relationships may be defined. For details, find applicable information in Transfer Submissions Between Publications.

To define a one-way transfer relationship, go to AdminManager > Configure Cross-Publication Submission Transfer.

Scroll to the Configure Transfer Target Publications section of this page.
Click the Enable One-Way Submission Transfer link to open the Enable One-Way Submission Transfer page. This page lists all active confirmed transfer target publications.
Check the box next to a publication to suppress transfers to that publication.
When finished, click Submit.

The Configure Transfer Target Publications section of the Configure Cross-Publication Submission Transfer page lists all publications that have been configured as transfer targets and the current status of the transfer relationships. Possible statuses:

Unconfirmed: Prospective target publication has not confirmed the transfer relationship.
Confirmed – bidirectional: Two-way transfer relationship confirmed.
Receive from only: For IJRS-linked and other EM publications. Checkbox on Enable One-Way Submission Transfer page is checked to suppress outgoing transfers. (This status cannot appear for non-EM publications, as EM uses a different mechanism to ingest submissions from non-EM publications.)
Transfer to only: For IJRS-linked and other EM publications, the other EM site has suppressed transfers to the home site. For non-EM sites, the home site has enabled transfer to the non-EM site.
Transfer suppressed: For non-EM publications only. Checkbox on Enable One-Way Submission Transfer page is checked to suppress outgoing transfers.
Transfer and receive both suppressed: For IJRS-linked and other EM publications. Both publication sites have suppressed outgoing transfers. (Example use case: Both publications want to suspend the transfer relationship temporarily while processing still-pending transfer offers).
Transfer disabled: For IJRS-linked publications only. Either the home publication or the target has not enabled cross-publication transfer for the People Sharing Group.