Stuck in creating library entry after Fetcher 'DOI' did not find an entry ...

[WolfgangFahl]

Steps to reproduce the behavior:

Im am trying to add a reference to
http://dx.doi.org/10.2777/1524
by creating a new article entry using the doi 10.2777/1524:

and get stuck here. I'd expect that after this error message i'd be able to create the entry manually.

[koppor]

Video of the issue: https://www.loom.com/share/1a7fb6101a8e4d499c4a39f2d9f11108

Solution approach:

Add buttons: "Add entry manually" and "Return to dialog" (Refs koppor#149)

[betochf]

I think I could solve this, it should be a customDialog instead of errorDialog?

[koppor]

I am not sure whether a JavaFX class CustomDialog exists. It should be a custom dialog (see other dialogs in JabRef). HTH.

[Siedlerchr]

Have a look at JabRefDialogService . We provide different dialog (and also custom dialog) implementations to use

[mrcstan]

Is anyone working on this issue? It not, I would like to work on it.

[koppor]

@mrcstan Sure - go ahead!

[mrcstan]

@koppor / others, I plan to create a dialog box that allows user to either "Add entry manually" or return to the original dialog box as suggested above. After the "Add entry manually" button is clicked by the user, should the Others menu open allowing user to choose the article type? I am guessing "Return to dialog" means returning to the original dialog box where the DOI can be changed? I am currently using an existing dialog box called showConfirmationDialogAndWait (see attached screenshot). When "Add entry manually" is click, a true value will be returned and the user will be directed to the menu that allows them to add the entry manually. Let me know if that is in the correct direction.

[mrcstan]

I submitted a pull request 8203. I received an error during the test "Deployment / Create installer and portable version for macOS." The error message is "Run apple-actions/import-codesign-certs@v1
80 Error: At least one of p12-filepath or p12-file-base64 must be provided." I was able to install the code successfully on my MacOS machine, and I don't think I have changed anything that affects the installation. Let me know if you have any hint what could be causing the issue.

[Siedlerchr]

Thanks for the interest! We have a checkstyle config https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace

And don't worry about the Mac deployment it will fail every time on forks because it accesses some signing keys that are stored in GitHub secrets and are not available when the Action runs on a fork

[evanpickett]

Are there still any problems regarding this issue that might need to be addressed? I'm only asking because the status is still listed as "open"

[WolfgangFahl]

I have not seen a release yet that would have the improvement. Is there some kind of prerelease to check?

[Siedlerchr]

We would like to ask you to use a development build from https://builds.jabref.org/main and report back if it works for you. Please remember to make a backup of your library before trying-out this version.