Hi Jay and Vanessa,
This has actually come up separately a few times in the past week or so, and we're investigating ways to deal with the problem. As far as we know, the problem only appears when the Expedited Submission or Quick Submit processes are used to publish back issues -- in those cases, the "date published" element is set as the date/time when the issue as a whole has been published within the system. As far as we can tell, this problem doesn't crop up when back issues are imported using the XML Import/Export plugin, which requires that articles include a date_published element, which is in turn used to populate the metadata correctly. I would appreciate it if you could confirm that this is the case for both of you -- that is, if you could let me know exactly how you have been publishing back issues.
The problem itself is two-fold:
1) correcting invalid metadata that has already been published;
2) ensuring that bad metadata won't get published again .
Problem 2 is relatively easy to solve -- we will be adding the ability to edit articles' date published metadata. (See http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=4718
, and please CC yourself for future updates -- this bug will be of relatively high priority for us.)
Problem 1 is more difficult than problem 2, although we believe we have found a way to identify incorrect data fairly consistently. If this proves to be the case, we'll be able to at the very least add a check to OJS that will remove the bad data on upgrade. We are investigating whether this data can actually be automatically corrected, but that may be a bit more difficult.
If you have any questions, please let us know. And please do feel free to ping us if you don't hear anything about problem 1 in the near future.