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

Issue with INSPIRE web search #7274

Closed
isserstedt opened this issue Dec 30, 2020 · 3 comments
Closed

Issue with INSPIRE web search #7274

isserstedt opened this issue Dec 30, 2020 · 3 comments

Comments

@isserstedt
Copy link

isserstedt commented Dec 30, 2020

In my opinion, the INSPIRE web search does not work as expected anymore:

The search for, e.g., "Tanabashi:2018oca" should yield exactly one result but instead I get 10. In addition, among the search results is not the one I was looking for.

Furthermore, the key "Barrie:2019pqc" gets truncated to "Barrie2019" even though I turned off "Overwrite existing keys" in the preferences. This happens with every entry fetched from INSPIRE.

Version information:
JabRef 5.2--2020-12-24--6a2a512
Linux 5.4.0-58-generic amd64
Java 15.0.1

EDIT: Problem is still present in the following version:
JabRef 5.3--2020-12-28--020cc97
Linux 5.4.0-58-generic amd64
Java 15.0.1

@Siedlerchr
Copy link
Member

@DominikVoigt Do you have an idea? Is this related to the new search syntax?

@isserstedt
Copy link
Author

@Siedlerchr The old search syntax still works. Actually, there is no old syntax as far as I know. I guess the issue is related to the new API since INSPIRE got an extensive overhaul in 2020.

Regarding the unwanted key formatting, I have no clue where this could come from. But I doubt that the INSPIRE API provides a truncated/wrong key.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 1, 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!

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

No branches or pull requests

2 participants