Unlinked files Importer: Fall back for files failed to be processed

Features
4

Dear Thiote E,

  1. I am using
    JabRef 5.3–2021-07-05–50c96a2
    Linux 5.3.18-lp152.106-default amd64
    Java 16.0.1
    JavaFX 16+8
    and I must admit that there that some error messages show up when I start jabref. So maybe this creates additional problems.
    I would need to check, where to find information on these problems, since currently I just have the observation that the import does not work without further comments. And I would have to check, which files I could send in view of copy-right issues

  2. So, if one starts to deal with one of the files created, and starts to add
    the information to the emergency entry, one should check then (e.g. by using the title and search) at some time, if this entry already exists. Of course, then one should merge these entries, or coping the file link form the emergency entry to the already existing entry.
    But, this is not only a problem for my emergency entries, but also for those entries that could be parsed somehow by the file importer, but the result is not correct. (I had observed for many preprints from the arXiv Server that the large arXiv Information that is “printed” on the first page in the pdf-file becomes the title in the Bibtex entry).
    Hence, already in this situation one may have two entries for one paper, and has deal with this situation somehow. And is the importer able to deal with the situations that there is an unlinked file and some entry in the database with the corresponding bibliographic data?
    I am not sure, but I believe the major concern in the issuUnlinked files Importer: Continue (fall-through) when individual files fail to be processed 7206 seemed to me the problem that after one incomplete import run some files were already imported and if these files are selected in the next run again there may be several entries for the same file.

But, in view of your remark: if some falied import dialogue is implemented, one can also add the possibility to to tich/untick the creation of
these emergency entries. In my suggestions I had in mind the situation that
there may be an implementation that simply allows to continue the import after an error without am elaborated failed import menu.
If one would like to get rid of the (unchanged) emergency entries, one could use search to find using the part of the title that is fixed. Or maybe, the imported entries/falied could be somehow marked/ groued by jabref, see my Featuere suggesttion Automatic markging/grouping enties after actions like mergiing duplicates/serching for unlinked files