Unify open and import database action and show errors

[kristofmeixner]

JabRef version

5.3 (latest release)

Operating system

GNU / Linux

Details on version and operating system

No response

Checked with the latest development build

• I made a backup of my libraries before testing the latest development version.
• I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

1. Open file bug-1.bib
2. Only 2 of 3 entries are read
3. Save the library
4. The third entry is commented out (see file bug-2.bib)

Appendix

bug-1.txt
bug-2.txt

[Siedlerchr]

When I copy the missing entry to the source tab of a new entry:

I think I found the issue, the problem is that the field name "Early Access Date =" contains spaces. That's why it's skipped.
The parsing error should be shown to the user as well

[kristofmeixner]

Okay, this seems more a Web of Science issue.
I wrote them an email.

But the parsing error wasn't shown to me.

[Siedlerchr]

Stumbled across this warning not shown stuff as well: JabRef has two methods for opening bib files:

JabRefGUI -> openDatabases is called when JabRef is started and will show any errors/warnings from the parser.
The other code for opening is in "OpenDatabaseAction" which does not show any errors from parser Result.
The same applies for "ImportAction". In the latter, there is still a TODO comment...

[calixtus]

We should try to unify these different methods.

[calixtus]

Main Issue seems to be the whitespaces in the field name.

Deeplinks for information resources on field name conventions

• https://mirror.dogado.de/tex-archive/macros/latex/contrib/biblatex/doc/biblatex.pdf
• TameTheBeast - http://tug.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf
• https://docs.jabref.org/advanced/fields

[k3KAW8Pnf7mkmdSMPHz27]

Refs. #8556 #8555 (merged methods might have prevented the issue)

[calixtus]

Background: There are three different methods to import/open bib files:

• ImportAction/ImportCommand
• OpenDatabaseAction
• JabRefGui#openDatabases

[koppor]

Another comment on the code is available at #361 (comment)

[koppor]

While working on this, #9714 should also be solved.