Hello,
I have a question about the CROSSREF plugin concerning the date of publication. Recently, at our platform, we have been uploading archive issues of our journals and activating their DOI numbers.
As a result, the date of the print version is for example the year 2000, 2001, 2002, while the online publication date is 2015.
Unfortunately, as the DOI number is activated, in an XML file, all we get is:
This may, therefore, confuse the readers, as it indicates that the original version came out this year.
This publication date will be drawn from the article’s metadata.
You can find it in User Home → Editor → Archives → [Select Article], then look under the Editing tab for the Scheduling section and the “Published” field.
If the articles have varying publication dates per issue, you will need to change them here one-by-one.
If all articles within an issue have the same publication date, you can reset them all at once:
User Home → Editor → Back Issues → [Select Issue] → Issue Data, then look for the option “Reset article publication dates” under the Identification section.
I wanted to bring up this thread again as we are currently experiencing a similar problem. We recently upgraded to OJS 3.4. In 2015, our staff added hundreds of articles to one of our journals, but did not take into account the publication date. All the articles that were actually published between 1950 and 2014 now have a 2015 publication date. Unfortunately, it doesn’t help if I just change the publication date of the issue, as it is no longer possible to apply this to all the articles in that issue.
Is there a way to change the publication date in the database? For example, if we correct the issue date, we could perhaps use a script to update the article publication date. Does anyone have an idea?
Yes, you can adjust the publication dates in the database directly in publications.publication_date and issues.publication_date. (Take a backup first, as always!)
Regards,
Alec Smecher
Public Knowledge Project Team