Angular catalog jumps to record on last page of search results

Bug #1954548 reported by Dan Guarracino
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
New
Undecided
Unassigned

Bug Description

This is on Evergreen 3.6.5.

When the Angular catalog has only one result on the final page of a catalog search, it will jump straight to the bib record that would have been on the final page of results.

From the bib record, a user is unable to press "Back to Results." Evergreen will continue to redirect to the single bib record.

To replicate:
-Have the Library Setting "Jump to details on 1 hit (staff client)" set to True
-(Assuming you have your preferences set to display ten search results)
-Perform a search that has 11, 21, 31, etc. results
-Click through to the last page of results or select the last page of results directly
-Note that the catalog jumps directly to the bib record. Also note that you selecting "Back to Results" will always cause the last bib record in the results to load, even after pressing "Start," "Previous," etc.

-An easier way to replicate this is to perform any Angular catalog search, note the number of results, and then to change the Search Results Per Page in Catalog Preferences. For example, I tried a search that returned 16 results and was able to replicate this bug with my Search Results Per Page set to either 5 or 15.

I think this may be related to 1912852.

Revision history for this message
Carol Witt (carolwitt) wrote :

This appears to be the same thing that we're experiencing on 3.7.2 when we search the Angular staff catalogue and retrieve only one result. The browser's back button also causes the single record to reload, not return to the search screen.

Revision history for this message
Shannon Dineen (sdineen) wrote :

Confirming this is still an issue on 3.9., albeit not often reported.

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.