PM checklist before transferring tickets to CS/COEs
Our primary goal should be to resolve the query at our end as much as possible. Only if we are unable to resolve it, should it be sent to other departments:
- Check the job instructions
- Check the job files
- Adding notes for CS/COEs: We have a lot of CMs from non-English speaking countries, so they may not necessarily understand the FL’s query. Also, there are times where the editor asks multiple questions within the same mail with not all pertaining to CS. Adding notes for CS will ensure that there aren't unnecessary back-and-forth.
Incomplete/missing formatting information on job page
- Always check the SERVICE-RELATED INFORMATION section in the lower right of the page, as CMs sometimes update the INQ page without adding a to-do for PMs.
- The journal name/URL might be part of the job instructions.
- The formatting guidelines may be provided in a PDF file (sometimes with a template .dot file) in the reference folder.
- The journal name and URL might be provided under the same field, thereby making the URL unusable. You can merely copy the entire text into a notepad file and separate the name from the URL. Look for https or http to help identify where the URL begins
- Two URLs might be provided in the same field resulting in a huge combined URL that will not function. Once again, follow step 4.
Formatting requirements for Korea Corp Jobs
Korea Corp CM tends to add the journal name as an FYI for PMs and editors. However, as long as formatting requirements is mentioned as No, we don't need to check with CS, and can assume that the job doesn't need formatting.
1000-word or 50% discrepancy allowed for shopping cart clients
Ever since clients have been allowed a leeway of a 50% word count discrepancy, we have seen mails from editors regarding word count issues almost double. This could easily lead to the editors getting an impression that we’re trying to cheat them by not mentioning the right count on the job page and getting more work out of them for a lower fee. I had a word with the BE cell, and they informed me that a tool that will auto-calculate the word count of a document will be implemented in a month or two, and this discrepancy allowance for clients will be removed. So if an editor writes to us regarding these issues, please assure them that this is a temporary inconvenience and a fix can be expected by the coming quarter.
Formatting-related queries [COE]
Component | SES | PES/PES+/Scientific Editing |
Apply template | Yes | |
Structured/unstructured abstract | Yes, ask editor to refer to guidelines for more details | |
Missing title or keywords | No, flag with comments | Yes, provide suggestions |
Word count/Page length | Yes | |
Moving figures/tables/some sections | Yes, ask editor to refer to guidelines for more details | |
Format references | Yes | |
Check/verify references for accuracy | No | Yes, using Crossref/Google Scholar |
Adding missing information in references | No, flag with comments | Yes, using Crossref/Google Scholar |
Making highlights | No, flag with comments | Yes, if mandatory |
Making significance statement, Summary, etc. | No, flag with comments | |
Blinding paper | Yes, ask editor to refer to guidelines for more details | |
Interdepartmental Communication:
Translation
The T&T deadline on all translation jobs are two hours prior to their delivery deadline. This 2-hour buffer doesn't apply to translation CQs.
When requesting for more time on any translation job, all communication must happen on ticket. PMs must ensure to transfer the job along with the ticket to TLPM and ping the TranslationSupport group on Teams. You also need to update them as soon as the job is completed and transferred back to the Geeta T interface.
CS Markets
When a job is delayed, inform the respective CS group on Teams, irrespective of whether the delay note is being sent immediately or at a later time.
Under Wiley, for SES and PES service, we do not offer formatting, in case client needs formatting, they have to opt for the Manuscript formatting addon