Bug 18711 - No longer possible have a blank value for Classification Sources in the Administration Module
Summary: No longer possible have a blank value for Classification Sources in the Admin...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: System Administration (show other bugs)
Version: 16.11
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-31 21:48 UTC by Karen
Modified: 2023-09-15 21:45 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karen 2017-05-31 21:48:33 UTC
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.
Comment 1 Josef Moravec 2017-06-05 11:02:51 UTC
(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.
Comment 2 J Schmidt 2017-07-07 18:25:04 UTC
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.
Comment 3 Katrin Fischer 2020-01-11 21:54:17 UTC
This sounds similar as bug 13246.
Comment 4 Katrin Fischer 2023-09-15 21:45:31 UTC
We should allow to leave  DefaultClassificationSource empty, so we can set the field to mandatory and force libraries to make a conscious choice.