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

Possible Duplicates - Bibkey Comparison #7395

Closed
kristofmeixner opened this issue Jan 29, 2021 · 4 comments · Fixed by #7708
Closed

Possible Duplicates - Bibkey Comparison #7395

kristofmeixner opened this issue Jan 29, 2021 · 4 comments · Fixed by #7708

Comments

@kristofmeixner
Copy link
Contributor

The 'Possible Duplicates' has a 'strange' behavior when comparing the bibkeys.
If there are two papers of the same author (e.g. Mayer) and the bibkeys are Mayer2019 and Mayer2019a or Mayer2019 and Mayer2019b it would make sense from my point of view to have the 'first' bibkey selected in the mere view.
This would be Mayer2019 in the first case or Mayer2019a in the second case.
However, the later is always selected, i.e., Mayer2019a resp. Mayer2019b.

@alfureu
Copy link

alfureu commented Jan 31, 2021

Not sure I completely understand this issue but I was wondering whether this is related to #7262 (comment)

My suggestion would be to highlight any duplicates (i.e. not the 1st occasion) in the Entry Table by making the font colour of the entry red by default.

@kristofmeixner
Copy link
Contributor Author

The issue occurs in the merge view, when I merge the entries. Then the bibtexkey selected is the one of 'higher order'.

@calixtus
Copy link
Member

calixtus commented Feb 15, 2021

Refs JabRef#331 JabRef#110

@SuXiChangZhen
Copy link
Contributor

Hi, I am a software engineering student and interested in this issue. Is it better if the first entry always has a smaller dictionary order when merge two entries. Hope I understand the issue correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants