There is no way to suppress an category of authorised values, even if no values are defined for it. There should be a way to do that. M. Saby
I think it is not a bug. There are several mandatory categories (Asort1 Asort2 Bsort1 Bsort2 SUGGEST DAMAGED LOST REPORT_GROUP REPORT_SUBGROUP DEPARTMENT TERM : They are hardcoded into admin/authorised_values.pl). Which categories are you talking about?
Yes, there are hard coded categories. But you can also define your own categories. For example, we defined a category for the type of alphabet used in record, for the type of diploma used in patron attributes, for the "level" of the documents (target audience), etc. Ex : If next year the diploma codes are no more stored in our patron records, the category we created (mapped with codes from our LDAP) will become useless... M. Saby
The mandatory categories you cite could be highted in Koha interface. We don't have DEPARTMENT and TERM in Rennes 2. What is used for? M. Saby
I mean highlighted...
To remove a category, you should remove all authorised values created for this category. DEPARTMENT and TERM are introduced by bug 8215
Ok, when I tested some months ago to suppress all values of a category, I believe the void category itself remained in Koha. Maybe I did it the wrong way... M. Saby
Hi Mathieu, the categories alone don't exist in Koha - they only come into existance once a value for the authorized value exists. If you take a look at the table you will see what I mean. So if a category is not hardcoded, it will vanish once the last value was deleted.
OK, I understand my mistake ; I suppressed all the values for my "OUI/NON" category, and when I finished, I was redirected to a page "authorised_values.pl?searchfield=OUI/NON&offset=0" which displayed this message : 'There are no authorized values defined for OUI/NON' But after that, when I went to the home page of Authorized Values module, of course, as you said, I did not see any trace of the former "OUI/NON" category. M. Saby