# Save key mapping when merging or detecting duplicates

**URL:** <https://discourse.jabref.org/t/save-key-mapping-when-merging-or-detecting-duplicates/1682>\
**Category:** Help\
**Created:** [July 6, 2019, 6:04pm UTC](https://discourse.jabref.org/t/save-key-mapping-when-merging-or-detecting-duplicates/1682 "2019-07-06T18:04:32Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [July 7, 2019, 8:06pm UTC](https://discourse.jabref.org/t/save-key-mapping-when-merging-or-detecting-duplicates/1682/3 "2019-07-07T20:06:45Z")

</div>

Btw,

> So far so good. But now let’s assume that I already have a latex document with references with the old keys, e.g. one to `author_foo_bar_baz_2019` . Now I have to manually write down, during the merge process, which key changes into which so I can find-replace the old keys in my latex files.

You might be also interested in the new LaTeX integration feature which @davidemdot is currently developing during GSOC. I think this could be an interesting use case as well.

> [@Project: LaTeX integration (please give us your feedback!)](http://discourse.jabref.org/t/project-latex-integration-please-give-us-your-feedback/1660):
>
> Hello! This summer I will be working on the LaTeX integration project for GSoC: The core of the proposal is a wide improvement of the LaTeX integration with JabRef, focusing on the end-user, whose characteristics have been studied before: 69% use LaTeX and 87% are researchers. The goal is to make the work easier for our users. I will develop several tools for analysing and checking LaTeX text documents: finding bibliographic entries (what are used, how many times, and where) and counting word…

---

_[View the full topic](https://discourse.jabref.org/t/save-key-mapping-when-merging-or-detecting-duplicates/1682)._