Wrong date imported from RIS file
Hi,
I'm using RIS files to create citations in my library. I noticed for several papers, the online publishing date is read by Zotero rather than the actual publishing date.
Examples are:
https://journals.aom.org/doi/10.5465/amj.2016.0819
Zotero reads the online publishing date (2018), while the actual date is 2019.
Similarly, for
https://pubsonline.informs.org/doi/abs/10.1287/orsc.1100.0525?journalCode=orsc
Zotero read 2010, while it should read 2011 as the publishing date.
I read a similar discussion about anothe Informs journal, but as you can see in the first example, AOM journals RIS files are showing similar errors.
Any way this can be corrected? Or is the error on the publisher's end, not providing the correct info on their RIS files?
As a sidenot, importing the citation in .bib format seems to work correctly, but misses other fields such as Journal Abbreviation.
Thanks in advance for any help.
I'm using RIS files to create citations in my library. I noticed for several papers, the online publishing date is read by Zotero rather than the actual publishing date.
Examples are:
https://journals.aom.org/doi/10.5465/amj.2016.0819
Zotero reads the online publishing date (2018), while the actual date is 2019.
Similarly, for
https://pubsonline.informs.org/doi/abs/10.1287/orsc.1100.0525?journalCode=orsc
Zotero read 2010, while it should read 2011 as the publishing date.
I read a similar discussion about anothe Informs journal, but as you can see in the first example, AOM journals RIS files are showing similar errors.
Any way this can be corrected? Or is the error on the publisher's end, not providing the correct info on their RIS files?
As a sidenot, importing the citation in .bib format seems to work correctly, but misses other fields such as Journal Abbreviation.
Thanks in advance for any help.
Y1 - 2018/08/27
PY - 2018
DA - 2019/06/01
And we go with Y1/PY over DA, which I think makes sense, but it's also not something that's well defined in the RIS "standard," so it'd be hard to point a publisher to something that says "you're wrong" here. We may just have to adjust the behavior here somehow, but it's not trivial to do without possible unintended consequences