# JabRef v5.15 is not using the merged entry + random changes to bibfile

**URL:** <https://discourse.jabref.org/t/jabref-v5-15-is-not-using-the-merged-entry-random-changes-to-bibfile/5403>\
**Category:** Help\
**Created:** [January 23, 2025, 12:57am UTC](https://discourse.jabref.org/t/jabref-v5-15-is-not-using-the-merged-entry-random-changes-to-bibfile/5403 "2025-01-23T00:57:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![deRemo](https://avatars.discourse-cdn.com/v4/letter/d/e56c9b/32.png) [@deRemo](https://discourse.jabref.org/u/deRemo)\
**Post date:** [January 23, 2025, 12:57am UTC](https://discourse.jabref.org/t/jabref-v5-15-is-not-using-the-merged-entry-random-changes-to-bibfile/5403/1 "2025-01-23T00:57:16Z")

</div>

Hi all,

I started using JabRef a few days ago, and I’m not sure if I’m using it correctly—I’d really appreciate your help. ☹ I’m trying to merge multiple `.bib` files that contain many duplicates with slightly different citation keys.

For example, I want to keep the citation key from the imported library:

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/jabref/original/2X/9/9a0e7ae4a42ba613eaa4532b1694b37cda9a5fd8.png)  
by clicking on “li2023FTworkflowSched”, which I prefer over “Li2023”.  
Then, I press “Keep merged” and “save all”.

Not only the merged entry is not applied as requested, but JabRef keeps unexpectedly changing the citation key of other entries in an erratic manner—sometimes just one entry is affected, while other times it changes all of them—and I can’t figure out why (but it seems to depend on which “save” button I use). Honestly, it’s taking more time than manually copying the entries. ☹

---

<div class="post-metadata">

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\
**Post date:** [January 23, 2025, 3:23pm UTC](https://discourse.jabref.org/t/jabref-v5-15-is-not-using-the-merged-entry-random-changes-to-bibfile/5403/2 "2025-01-23T15:23:17Z")

</div>

Hi,

Welcome to JabRef 🙂

There is an option in the preferences, “Overwrite existing citation keys” and “Autogenerate citation keys”  
For importing stuff, there is another option under “Web search”

Regards  
Christoph

---

<div class="post-metadata">

**Author:** ![deRemo](https://avatars.discourse-cdn.com/v4/letter/d/e56c9b/32.png) [@deRemo](https://discourse.jabref.org/u/deRemo)\
**Post date:** [January 24, 2025, 12:05pm UTC](https://discourse.jabref.org/t/jabref-v5-15-is-not-using-the-merged-entry-random-changes-to-bibfile/5403/3 "2025-01-24T12:05:45Z")

</div>

Thanks for the response.

If I may give a suggestion, you should clarify the difference between “importing” a library and “loading” a library. The latter does not seem to be affected by the overwrite option, which honestly should be disabled by default, if I may (unless you are actually building a new library from scratch). But I’m not sure about that either, I’ll have to rebuild the whole library to be sure

---

<div class="post-metadata">

**Author:** ![ryan-carpenter](https://avatars.discourse-cdn.com/v4/letter/r/b487fb/32.png) [@ryan-carpenter](https://discourse.jabref.org/u/ryan-carpenter)\
**Post date:** [February 25, 2025, 7:28am UTC](https://discourse.jabref.org/t/jabref-v5-15-is-not-using-the-merged-entry-random-changes-to-bibfile/5403/4 "2025-02-25T07:28:00Z")

</div>

The pattern in your example is probably too complex to reproduce automatically, and I presume that you need to restore the original keys exactly as they were. Otherwise, I would suggest regenerating the keys after deduplicating the library. For future reference, JabRef has very flexible options for key-generation and file-naming options, which you might appreciate ([documentation](https://docs.jabref.org/setup/citationkeypatterns)).

There are definitely ways of merging citation keys that would be easier than manually copying entries. I can help if you haven’t dealt with this another way by now.