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

When pasting an entry into jabref, check whether key already exists #8406

Open
ilippert opened this issue Jan 9, 2022 · 3 comments · Fixed by #8361
Open

When pasting an entry into jabref, check whether key already exists #8406

ilippert opened this issue Jan 9, 2022 · 3 comments · Fixed by #8361
Labels
bug Confirmed bugs or reports that are very likely to be bugs duplicateFinder keygenerator type: enhancement

Comments

@ilippert
Copy link
Contributor

ilippert commented Jan 9, 2022

Is your suggestion for improvement related to a problem? Please describe.
When I paste an entry into JabRef, I occasionally mess up my library because an entry with that citation key already exists.

Describe the solution you'd like
JabRef should notify me when I paste an entry and an entry with the same key already exists. I think this already happens as part of the import function, but not when an entry is pasted.

@Siedlerchr Siedlerchr added bug Confirmed bugs or reports that are very likely to be bugs type: enhancement labels Jan 10, 2022
@Siedlerchr
Copy link
Member

Siedlerchr commented Apr 4, 2022

Only works if you copy + paste the article twice

@Siedlerchr Siedlerchr reopened this Apr 4, 2022
@koppor koppor mentioned this issue Apr 4, 2022
6 tasks
@koppor
Copy link
Member

koppor commented Apr 4, 2022

The cause is probably our duplicate check. We need to work on checking the bibtex keys when pasting...

@Article{Kopp2015,
  author    = {Kopp, Oliver and Martin, Daniel and Wutke, Daniel and Leyman, Frank},
  journal   = {Enterprise Modelling and Information Systems Architectures},
  title     = {The Difference Between Graph-Based and Block-Structured Business Process Modelling Languages},
  year      = {2015},
  pages     = {No 1 (2009)},
  volume    = {Vol 4},
  doi       = {10.18417/EMISA.4.1.1},
  language  = {en},
  publisher = {Gesellschaft für Informatik e.V. (The German Informatics Society)},
}
@Article{Kopp2015,
  author    = {Kopp},
  year = {2015},
}

@koppor
Copy link
Member

koppor commented Apr 4, 2022

The issue is fixed when automatic key generation is in place --> JabRef automatically detects duplicate entry; if no duplicate, the key is generated to be unique

We need to check the behavior if existing keys should not be overwritten

grafik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs duplicateFinder keygenerator type: enhancement
Projects
Status: Low priority
Development

Successfully merging a pull request may close this issue.

4 participants