call number label class not able to be set in 2.0, default is ignored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Dan Scott |
Bug Description
Evergreen 2.0 added a label_class column to the call number table with one major purpose being the generation of correct sort keys. You can also specify a default label class as an org unit setting. However:
1) There are no interface elements for setting the label class of an individual call number.
2) The default setting is not consulted (that is, not set in the call number table) when new call numbers are created.
These two facts together greatly reduce the utility of this very valuable feature, as all new call numbers end up in the 'Generic' class.
While #1 has been addressed in 2.1+, there is still work to be done in setting this class on import. Also, which interface parts (if any) make it back to 2.0 is subject to debate.
As a more reasonable default, I suggest something similar to the attached patch be applied to master, 2.1, and 2.0. Rather than always defaulting to '1' (Generic), it defaults to the 'cat.default_
Thoughts?
Thanks,
Dan
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
I think it looks good! I intended to do something like this as a next step ages ago, but my lack of focus meant that the next step never happened. I think you've nailed it. If you push it to a working branch, then I'll gladly sign off on it.