We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Latest development branch build (please note build date below)
Windows
Jabref 5.6 version 4d8e41c
Follow up to #8361
Original comment: #8361 (comment)
Looking quite good! Solved 2 issues. 1 new issue pops up 😂 Hopefully the last one. Bug3: Have options>preferenes>import and export>generate a new key for imported entries (overwriting their default) enabled. Have a customized key-pattern for the citation-key generator set in preferences. Have this preference set under citation-key generator preferences: Import entry by ID into library5 OR paste entry5 by ID into library5. Let's call this one entry5. Import entry by ID into library5 OR paste entry5 by ID into library5 AGAIN. Let's call this one entry5². Duplicate Merge Editor will emerge. So far so good. Click keep merged entry only Result: entry5² will get assigned citationkey-according-to-my-pattern+a Expected result: entry5² will get assigned citationkey-according-to-my-pattern Additional info: This becomes really weird when entry5 and entry5² are not exactly identical. E.g. entry5: date = {2016} entry5²: date = {2016-10-02} My key pattern includes the date into the citation-key. Therefore, key before merge: 2016 key after merge: 2016-10-02a, EVEN THOUGH 2016-10-02 would be unique in my library. All the other buttons work and I have not noticed any other bugs so far.
Looking quite good! Solved 2 issues. 1 new issue pops up 😂 Hopefully the last one.
Bug3:
options>preferenes>import and export>generate a new key for imported entries (overwriting their default)
keep merged entry only
Result:
citationkey-according-to-my-pattern
a
Expected result:
Additional info:
This becomes really weird when entry5 and entry5² are not exactly identical. E.g.
My key pattern includes the date into the citation-key. Therefore,
key before merge: 2016 key after merge: 2016-10-02a, EVEN THOUGH 2016-10-02 would be unique in my library.
2016
2016-10-02a
All the other buttons work and I have not noticed any other bugs so far.
No response
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
JabRef version
Latest development branch build (please note build date below)
Operating system
Windows
Details on version and operating system
Jabref 5.6 version 4d8e41c
Checked with the latest development build
Steps to reproduce the behaviour
Follow up to #8361
Original comment: #8361 (comment)
Appendix
No response
The text was updated successfully, but these errors were encountered: