Excluding custom fields from merge dialog/import

[funnym0nk3y]

Is your suggestion for improvement related to a problem? Please describe.
Importing data from DOI or ISBN sources usually includes a citation key which differs from the format used in the library. There is also a similar case for files, where there isn't anything one can get online.
However those fields are displayed in the import merge dialog where one needs to check each field if it should be included or not.
Custom import filters via a java class are way out of my abilities and I don't know if they could be used in online imports.

Describe the solution you'd like
The process of getting information online could be eased if there was the ability to customize the import of certain fields.

[Siedlerchr]

This is already possible:

[funnym0nk3y]

Thanks for the reply but I don't see how to in this image. Could you elaborate?

[Siedlerchr]

Checking the first option : Generate a new key for imported entries will overwrite the keys coming from an import.
E.g. the DOI fetcher returns @article{abcdefg.... Now the citation key generator will overwrite it with your defined pattern.e. g generating a new key for that entry to @article{einstein1980...

[k3KAW8Pnf7mkmdSMPHz27]

Maybe references #1283

[funnym0nk3y]

Unfortunately this does not solve my problem:

When importing additional data the citation key is still imported.

[Siedlerchr]

@funnym0nk3y I come back to this issue as I recently investigated another issue. If you not want to import the citation key, you should set it to the left or the middle option.

[funnym0nk3y]

But I need to set this for each entry, right? Would be more convenient if one could disable citation key import entirely.

[Siedlerchr]

ah now I understand your suggestion. you want to exclude certain fields from the merge dialog.
Could be considered in #6190

[ThiloteE]

@funnym0nk3y Please try https://builds.jabref.org/pull/8361/merge/

Disabling overwriting keys upon import can be enabled/disabled here:

This method works with your pull-request Christoph.

(Edit: I cannot reproduce #8354 (comment))

Edit²: My bad. If you click on merge, obviously the citation key will be used you chose. Now, if you had enabled the preference to overwrite citation keys, then EVEN IF YOU CHOOSE THE ORIGINAL KEY FROM INTERNET, then it will be overwritten using the citation key pattern you use in your library. At least, if you use the version of Jabref in this pull request.

[ThiloteE]

Excluding custom fields from merge dialog of course goes beyond that. Would suggest to rename this issue then.