|
Step 3. Submitting the Volume3.2 Uploading Files to the ASPCS Server 3.3 Compiling on ASPCS Server and Submission 3.6 Sending the Manuscript to the Printer
When your volume is assembled on your local machine and ready to upload to the ASPCS server, please complete the Pre-Submission form linked below. Please email the completed Pre-Submission Form to aspcs@aspbooks.org. The Pre-Submission Form allows the ASPCS staff to set up the user account and password you will need to login to the ASPCS linux server, load the volume files, and compile them on the server. The Pre-Submission Form is available in the following formats:
3.2 Uploading Files to the ASPCS Server The next step is to upload your volume to the ASPCS linux server. When your volume compiles correctly and looks good on your local machine, please upload all source files to the ASPCS linux server using the username and password you received from the ASPCS Publication Manager. Make sure you upload all files for the manuscript, figures, and photos (.tex, .eps, etc.). Please don't upload temporary LaTeX files or any modified style files. They will be replaced with standard ASPCS versions on the server. You don't need to upload the final .pdf of the entire manuscript because it will be regenerated on the server. We recommend compressing them into a .zip or .tgz archive file for upload. When the files have been uploaded, please notify the Publication Manager . The simplest way to upload files is using sftp to put the files in the editor's working directory. Using ssh or sftp, upload your files, unpack them, and confirm that they are all in place with the correct subdirctory structure before notifying the Publication Manager that the files are in place in the editor's working directory. If you are not able to use sftp to upload your files, please contact the Publication Manager for instructions on alternate methods for transferring the files. After the files are uploaded and copied to the editor's working directory, this will be the master copy, and any further changes by authors or editors will need to be made on the linux server. Please notify the Publication Manager whenever you are working on the manuscript to avoid version conflicts. Hard copies of manuscripts are not accepted, and should not be sent. 3.3 Compiling on the ASPCS Server and Submission The next step is to compile the volume on the ASPCS linux server, just like you did on your local machine, and confirm that it compiles without errors (or fix any errors that appear). Additional details on how to login to the linux server and compile the manuscript can be found here. When you log in, you will be in the editor's working directory by default. Once you have compiled the volume on the ASPCS server, please review it carefully, one page at a time, to look for items that may have changed when compiling on the linux server. If you have questions or if problems arise, please notify the Publication Manager. If the volume compiles correctly and no errors are found, please notify the Publication Manger that the manuscript is ready for the next step, the aesthetic review. The volume is not considered to have been officially submitted until it compiles correctly without errors and the Publication Manager confirms that it does so. The Publication Manager will assign a volume number, copyright date, LCCN, and ISBN numbers only after the submission process is officially complete. 3.4 Aesthetic Review Upon notification that the manuscript has been successfully submitted and is ready for review, we will run a "Preflight Report" to determine if the PDF will have problems when sent to the printer. The types of problems identified during Preflight include image resolution, hairlines, font issues, color space issues, etc. We will also inspect the manuscript for aesthetic problems. We do not proofread the entire volume for typos or other corrections; we only check the overall aesthetics of the manuscript, checking items such as margins, running heads, table of contents layout, consistency of author and title names, pagination, image quality, etc. Following the aesthetic review, editors are responsible for correcting any problems found in the review process. Corrections must be made on the working copy on the ASPCS linux server. If the editor needs help making corrections, the editor may request that we make the changes at a rate of $35.00 per hour. Depending on ASPCS staff availability, having our staff make corrections can delay publication, so this should be considered a last resort for getting problems fixed. Some problems can be fixed more efficiently by our staff, however, so please consult with the Publication Manager about any problems you may experience. It is important for us to track changes and resolve conflicts that may arise when editors and ASPCS staff make changes at the same time. It is therefore critical that editors notify the Publication Manger when actively editing the volume, either on the ASPCS server or on your local machine. 3.5 Final Review Once the aesthetic review corrections have been made the editor will compile the volume again on the ASPCS server and review each page of the latest PDF file to make sure everything is exactly as it should be. The editor then notifies the Publication Manager that the manuscript is ready. ASPCS staff will make any final corrections they feel are needed, and the editor and co-editors will have one final opportunity to make any editorial changes before the manuscript is sent to the printers. Once the manuscript goes to the printer for proofs, any further editorial corrections will be billed $50 each. (See Overview of the Publishing Process for further information on stages of publishing and related costs).3.6 Sending the Manuscript to the Printer Once the editors have made their final review, the Publication Manager will send it to the printer. An electronic proof in PDF format is typically returned from the printer within two weeks. Go to Step 4: Proof Stage. |