Jabref: Check for comma separation in "keyword" field

[Codeberg-AsGithubAlternative-buhtz]

Using the dev version from today.

JabRef accept keywords in the keywords field without (or with space) separator.
By default biblatex use comma (,) as separator. Not using it causing some problems e.g. when you filter your bibliography by keywords.

Separators in biblatex can be modified. So I think it would not be the best solution for JabRef to check for comma only.

There should be a warning or something like that if you have multiple keywords but no comma between them.

[tobiasdiez]

If I understand you correctly you want to have a check that reports keywords={TestA TestB TestC} because there is no comma between the words, right? But what if the user decides to put spaces into their keywords like bibliographic manager, JabRef is the best (which would be two valid keywords)?

[Siedlerchr]

At least for keyword groups you can speficy your own keyword separator

[Codeberg-AsGithubAlternative-buhtz]

You understood me correct and I understand you.
Currently I have no solution.

But keep in mind: A user of JabRef shouldn't know much about biblatex syntax rules. JabRef is a GUI. IMO it is the job of a GUI to keep the user away from "to complex things". You have to find a way to vizualize this different possible and valid ways to use keywords.

e.g.
You know how keywords/tags are displayed on StackExchange (e.g. StackOverflow?). Do it like this would be ergonomic, user friendly and easy to understand. This would protect the user for having problems.

[Siedlerchr]

I think this is a good idea. For crossref field we have such highlighting, so could be implemented similarly

[DOFfactory]

I can second this, multiple websites provide multiple ways of keywords, unfortunately JabRef performs pretty poor in scraping them at the moment from these websites. Sometimes these are listed as keyword1, keyword2, keyword3, others as Key Word1; Key Word2; Key Word3 (please note the spaces) or Keyword1 [Tab] Keyword2 [Tab] Keyword3. It would be great if Jabref could automatically adjust the keywords into correct biblatex syntax based on these hidden/not so hidden characters.

[Codeberg-AsGithubAlternative-buhtz]

I aggree with Sidlerchr and DOFfactory

[github-actions[bot]]

This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs.

As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:

• If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
• Provide further steps or information on how to reproduce this issue.
• Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
• If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!