MLEP

For the keywords, I suggest keeping the ones provided by the DOI fetcher only. Removing the parts in parentheses might be a plus.

I am not sure that I got you right. When the user provides the arXiv ID (e.g. `1811.10364`), the user also provides, in fact, the DOI. This is because you...

You could possibly add the prefix `10.48550/arXiv` because you have identified that `1811.10364` is an arXiv ID. And, currently, JabRef is already able to identify if a string is an...

If we want to support case changes for multiple languages, we need to identify first the language of the string first. There seems to be libraries dedicated to this, such...

I agree for the "too broad for the moment". However, if you provide the right casing (and a BibTeX style that does not alter it), BibTeX is ok with it,...

I forgot that the Relevance and Printed columns are not displayed by default. You have to add them to the entry table in Options -> Preferences -> Entry table.

@ruoyu-qian: You may want to enhance your previous contribution to JabRef. Cheers.

@ThiloteE Not really: my key pattern is [auth][shortyear]. Since my "almost empty" entry does not have an author or a year, I cannot really blame this feature. :wink:

To manage keywords, JabRef has also a dedicated window, accessible through the menu `Edit -> Manage keywords`. _About a better keyword management:_ While BibTeX does not define the field `keywords`,...

Being a special field in biblatex, the content of `keywords` is "usually not printed" (according to the doc). A user could decide otherwise by altering a citation style (like with...