Step 3. Submitting the Volume
When you are within one week of submitting your volume, please email the completed Submission Form (below) to firstname.lastname@example.org to request the remaining information needed to finish the front pages and the eyebrow/slug of the volume. The manuscript should be complete and ready to send at this point except for these last few items. Please do not send the Submission Form unless these items can be finished up promptly and the manuscript submitted within one week.
For more information on the ISBN, LCCN and copyright, see http://www.sheridanbooks.com/getstart.htm. This page is for your information only–do not submit any forms on this Sheridan Books page. Simply submit the Submission Form to ASPCS and we will apply for and email you all the numbers needed to finish the volume.
Due to problems that arise when a manuscript is not received during the same publication year as a volume number is requested, we now will rescind the volume number if we don't receive the manuscript within one month from the time the volume number is assigned.
The Submission Form is available in the following formats:
After successfully compiling and reviewing your manuscript locally, please upload all source files to the ASPCS server and recompile the manuscript here. This includes all files for the manuscript and figures (.tex, .eps, .ps, etc.). Upload time can be reduced by excluding the .ps and .pdf of the entire manuscript. These files are not necessary since the manuscript will be recompiled on the ASPCS server. We also recommend compressing them into a .zip or .tar.bz2 file.
Please contact Lisa at email@example.com after the files are uploaded and we will add them to the Subversion repository in preparation for compiling on the server (see below for more on Subversion, a version control software package). We will check out a working copy to our server for your use in compiling and making corrections remotely, if desired. Once the files have been uploaded to our server, the master copy will then reside with the ASPCS. All revisions made from this point on will need to be made by checking out files through Subversion. They may be checked out to your own computer, or you may work on them remotely in the working copy on our server and then simply commit the changes to the repository.
A hard copy no longer needs to be mailed; ASPCS will print one from the server for our aesthetic review.
Instructions for uploading files with a link to upload may be found at http://linux.aspbooks.org/upload.php.
Instructions for using the server and recompiling your volume, including specific commands to use, may be found at http://linux.aspbooks.org/connect.php.
The ASPCS server is configured with settings required by the printer so some discrepancies may arise when recompiling. However, compiling remotely on this server will allow you to review and modify the manuscript as produced with these required settings.
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 with this PDF. If questions or problems arise or when the manuscript is ready for ASPCS’s aesthetic review, please email Lisa at firstname.lastname@example.org. When the manuscript is ready for the ASPCS's aesthetic review, please email Amy Schuff at email@example.com.
To save both time and money, we strongly recommend that, while the ASP reviews your volume for aesthetic issues, all editors also review the entire volume at this point. Please send a copy to all co-editors for their review, because the additional readers will help catch editorial errors. Please give your volume a thorough edit before it is submitted to the printer. Corrections made at this stage only involve time and effort; however corrections made at the proof stage are billed by the printer at approximately $12.00 per page. Resubmitting an entire volume costs approximately $500.00 for a new proof. (See Overview of Publishing Process for further information on stages of publishing and related costs).
Upon notification that the manuscript is ready for review, we will run a Preflight Report to determine if the PDF will have problems when sent to the printer. These types of problems 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, proofing items such as margins, running heads, table of contents layout, consistency of author and title names, pagination, image quality, etc.
Following the ASP’s aesthetic review and the co-editors’ review, editors are responsible for correcting any problems found in the review process. Corrections may be made by using Subversion to check out the files either to your local computer or to the working copy on our server to work on remotely. If too limited on time, an editor may request that we make the changes at a rate of $35.00 per hour.
Please see checkout information at the following two links:
Once all needed editorial revisions and aesthetic issues have been corrected, please 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. Once you notify us that the manuscript is ready, we will send it to the printer. When the manuscript is sent to the printer, we invite you to print a complete copy for your reference. Please save this for the proof stage, to carefully compare the electronic proof to the printed hard copy. (See Step 4, Section 4.2.7 for items to review in the proof.) A proof is typically returned from the printer within two weeks.