Improved duplicate key resolving

Features
1

Currently, JabRef checks if there are duplicate keys on opening a database. There are three things which could improve the experience if you happen to click yes when offered to resolve the issue:

  1. A “stop resolving for now” button as “cancel” only gives you the next entry
  2. A possibility to merge entries instead of generating a new key
  3. A button to automatically remove exact duplicates

Actually, 1 can be implemented with an option to search for duplicate entries instead as this has both the other features.

Yes, I get merge conflicts from version control quite often…

Please vote if you support this proposal:

  • I would like to have this feature, too!
  • I don’t care.

0 voters

Show results
2 Likes
2

:thumbsup:

Yes, this all are some valid points which would really improve the workflow.

For 1. I would propose two buttons “Skip this duplicate” and “Cancel duplicate key resolving”.

1 Like
3

And for consistency:

  • instead of “Use”(Left None Right) at the top of the window, use “Keep”
  • instead of “Merged entry” at the bottom left, use “Merged entry preview”
4

I added a small patch for 1. using “Ignore” and “Cancel” (as they were readily available).

2 Likes