Web Client: Org Unit printing on Spine and Pocket labels

Bug #1726568 reported by Lynn Floyd
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
High
Unassigned
3.1
Fix Released
High
Unassigned

Bug Description

I was testing on on Webby, and discovered that the Spine and Pocket labels only printed the org unit ID, not the shortname or name.

copy['location.owning_lib']
copy['circ_lib']

This prints just the ID.

If

copy['location.owning_lib.shortname']
copy['circ_lib.shortname']

or

copy['location.owning_lib.name']
copy['circ_lib.name']

could be added it would be more beneficial to all.

Revision history for this message
Lynn Floyd (lfloyd) wrote :
Changed in evergreen:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Elaine Hardy (ehardy) wrote :

This is a potential show stopper for those PINES libraries with multiple branches that also print pocket labels with org unit name. The current workaround is to type the shortname into the template or label, either at the time of printing or having multiple templates for each branch. Since cataloging staff print out multiple labels for multiple branches at one time -- generally based on what they have cataloged in a day, this is not a workable solution since different branches would be mixed in one print run.

Revision history for this message
Lynn Floyd (lfloyd) wrote :

I have found a work around for now.
It will take some coding on the library's end.

Basically you take the id and translate it with in the pocket label. Here is the code for WEBBY. I using this with just my library's Ids. Just make sure all the coding is on one line.

<span ng-switch="copy.circ_lib"><span ng-switch-when="4">BR1</span><span ng-switch-when="5">BR2</span><span ng-switch-when="6">BR3</span><span ng-switch-when="7">BR4</span><span ng-switch-when="8">SL1</span><span ng-switch-when="9">BM1</span><span ng-switch-default>CONS</span></span>

Kathy Lussier (klussier)
tags: added: spinelabels
Revision history for this message
Terran McCanna (tmccanna) wrote :

Bumping this up to High - Lynn's workaround is handy, but we can't reasonably expect all of the library systems to implement that workaround.

Changed in evergreen:
importance: Medium → High
Revision history for this message
Lynn Floyd (lfloyd) wrote :
Revision history for this message
Terran McCanna (tmccanna) wrote :

Ah, I KNEW I had seen that bug! I'll mark my new one as a duplicate.

tags: added: printing webstaffblocker
Revision history for this message
Terran McCanna (tmccanna) wrote :

To reiterate from other bug about Owning Library needed:

callnumber.owning_library only prints the owning library's numeric ID and call_number.owning_lib.shortname prints nothing.

Galen Charlton (gmc)
Changed in evergreen:
milestone: none → 3.2.2
assignee: nobody → Galen Charlton (gmc)
Revision history for this message
Galen Charlton (gmc) wrote :

A patch is available at the tip of the user/gmcharlt/lp1726568_label_owning_lib branch in the working repository:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gmcharlt/lp1726568_label_owning_lib

tags: added: pullrequest
Changed in evergreen:
assignee: Galen Charlton (gmc) → nobody
Revision history for this message
Terran McCanna (tmccanna) wrote :

Works like a charm!

I have tested this code and consent to signing off on it with my name, Terran McCanna, and my email address, <email address hidden>.

tags: added: signedoff
Changed in evergreen:
milestone: 3.2.2 → 3.2.3
Changed in evergreen:
milestone: 3.2.3 → 3.3-beta1
status: Confirmed → New
Revision history for this message
Galen Charlton (gmc) wrote :

Thanks for testing, Terran! I've gone ahead and pushed this to master, rel_3_2, and rel_3_1.

Changed in evergreen:
milestone: 3.3-beta1 → 3.2.4
status: New → Confirmed
no longer affects: evergreen/3.2
Changed in evergreen:
assignee: nobody → Galen Charlton (gmc)
status: Confirmed → Fix Committed
assignee: Galen Charlton (gmc) → nobody
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.