Angular catalog - Advanced Search with OR and AND Yields Erroneous Results

Bug #2010306 reported by Michele Morgan
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Undecided
Unassigned

Bug Description

The Angular catalog groups advanced search terms differently than the traditional catalog

To reproduce this on a master Concerto system:

Set the library setting "GUI: Enable Traditional Staff Catalog" to TRUE

- Navigate to Cataloging - Search the Catalog (Traditional)
- Perform the following search:
 - keyword: symphony
 - Or keyword: concerto
 - And keyword: Tchaikovsky

Note that there are 4 hits
The search appearing in the resulting search box is:
((symphony || keyword:concerto) && keyword:tchaikovsky)

- Navigate to Cataloging - Search the Catalog
- Perform the same search as above in the Angular catalog

Note that there are 25 hits
Though not visible on the screen, logs show the search as:
((keyword:symphony) || (keyword:concerto) && (keyword:tchaikovsky))

Adding another OR term:

Traditional catalog:

(((symphony || keyword:concerto) || keyword:score) && keyword:tchaikovsky) - 5 hits

Angular catalog:

((keyword:symphony) || (keyword:concerto) || (keyword:score) && (keyword:tchaikovsky)) - 99 hits

Scoping similar searches also yields erroneous results in the Angular catalog. This was described in the following comments on bug 1929072:

https://bugs.launchpad.net/evergreen/+bug/1929072/comments/4
https://bugs.launchpad.net/evergreen/+bug/1929072/comments/5
https://bugs.launchpad.net/evergreen/+bug/1929072/comments/9

1929072 was resolved in bug 1746800, I've moved Shannon Dineen's and Jennifer Pringle's reports here.

Also relevant is bug 1152863 - Support for traditional boolean operators.

Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

I think we're seeing this in the angular catalogue in 3.9.1. When AND and OR is used in a search the search results don't scope to the selected library but show results from the entire consortium instead.

Changed in evergreen:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.