-
Notifications
You must be signed in to change notification settings - Fork 1
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
Found false negatives #37
Comments
Sure thing @dschaehi. I'll test it soon. Thanks for your feedback! |
Hi @dschaehi, I think the most direct reason is that their DOI values are different, which causes Zotero to no longer match other fields. I'm not sure if it is common practice to treat the preprint version on Arxiv as equivalent to the published version. Any thoughts? Thanks! Best, |
Hi @ChenglongMa, I see. The thing is that often times I don't want to keep both versions and I discard the arXiv version as soon as I find a published version. There are few cases I want to keep both, because sometimes arXiv versions are more comprehensive than the published ones that are constrained by page limits. Best, |
Hi @dschaehi, I came across this article. Since January 2022, arXiv began assigning DOIs to the preprint papers. Authors are not only allowed but also encouraged to connect their papers with external DOIs. Thus, the impetus largely rests with the authors. While developing a custom duplicate detection method appears to be the optimal solution, the current workaround may necessitate manual upkeep of these duplicates. I will try my best to make the custom duplicate detection method available ASAP. Thanks! Best, |
Thanks for the information, @ChenglongMa. Best, |
Hi @ChenglongMa,
Thanks again for the recent update, which removed all false positives in my case.
However, I found false negatives today, i.e., duplicates that are not shown in duplicate items (see the items in the attached Zotero RDF file).
Can you check whether this is specific to my setup or a general issue?
Best,
Jae
Exported Items.rdf.zip
The text was updated successfully, but these errors were encountered: