-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JabRef should support users entering their own API keys for the lookup services that use API keys #6877
Comments
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:
Thank you for your contribution! |
I suspect this issue is still relevant, given that #6395 has been closed without any indication of it having been fixed |
@Siedlerchr Hi, I am intersted in this issue. But I wonder how to design the UI to let user enter the api key. Which one is better, add in the preferences or pop up a dialog when exception occur? |
I think it should be in preferences. The setting should be stateful; I shouldn't have to reenter it every time an error occurs. (And it should be possible to go back to the default key, which it wouldn't be if there was a stateful change that could only be entered on error.) |
Thank you for your reply. I agree with you, and I think other api keys(like ieee) should also be included in the preferences. Otherwise, it may seem odd if only springer's api key can be changed. |
Yep and gui wise mabye under the Network tab. @calixtus is the master of preferences atm, maybe he has a btter idea |
OK, I get it. My teammate @ryyyc and I was thinking put it in the "Customization" where user can custom DOI URI. |
I am running into the same issue as #6395 . As per #6369 (comment), this is probably Springer rate-limiting JabRef's API key. If there's no way to permanently fix this problem, I'd suggest adding a dialog box that lets advanced users enter their own API keys, to work around the app-limits.
The text was updated successfully, but these errors were encountered: