In Koha 3.22 it was possible to enter a blank value for Classification Sources in the Administration Module. In 16.11 it is no longer possible to enter a blank value. The expected behavior is that it would still be possible to enter a blank value. The SWITCH Library Consortium has requested the ability to keep the ability to add a blank value field.
(In reply to Karen from comment #0) > In Koha 3.22 it was possible to enter a blank value for Classification > Sources in the Administration Module. > > In 16.11 it is no longer possible to enter a blank value. The expected > behavior is that it would still be possible to enter a blank value. The > SWITCH Library Consortium has requested the ability to keep the ability to > add a blank value field. If you wan't to "use" blank value, why not just ommit the field with classification source? If no classification is used, then it makes better sense to me to not add any classification rule to the record.
We are on 16.11. We are hoping to always have a blank option available for the authorized values LOC, CCODE and Classification....We are in a consortium and we have libraries using different option between themselves and also within their own branch.... The other thing is what the equivalent 952$ subfield outputs as a MARC or XML file when it's a blank because discovery vendors get mapped information for their displays... Often a 952$subfield with a blank might be a zero but a dash wouldn't be something currently mapped.
This sounds similar as bug 13246.
We should allow to leave DefaultClassificationSource empty, so we can set the field to mandatory and force libraries to make a conscious choice.