Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

arXiv.org translator imports original date rather than current revision date #1992

Open
nschneid opened this issue Aug 20, 2019 · 4 comments

Comments

@nschneid
Copy link
Contributor

commented Aug 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.

@zuphilip

This comment has been minimized.

Copy link
Collaborator

commented Aug 29, 2019

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 original-date which can be saved in the extra field?

@nschneid Do you want to fix this issue yourself?

@adam3smith

This comment has been minimized.

Copy link
Collaborator

commented Aug 29, 2019

agree with the first part, but I don't think original-date is the right approach for the first date, no. That's typically used for the actual date of publication of a republished paper, not the date of a first version of a manuscript and it'll cause unexpected behavior in (some) citation styles.

@nschneid

This comment has been minimized.

Copy link
Contributor Author

commented Aug 29, 2019

@nschneid Do you want to fix this issue yourself?

I don't have time now, sorry.

@zuphilip

This comment has been minimized.

Copy link
Collaborator

commented Aug 29, 2019

Okay, I will try to look into this and fix it.

I guess we should rather take the newest date, which we could determine by sorting the strings.

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...

I don't think original-date is the right approach for the first date, no

Okay, but I try to save additionally the version number, if you are looking at a specific one.

zuphilip added a commit to zuphilip/translators that referenced this issue Aug 29, 2019

Prefer latest date in arXiv.org.js [web + search]
This solves zotero#1992.

However, when you are on the website of the specific
version of the paper, then it will try to find the correct
publication date in the XML and save the version
number as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.