Comment 24 for bug 1315552

Kathy, to address your concern, I just want to emphasize that the fix doesn't change the current sort order at all, so it doesn't break any of that intended behavior. It continues to display first the most available copy as it always has since that feature was implemented. From a usage perspective, it only removes the duplicates mentioned in the bug.

To illustrate, if we use letters to represent call numbers and numbers for copy rank, we currently get the following display in cases with mismatched owning/circ libs:

Q1
Q1
Q4
Q4
F2
F2
F5
F5
H3
H3

The duplicates listed above are not real copies, just display problems. The new codes removes the dupes, keeping the same order:

Q1
Q4
F2
F5
H3

An idealized future would remove call number grouping to give us:

Q1
F2
H3
Q4
F5

The current code, both before and after the fix, orders by copy "rank" (the complex set of rules from the branch linked) but groups by call number. This means the best copy (the "1") is still always first, and in this case, the Qs come before the Fs come before the Hs. The more nuanced issue is how to handle Q4 and F5 (to shove them further down), but it is not (AFAICT) something the original code did.