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

Search in import (inspection) window #4781

Closed
alfureu opened this issue Mar 19, 2019 · 3 comments
Closed

Search in import (inspection) window #4781

alfureu opened this issue Mar 19, 2019 · 3 comments

Comments

@alfureu
Copy link

alfureu commented Mar 19, 2019

This is a follow-up on the issue #4685 as kindly suggested by @Siedlerchr.

It would be great if the new import dialog will have a search where one ideally can filter the listed results. Maybe implementing author:john, title:goal-oriented, etc, filters might be useful.

@tobiasdiez
Copy link
Member

I'll like your suggestion. It makes sense especially for (larger) imports. However, for the web search, we usually show only between 10 to 20 entries. Thus, in case, I would suggest that we show a text field with the search query and changing the text would trigger a new search.

@alfureu
Copy link
Author

alfureu commented Mar 19, 2019

Thanks @tobiasdiez for the feedback, I was unaware of the fact that the results window shows only 10-20 results. Personally, I liked the compact view of the 3.4 version, where a lot of articles were loaded. I think the best would be if one could conduct some basic literature review searches in the import as well. Just in idea.

@github-actions
Copy link
Contributor

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
None yet
Development

No branches or pull requests

2 participants