web client: record summary displays 050

Bug #1739284 reported by Elaine Hardy
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
3.0
Fix Released
Medium
Unassigned

Bug Description

In the record summary, the call umber display is the 050 -- the Library of Congress Classification call number. As Dewey libraries, we need the 082, Dewey Decimal Classification number, to display as it does in the XUL client

Elaine Hardy (ehardy)
tags: added: webstaffclient
Revision history for this message
Mary Llewellyn (mllewell) wrote :

We are a mix of Dewey and LC libraries. In the XUL staff client, the bib call# was from tag 050 or 082, depending on the library settings. We'd like to see that behavior in the web client.

Changed in evergreen:
status: New → Confirmed
Changed in evergreen:
assignee: nobody → Jason Stephenson (jstephenson)
milestone: none → 3.1.3
Revision history for this message
Jason Stephenson (jstephenson) wrote :

Mentioned this in IRC and that I had traced the cause in the Chromium debugger, and Bill Erickson made a branch to fix it: user/berick/lp1739284-bib-summary-cn-classification.

I tested the branch, and it works, so I've added my signoff and pushed that to the working repository:
user/dyrcona/lp1739284-bib-summary-cn-classification-signoff.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dyrcona/lp1739284-bib-summary-cn-classification-signoff

Thanks, Bill!

tags: added: pullrequest signedoff
Changed in evergreen:
assignee: Jason Stephenson (jstephenson) → nobody
importance: Undecided → Medium
Revision history for this message
Elaine Hardy (ehardy) wrote :

Thanks! I will ask for this to be added to our test server so that we can take a look.

Revision history for this message
Elaine Hardy (ehardy) wrote :

I am seeing the 082 when present in the bib record. If the record has an 092 but no 082, that is displaying. If it has neither an 082 or 092, the there is no bib call number in the summary. This is the same behavior we see in the XUL client. Thanks!

Mary may want to check to see that it displays correctly for her libs.

Revision history for this message
Millissa (millissam) wrote :

We also would like the 082/092 to display. Our library is displaying the 050 even when there is an 082/092. I have attached a screenshot of the display and the MARC record.

Revision history for this message
Kathy Lussier (klussier) wrote :

If anyone would like access to a Sandbox to test Jason's fix as Elaine did, you can do so by filling out the request form at https://docs.google.com/forms/d/e/1FAIpQLSdzcYLSXYxsHE8RJIC32r8BNGpoON-sXneV8cIqmZHNEhM5fA/viewform.

This would be extremely helpful for moving the fix into Evergreen sooner rather than later.

Changed in evergreen:
milestone: 3.1.3 → 3.1.4
Changed in evergreen:
milestone: 3.1.4 → 3.1.5
Revision history for this message
Jason Stephenson (jstephenson) wrote :

I'm inclined to push this before the 3.1.5 and 3.0.11 releases if no one objects. I was just looking at it again, and the fix is still relevant.

Revision history for this message
Kathy Lussier (klussier) wrote :

+1 - no objections from me.

Revision history for this message
Janet Schrader (jschrader) wrote :

+1 - libraries have been waiting for this.

Revision history for this message
Jason Stephenson (jstephenson) wrote :

Pushed to master, rel_3_1, and rel_3_0 for the next releases!
Thanks, Bill, Elaine, and everyone else!

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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