Skip to content

Unexpected behaviour of the new search feature #11823

@ytzemih

Description

@ytzemih

JabRef version

JabRef 5.16--2024-09-20--5ac788c

Operating system

GNU / Linux

Details on version and operating system

Linux Mint/Debian

Checked with the latest development build (copy version output from About dialog)

  • I made a backup of my libraries before testing the latest development version.
  • I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

  1. Open database with an entry A containing the string "xyz-abc" (choose as appropriate)
  2. Search for xyz AND abc
  3. Entry A does not appear in the results although it should (it did before the search feature update).
  4. Entry A will appear in the search results when using xyz abc (which in Lucene implies an OR used).

Hope anybody can reproduce this issue. I found the issue when looking for strings in the "comments" field but I tested that the issue should occur with the title field and perhaps other fields as well. The issue does not occur when using "xyz abc", so it seems the new search now expects strings to occur as substrings in separate words. I'm using search groups a lot and found that behavior today only because some entries where missing after the search-group migration.

Update: It also seems that the new search does not recognise string occurrences in the keywords anymore.

Appendix

...

Log File
Paste an excerpt of your log file here

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions