Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign uparXiv.org translator imports original date rather than current revision date #1992
Comments
This comment has been minimized.
This comment has been minimized.
The translator looks for the XML data e.g. http://export.arxiv.org/oai2?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai%3AarXiv.org%3A1810.04805 and there for DC.date, which in this example looks like <dc:date>2018-10-10</dc:date>
<dc:date>2019-05-24</dc:date> Current strategy is then to just take the first value. I guess we should rather take the newest date, which we could determine by sorting the strings. Would it make then sense to save the original date as a separate CSL-field @nschneid Do you want to fix this issue yourself? |
This comment has been minimized.
This comment has been minimized.
agree with the first part, but I don't think |
This comment has been minimized.
This comment has been minimized.
I don't have time now, sorry. |
This comment has been minimized.
This comment has been minimized.
Okay, I will try to look into this and fix it.
That would work for this example. However, then it would not be possible to cite explicitly the older version. Both versions share the same XML file, which might not be the best to work on... Moreover, the BibTeX in arXiv itself is giving the wrong date in these cases with several versions as well.. Hm... I have to work a little bit more then...
Okay, but I try to save additionally the version number, if you are looking at a specific one. |
nschneid commentedAug 20, 2019
E.g. https://arxiv.org/abs/1810.04805 imports with a date of 2018-10-11 rather than the current version's date of 2019-05-24.
IMO this is harmful because it will be impossible to tell from the Zotero-based bibliography which version is being referenced.