Citation Key is overwritten when importing bibtex code with ctrl+v even when the generator is disabled.

[MKHoffmann]

JabRef version

5.7 (latest release)

Operating system

Windows

Details on version and operating system

JabRef 5.7--2022-08-05--73c111c Windows 11 10.0 amd64 Java 18.0.2 JavaFX 18.0.1+2

Checked with the latest development build

• I made a backup of my libraries before testing the latest development version.
• I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

1. Disable Citation Key Generator
2. Copy a bibtex citation code from Google Scholar
3. Import it using ctrl+v
4. Citation Key is changed to something different.

Appendix

No response

[ThiloteE]

With "disable Citation Key Generator" you mean to disable "Overwrite existing keys" in the preferences?

[ThiloteE]

Related issues/PRs:

• Fix import entry by id does not generate citation key #8361 (Last major rework of citationkey behaviour)
• When pasting an entry into jabref, check whether key already exists #8406

[koppor]

We think, our preferences are not well organized in this respect. Please check following setting

[koppor]

Since requires internal refactorings, we postpone this after the release of v5.8.

[MKHoffmann]

Yes, all these settings are disabled. I should add, I am using Jabref on a Windows 11 machine.

[koppor]

Our test case:

Library without following entry:

@Article{test-key-not-generated,
  author = {Test Author},
}

1. Use JabRef build as of today (not 5.7)
2. Run on Windows 10
3. Copy the entry from GitHub to the clipbard
4. Paste entry

Result:

Video of it https://www.loom.com/share/d5098caf604e456296169fa68841d09e

[MKHoffmann]

For version 5.8 and Windows 11: If I paste your test case, this is my output:

With the settings:

[koppor]

Oh, wow. Can you

1. Export your preferences (small arrow on the lower left side on the dialog) - and send them to us (web -> jabref.org)
2. Reset the preferences (if that is OK for you)
3. Change both (!) preferences again. The thing is, in your case, JabRef DOES NOT check "Overwrite existing keys", but uses "Generate new key on for imported antries". In other words: It does not matter what you ticket at "Overwrite existing keys", because this is about the behavior of the manual triggering of the key generator, not the logic running when importing an entry.
4. Check again

[MKHoffmann]

Sure, I will do that, how should I send it though? Via the forum or what is the preferred way?

[Siedlerchr]

you can send a mail to web@jabref.org

[MKHoffmann]

Thank you, I sent the preference settings and tried your steps, the problem still occurs.

[Siedlerchr]

Maybe related issue? #8644