Cumulative Fixes for Spine Label Display
Bug #1845556 reported by
Adam Bowling
This bug affects 28 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Medium
|
Unassigned | ||
3.7 |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Cumulative fixes for spine label display and editing issues, including:
-Random spine label display order (https:/
-Unique call number editing limitation (https:/
-Incorrect display of long call numbers (https:/
tags: | added: printing spinelabels |
tags: | added: cataloging pullrequest |
tags: | removed: pullrequest |
tags: | added: needsrepatch |
tags: | removed: needsrepatch |
Changed in evergreen: | |
importance: | Undecided → Medium |
tags: | removed: pullrequest |
Changed in evergreen: | |
assignee: | Terran McCanna (tmccanna) → nobody |
tags: |
added: cat-labels needswork removed: needsrepatch spinelabels |
Changed in evergreen: | |
milestone: | 3.next → 3.8.1 |
To post a comment you must log in.
Tested this on PINES servers.
Still getting an error message when I try to open print labels from an item bucket. In Chrome, the error is: Could not create print label export. Firefox has a similarly worded error message.
I can print labels from holdings view and item status
I can now edit a single call number where multiple identical ones exist in a file while in the call number tab of the print labels interface. However, the call numbers no longer have the correct default wrap.
Instead of
FIC
PATTERSO
it is now:
FIC PA
TTERSO
and
FIC
PAT
is now
FIC PAT
The sort/display order also seems to have regressed. If the order in item status is:
31001001055376
31001001320572
31001004671773
31001004671781
Print spine label call number tab displays as:
31001004671781
31001004671773
31001001320572
31001001055376