Note: A publication cannot use this method to deposit to NIHMS if they are participating in PMC. If the publication is not participating in PMC, they are eligible to use this method as follows: The publication must be recognized by the NLM. The publication must have an account with the NIHMS. The publication must configure a Submission Production Task as described in the “To Configure” section below. The publication must enter their NLM TA code into a custom transmittal field as described in the “To Configure” section below. The publication must ensure that file descriptions are unique for all files within a file type (i.e. all Submission Items in the Figure family must have different file descriptions (if selected as Assignment Files), all Submission Items in the Table family must have different file descriptions etc.) The NIHMS requires a file from the Default or Document Submission Item family to be sent to them, along with any relevant figures or tables. The system PDF should not be sent as an assignment file, as the NIHMS builds its own PDF. Due to the fact that this type of task is usually at the end of the Production process, this will typically be configured as a Milestone Task. After the Task has been assigned and the selected files have been transmitted, publications may go to the NIHMS Web Interface and review the files: Login to the NIHMS web interface () Click the ‘publisher’ login route from the login route table. Enter the username and password for your established account, and click the ‘Login’ button: You will be automatically directed to the NIHMS interface. The FTP’ed submission should be listed, and will initially have the status “Awaiting submitter approval of PDF receipt”. Note: It may take up to an hour from FTP for the file to go into this status. Clicking the article title in this interface allows you to review the NIHMS PDF (listed as “PDF Receipt”): Click on the ‘PDF Receipt’ link. Ensure that all manuscript, figure and table files that were FTP’ed have been built into the PDF. Ensure that any supplemental files are listed on the last page of the PDF, and on the web page as “Supplemental Files”. After clicking the ‘PDF Receipt’ link a listing of the transmitted files is displayed.
Clicking the ‘Submit’ button saves this letter and adds it to the ‘History’ page of the submission, inserted into the list chronologically. The text ‘(External)’ is displayed next to the letter link identifying this letter as External Correspondence. This correspondence is then visible to all users with ‘View Production Correspondence History’ permission enabled. Editors with the ‘Add/Edit External Correspondence’ permission may also Remove or Edit these external correspondence items, if desired. Editors may also use the External Correspondence feature to note that a phone call was received, such as an Author calling to check on the status of a submission. In this example, the Editor could use the ‘Add Editorial Correspondence’ button, and simply enter a Description of ‘Phone: Status Query from Author’, and the date/time of the call to record it. Publish Information A new target date, the ‘Submission Target Online Publication Date’ has been added to the Actual Publication Dates. The layout of this page changes if the submission is assigned to a Schedule Group after production has been initiated, to show two columns: Target and Actual Publication Data. For Commentaries, the Target data will initially show the information entered when requesting the commentary. For all other submissions, the Target date will show information entered during the production process, either manually for the submission, or inherited from an assigned Schedule Group. To Configure: No configuration is necessary Automatically Copy Target Information to Actual Information on Publication Publications may be configured so that the Target Information for a submission can be automatically copied into Actual Information fields for all submissions in the Schedule Group when that Schedule Group is closed, or for individual submissions when End Production is clicked for that submission. Publications may further configure this option to allow or prevent existing “Actual” information from being replaced when Production is ended on a submission. To Configure: To allow Target publication information to be automatically copied to Actual publication information fields when production is ended, go to PolicyManager, and click the new Configure Automatic Copy of Target to Actual Publication Information link. To allow Submission Target Publication Information to be copied to Actual Publication Information when Production is Ended or a Schedule Group is closed, select/check the “Copy Submission Target Publication Information to Submission Actual Publication Information” checkbox. When this box is selected/checked, the two Radio Button sub-options are enabled. The default option is “Do not overwrite existing values for Actual Publication Information”, but the option to allow overwriting is available for selection.
Closed Schedule Groups This folder lists all Schedule Groups that have been previously closed, for example, issues which have been published. Note: Groups must currently be manually closed to remove them from production and into this folder. Use this folder to: Re-open closed Schedule Groups Review published material To Configure: Go to RoleManager, Editor Role or Publisher Role, select the role and set the ‘Manage Schedule Groups’ permission. View All Submissions with Production Completed This folder lists all submissions for which production has been completed, and therefore has the production status ‘Production Completed’. Use this folder to: Return submissions to production Access data and files for completed submissions Note: Submissions must be manually closed to move them from production into this folder. This can be done for individual submissions, but note that all submissions assigned to a schedule group will be closed and moved into this folder when the associated Schedule Group is closed. To Configure: Enable the RoleManager permission ‘View All Submissions in Production’. Submission Tasks Reminder Report This report allows users to create a list of tasks that may be overdue, nearly due, or which have been in progress for a specified time. Reminder letters can be generated from the list. The reporting process spans several pages. The first page allows users to define a report; use the options here to limit reports to specific sets of submissions, tasks or assignees, and to define the date range for reminders. Use ‘Select Production Task’ to limit the report run to just one type of task. Use ‘Select Schedule Group’ to limit the report run to tasks associated with submissions that have been assigned to one schedule group, for example to chase up tasks for a specific issue. Use the ‘Assigned to’ check boxes to limit the report to tasks assigned to selected types of user. Choose one of the ‘Show open Production Tasks…’ settings to base the report on. For example, choose the option ‘Show open Production Tasks that are [__] days past their due date.’ and set the figure to ‘0’ to list all submissions due today. It is possible to further limit the results to specific article types and section/category settings. After a user ‘Submits’ a search, he or she is presented with a list of task assignments matching the search that was just set up; specific assignments may be selected. Click the ‘Send Reminders’ button to send reminder E-mails, as