Recently, two papers had been published in a series of papers, and the result journal input system was less reliable than one. The document was not transmitted, the status of the review was not updated for three days, and eight emails were returned by editing. I'm sorryThere's a problem with the journal contribution systemThis is no longer the case, especially at the end of the year and during the graduation season, the main platform servers are like the spring train station. But the first reaction of most authors, when they're stuck, is to be in a hurry, to understand a few underlying logics, many of which look like the "genetic" bug himself。
What if there's a problem with the journal system
First of all, one of the worst: the system shows "had submitted" but your local e-mail confirmation is out of line. The last time i pitched some cssci, i turned around for 20 minutes, and i played "the server's busy, please try again later." i thought it was gone, and it was passed again in half an hour. As a result, the editor called and said that he had received two identical copies and almost called back. It was later known that the magazine was still using an old oa system for over a decade, and that the front end would collapse as soon as there were more people online at the time of writing, but the back office was already in the library。
In such cases, it is important not to repeat itself. First, leave a copy of any confirmation number that the system gives you, or even a miscalculation, even if the page is in circles. Two hours to refresh it, most of it stuck in the back end. It's just the front end. If more than 24 hours are still in "unsubmitted" mode, then take the mailbox and add a PDF note to the editor's office and say, "the system does not generate a confirmation number, please check that a copy has been received", usually back to you the next day。
Contributions to periodicalsSystem failureWho
Many people felt that the complaint was not useful and that the editorial office was not writing codes and had no luck with the server. But there's one line: the bottom of the magazine network is usually hungTechnical supportTelephone or it mailboxes, and editing mailboxes, are completely two entrances. I made a special "failure time line" before my last call -- a few points, a few points stuck, a few screenshots, the campus network used at the time, or a cell phone hotspot, and the other side was able to judge whether it was the side of the platform or your local network for almost 10 seconds, so you were not guessing there。
There is also a more disproportionate situation: the day the system is upgraded or the database is migrated, the large volume of manuscripts is returned. My roommate's story went out for a week, and suddenly jumped back from "editor's audit" to "to be submitted" and people got numbed on the spot. The editor later replied that the database was being migrated in the early hours of the day and that the technical team had spent half a day manually restoring her records. You're just gonna have to waitAll we can do is leave a copy of the source file locallyDon't count on the cloud-end version。
After all, there is a problem with the journal writing system, which in the short term is a platform that is not maintained, is technologically old and, in the long run, our authors rely too much on that web portal. I now have the habit of creating a local folder, a PDF, a data form, a cover letter, a confirmation screenshot, named by date and name. The next time the system gets windy, you've got the bottom of it, so you don't stare at a 40-minute circle page。
