Legacy Manuscript Information

There are three different types of legacy manuscript information that may be either manually entered or imported into EM: in-process manuscripts out for revision (manually entered), in-process manuscripts (manually entered), and completed manuscript information (imported).

In-process manuscripts out for revision, including submissions where the Author has been notified of a Revise decision (from the legacy system), as well as submissions where the Author has not yet started submitting the revision, should be submitted directly into EM, rather than into the existing legacy system. Journals should therefore make it a point to let Authors with manuscripts that are in the revision stage to submit revisions to EM. The revision would be submitted using a special Article Type (e.g. Legacy Revision), indicating the submission is actually a revision from the legacy system. Historical information, such as Editor and Reviewer names, performance information, and comments, can be entered into the EM system by creating ‘user-defined fields’.

Note: Your Journal may opt to ‘run down’ the legacy system until there are no more in-process manuscripts. In other words, both the legacy system and EM would be run in parallel, until there are no more in-process manuscripts in the legacy system

In-process manuscripts that have been submitted to the legacy system, and the paper is ‘somewhere’ in the review cycle (e.g. with the Journal Office, with a handling Editor, out with one or more Reviewers, or waiting for an Editor decision) must be manually submitted into EM. As these manuscripts are already in the process of peer review and are therefore not static, there is no automated method of loading manuscripts in-process into EM. The Journal Office will manually submit the manuscripts to EM, re-assign Editors, re-invite Reviewers, etc.

Completed manuscript information can be imported once your Aries Account Coordinator enables this option, and you have appropriately configured the ‘Additional Data Policies’ in PolicyManager.

Note: Legacy manuscript data is not connected to People records, nor can legacy manuscript records be linked to regular EM submission records. The purpose of the Legacy Manuscript database is to preserve a record of those submissions processed using a different tracking system, and to make those records available to users of the new system

The fields you will create in PolicyManager serve as the ‘map’ for the file of completed legacy manuscripts that is then imported into EM.