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.

Sign up for GitHub

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

Jump to bottom

Duplicate Detection #7770

Open
WolfgangFahl opened this issue May 25, 2021 · 3 comments
Open

Duplicate Detection #7770

WolfgangFahl opened this issue May 25, 2021 · 3 comments

Comments

@WolfgangFahl
Copy link

I am using paste of a DOI to add references and find it astonishing that duplicates are not detected and another
"identical" entry is created.
I'd expect a warning in this situation at least "DOI" already assigned to ...
@Siedlerchr
Copy link
Member

Which JabRef version are you using? If I remember correctly, there has been some improvement to the duplicate detection in the current dev version. https://builds.jabref.org/main/

@Siedlerchr Siedlerchr added the status: waiting-for-feedback The submitter or other users need to provide more information about the issue label May 30, 2021
@WolfgangFahl
Copy link
Author

JabRef 5.3--2021-05-15--0a26d31

@ThiloteE
Copy link
Member

ThiloteE commented Mar 14, 2022 •
edited
Loading

I can reproduce.

Related: #8361 will probably fix this issue.

@Siedlerchr Siedlerchr added [outdated] type: bug Confirmed bugs or reports that are very likely to be bugs and removed status: waiting-for-feedback The submitter or other users need to provide more information about the issue labels Mar 14, 2022
@calixtus calixtus removed the [outdated] type: bug Confirmed bugs or reports that are very likely to be bugs label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Siedlerchr @WolfgangFahl @calixtus @ThiloteE