Generic and Dewey call number normalizers should sort volume numbers numerically, not asciibetically

Bug #1131895 reported by Galen Charlton
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Wishlist
Unassigned

Bug Description

Consider three volumes on the same bib with the following call numbers:

234.54 ABC vol. 1
234.54 ABC vol. 2
234.54 ABC vol. 10

Using the generic normalizer, the label_sortkeys would be

234.54 ABC VOL. 1
234.54 ABC VOL. 2
234.54 ABC VOL. 10

Using the Dewey normalizer, the label_sortkeys would be

234_540000000000000_ABC_VOL__1
234_540000000000000_ABC_VOL__2
234_540000000000000_ABC_VOL__10

In both cases, the effective sort order is:

234.54 ABC vol. 1
234.54 ABC vol. 10
234.54 ABC vol. 2

which is not ideal.

What I think the desired behavior is:

[1] In the case of the Dewey normalizer, groups of numbers that occur after the main classification number should be left-zero-padded.
[2] In the case of the generic normalizer, all numeric tokens should be left-zero-padded.

Evergreen master

Tags: opac sorting
Revision history for this message
Dan Scott (denials) wrote : Re: [Bug 1131895] [NEW] Generic and Dewey call number normalizers should sort volume numbers numerically, not asciibetically

Or call number normalization routines could normalize call numbers
according to their classification definitions, as they're doing now,
and suffixes like "Vol. 10" that don't belong to the call number
proper could either be added as a call number suffix (now that we've
had that option for a year or so on a per-call number basis), or they
could be catalogued as parts (which we have also had for a year or
so).

Revision history for this message
Galen Charlton (gmc) wrote :

The LC normalizer already currently zero-pads numeric elements that occur after the classification part. For obvious reasons of history if nothing else, use of call number suffixes is not universal, and monograph parts are not used by serial units.

Revision history for this message
Galen Charlton (gmc) wrote :

Also, analytic call numbers can have volume designations that are considered part of the main call number, not enumeration designation that could be put in a suffix or hypothetical enumeration field.

Revision history for this message
Ben Shum (bshum) wrote :

I know our catalogers would appreciate not having to recreate everything multi-volume related into parts or use suffixes. So having the label_sortkey add padded 0's to help sort things out sounds pretty good to us.

Changed in evergreen:
status: New → Confirmed
milestone: none → 2.4.0-beta
Ben Shum (bshum)
Changed in evergreen:
milestone: 2.4.0-beta → 2.4.0-rc
Ben Shum (bshum)
Changed in evergreen:
milestone: 2.4.0-rc → 2.5.0-alpha
Dan Wells (dbw2)
Changed in evergreen:
milestone: 2.5.0-m1 → none
Revision history for this message
Chris Sharp (chrissharp123) wrote :

Just noting here that we're still seeing this problem in 2.11.1.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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