Skip to content
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

Closed
JasonGross opened this issue Sep 5, 2020 · 8 comments · Fixed by #7720

Comments

@JasonGross
Copy link

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.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2021

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!

@JasonGross
Copy link
Author

I suspect this issue is still relevant, given that #6395 has been closed without any indication of it having been fixed

@SuXiChangZhen
Copy link
Contributor

@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?

@JasonGross
Copy link
Author

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.)

@SuXiChangZhen
Copy link
Contributor

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.

@Siedlerchr
Copy link
Member

Yep and gui wise mabye under the Network tab. @calixtus is the master of preferences atm, maybe he has a btter idea

@mlep
Copy link
Contributor

mlep commented May 7, 2021

Note that there is now (5.3) a "Customization" tab which includes some network configuration:
ksnip_20210507-171420

@SuXiChangZhen
Copy link
Contributor

OK, I get it. My teammate @ryyyc and I was thinking put it in the "Customization" where user can custom DOI URI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants