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

Support more complicated search expressions #840

Closed
tobiasdiez opened this issue Feb 20, 2016 · 5 comments
Closed

Support more complicated search expressions #840

tobiasdiez opened this issue Feb 20, 2016 · 5 comments

Comments

@tobiasdiez
Copy link
Member

It would be nice to search for

  • recently published articles: year > 2000
  • highly ranked: ranked > 3

Related request for groups: https://sourceforge.net/p/jabref/feature-requests/232/

@Le-wi
Copy link
Contributor

Le-wi commented Jan 7, 2019

Hi, I like to clean up old issues, is this still a thing? @tobiasdiez

@tobiasdiez
Copy link
Member Author

This feature has not been implemented yet and is still relevant. I think, it is best to combine it with #1975, ie use lucene query parser. This might turn out to be a bit more work, but if you have the time go for it!

@Le-wi
Copy link
Contributor

Le-wi commented Jan 16, 2019

Ever since you wrote it takes more time ... I can't force myself to do it :D

I'm afraid it implies architectural changes and a ton of tests etc. And I don't want to leave a half finished mess. So now I wonder:
Can you (a) break it down for me or (b) point at something smaller but still helpful :)

@tobiasdiez
Copy link
Member Author

Yes, it's quite a big project but as you appeared motivated I didn't want to stop you in your tracks. If you already started working, you may create a WIP PR and maybe somebody takes over.

A good starting point are the issues tagged with "good first issue". If you don't find something in this list that triggers your interest, just let us know what kind of things you are looking for (ui vs backend?) and we may be able to suggest something fitting. Our chat https://gitter.im/JabRef/jabref is probably better suited for this.

@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
Status: Discussion
Development

No branches or pull requests

3 participants