-
-
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
meaningful search #12296
Comments
Which means in 5.x, it used to work? |
The key problem seems to be that year/date alias fields are not resolved/handled I tested with 3 entries and the fields.
this is also visible in the SQL query
|
JabRef 5.14--2024-06-03--109600b search here works still wonderfully :) Oliver, I guess here I can suggest to split the issue: the date bug issue vs my repeated frustrations with the "new search". If of any use for the latter, I am happy to create a new issue on the larger frustration and try to generate a screencast to illustrate, walk you through, my "frustrations", might help to turns this into something more specific and then a productive conversation ;) I apologise for the outburst with the notion of frustration, which you and the other developers do not deserve! |
JabRef version
Other (please describe below)
Operating system
GNU / Linux
Details on version and operating system
JabRef 6.0--2024-12-11--38576bb Linux 6.11.11-300.fc41.x86_64 amd64 Java 23.0.1 JavaFX 23.0.1+4
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
date
,Date
,year
.Date=2012
date=2012
year=2012
will all produce different hits.
Sorry, the new search engine makes me typically frustrated.
Appendix
No response
The text was updated successfully, but these errors were encountered: