Web client - random sort order of spine labels in preview & printed out
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
High
|
Adam Bowling | ||
3.1 |
Confirmed
|
High
|
Unassigned | ||
3.2 |
Confirmed
|
High
|
Unassigned |
Bug Description
EG3.1
when we scan barcodes into Item Status, then chose “Print Labels” the labels do not come out in the order they were scanned in, instead they are in a random order.
We’ve tried putting the items into a copy bucket first, and printing from there but the results are the same.
Steps to reproduce
Scan barcodes into item status
CONC4000036
CONC4100053
CONC4100054
CONC4100055
CONC4100056
CONC61000236
CONC61000237
CONC61000238
items are listed in reverse order -> check box to select all -> Actions -> Print Labels
Label preview / print in this order
CONC61000237
CONC4100056
CONC61000236
CONC61000238
CONC4100055
CONC4100054
CONC4100053
CONC4000036
The random order creates a lot of extra work as we do not expect our processors to know which Dewey number applies to a particular book or item, instead for efficiency we have them apply the labels in the order they are on the cart.
Desired behaviour -> Spine labels should print in the order or reverse order they are scanned
tags: | added: cataloging printing sorting |
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
importance: | Wishlist → High |
tags: | added: spinelabels |
Changed in evergreen: | |
assignee: | nobody → Adam Bowling (abowling) |
Changed in evergreen: | |
milestone: | none → 3.3.4 |
Changed in evergreen: | |
milestone: | 3.3.4 → 3.3.5 |
** Note - the random sort order does not appear as bad with upstream test data. I wonder if the items are being sorted by database id or something?