Thanks. I am glad that this has been recognized as a to-do item. I still think that an output of the date of the last versions of the revised files would be a good solution (in addition to highlighting). (BTW In our case, the additional problem is that we already use color-highlighting for fast-tracked papers.)
I think a patch would be quite easy to do, but the database is so complex that I haven't figured out yet how to query the database for the dates of the latest author versions (I need a quick fix as my submission queue is getting out of control).
Your initial thinking that authors inform the editor works in our case (authors do notify the editor), but neglects the fact that the editor will usually not drop everything else immediately when an author email arrives, but defers looking at the ms and the author comments (it is a time-consuming process, and one needs to have a couple of hours time for this). If the editor has to keep a separate list of to-do items (or has to search his email), then this defies the purpose of an ms management system.
So bottom line is, I am grateful that this will be addressed, but still if you can come up with the code that looks up the dates of the latest submitted versions so that we can fiddle this into the table, that would be great.
We're intending to approach this using colour-coding for the next release; see http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=2683
. We had originally anticipated that authors would be in contact with editors to notify them of a newly uploaded version, but that hasn't tended to happen, so we'll be addressing the problem soon.
Public Knowledge Project Team