I have recently come accross the following issue when discussing with Google Scholar team member. For back issues we use other publication dates for online version compared to the actual publication date of the original print version – this is due to the fact that the online version has been published on a basis of new terms (open access, CC licences). So, e.g., the issue published in print in 1960 has been published online in 2014, and 2014 is put as the year in publication date field of this issue and all articles. All other fields such as vol, iss, year are filled based on the original issue (e.g. vol 60, iss 2, year 1960). However, this couses that Google Scholar displays, following the above example, year 2014 as the publication date of the article from 1960. I noticed that the source code of an article’s landing page has the following metadata:
meta name=“citation_date” content=“xxx”
meta name=“citation_volume” content=“xxx”
meta name=“citation_issue” content=“xxx”
The “citation_date” part takes data from the article’s “publication date”. Maybe it would be reasonable to distinguish these dates in metadata? Following Wiley, they have, e.g.:
So for OJS “citation_online_date” could come from article’s “publication date” field while “citation_publication_date” from the issue’s year? Would it be enough? Or there would be additional field for inserting original publication date.
just wanted to find out whether there were any changes to the latest OJS code with regard to the publication dates, or are they planned to be introduced? Specifically, to distinguish between print and online publication dates. The Schedule for Publication option within Production tab contains only Published option. I am discussing this issue with Google Scholar as they pointed this out in our OJS instances (that the publication dates differ from issues year).
We are trying to make all first “Feature Request” posts follow the same structure. We hope this will make it easier to understand the requests and, at the same time, ensure that no relevant information is missing.
Could you please edit your post following this template?
Describe the problem you would like to solve
Example: Our editors need a way to […]
Describe the solution you’d like
Tell us how you would like this problem to be solved.
Who is asking for this feature?
Tell us what kind of users are requesting this feature. Example: Journal Editors, Journal Administrators, Technical Support, Authors, Reviewers, etc.
Add any other information or screenshots about the feature request here.