Strange behavior for subject display in staff catalog

Bug #1770454 reported by Kathy Lussier
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Medium
Unassigned

Bug Description

Evergreen version: 3.1

We're seeing some strange behavior with subject display in the catalog record when logged into the staff client.

When first retrieving the record, the subject headings display as described in bug 1770453 with highlighting applied to the search terms, if present. When refreshing the page, the subject headings revert back to the pre-display-fields way of displaying them with the full subject heading, but search highlighting turned off.

See the screencast at

https://drive.google.com/file/d/1LyCFQYywt_gCl5xHXPUOphePnQHf0GWY/view

Revision history for this message
Mike Rylander (mrylander) wrote :

Kathy, this is happening because when you refresh the whole page, the inner iframe is built with a different source URL -- one that points directly to the record without any search information. If you look at the hit count, you'll see that it shows "1 of 1" at the bottom of the record summary. Because there is no search, but just a retrieval of the record, the record is rendered using the "pull data from MARC" mechanism rather than using the record's display field data. While we could probably use the display field data here, it's not, strictly speaking, a "search result" anymore, but more like a "deep link to a specific bib".

Revision history for this message
Mike Rylander (mrylander) wrote :

And, to be more direct about the cause, a refresh of the outer frame loses the inner frame's search context entirely. This is simply a side effect of the use of iframes for the catalog. (Here's to hoping the community as a whole embraces a "angular-first web app" approach to a future OPAC rewrite!)

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Kathy Lussier (klussier) wrote :

+1 to using display field data in these instances. These fields really need to display the exact some data, whether the record retrieval is the result of a search or not. Is there any benefit to having two different ways to display these fields?

Another issue here is that, as reported in bug 1770453, the subject headings using display fields isn't displaying all of the subfields that it should. However we proceed, those need to be fixed up so that the full heading can display.

Revision history for this message
Terran McCanna (tmccanna) wrote :

Marking this Won't Fix as it was specific to the iframe which has been deprecated.

Changed in evergreen:
status: Confirmed → Won't Fix
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.