Ticket #799 (new defect)

Opened 6 years ago

Boolean searching: AND NOT behaviour

Reported by: ak19 Owned by: nobody
Priority: moderate Milestone: 2.87 Release
Component: Greenstone2 Runtime Severity: major
Keywords: Cc:

Description

When using either MG or MGPP (not Lucene, I think), and having advanced fielded searching on, AND NOT results behave weird.

Use the TestDocs? test collection from SVN. Build the collection and turn on advanced and fielded searching. Search for "images" in text and "de" in filenames. Then set the boolean operator to be AND NOT (so it is expected to exclude any files with the filename "de" among the results where the text contains the word "images".)

Which of the indexers has this problem?

Was AND NOT implemented for MG and MGPP?

Is the submit button sending the correct request?

May need to trace the request through to find out what is happening.

Note: See TracTickets for help on using tickets.