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:
- A "stop resolving for now" button as "cancel" only gives you the next entry
- A possibility to merge entries instead of generating a new key
- 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...
- I would like to have this feature, too!
- I don't care.