We are backtracking from OJS3 to OJS2 and will look for other submission system

Feature Requests
3

Within the limits of my frustration, I will try to be as constructive as possible.

  1. On article id. This is a requested feature by another OJS user that I hooked on to. What is frustrating is that OJS2 was brilliant on this–you always had the id number in sight, no matter where you where in the workflow (99%). So value was lost because, as you correctly state somewhere, as editors we are not programmers (“I understand that many groups don’t have developer expertise”).

  2. Our installed version is 3.1.1.4. On the sending emails to all coauthors, I have not been able to find any option to copy all coauthors in the correspondence to the corresponding author. This was automatic in OJS2. Now we cannot do it. Sending copies of emails to all authors is now best practice in journals.

  3. No, it is not related to How to send email to all authors of a submission in OJS 3.1.0.1?. To clarify the point, in OJS2, when you send emails, you can send a copy to yourself, or you can CC others, then the email is sent, it is logged into the system and it is sent as an actual email to the recipient. Now, apart from the log, now called editorial history, you can’t really be sure what came out, and it turns out that a notification is sent…This is a loss of value compared to OJS2.

  4. My proposal would be to keep the logic of OJS2, as shown here:
    Screenshot_2019-03-04%20%231538%20Review

  5. See figure.
    Screenshot_2019-03-04%20%231538%20Review-1

  6. Our version is 3.1.1.4

  7. No, there wasn’t. I requested the feature in 2015 Author should be able to complete submission or editor unsubmit or return to draft I was hoping that in a full upgrade of OJS this would have been included.

  8. Sending to draft is the same as unsubmit. Very helpful when authors send incomplete submissions without having to decline, or reject.

  9. My editorial assistant pointed this one out to me. She feels insecure that notifications have actually been sent. We have found more user problems but couldn’t list them all…

  10. The problem here is that OJS 3 has some nice things to it–better look and feel, great to switch between languages, some better user experiences. What is frustrating is that many good things from OJS 2 are gone and we don’t understand why.

If your’s is a small team, mine is probably even smaller.

And thank you for replying promptly.

Regards,

Vivienne