Bug 10095 - There should be a way to suppress a category of authorised values
Summary: There should be a way to suppress a category of authorised values
Status: CLOSED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: System Administration (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-22 15:10 UTC by Mathieu Saby
Modified: 2016-05-14 20:46 UTC (History)
4 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 Mathieu Saby 2013-04-22 15:10:40 UTC
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
Comment 1 Jonathan Druart 2013-05-28 13:46:19 UTC
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?
Comment 2 Mathieu Saby 2013-05-28 13:55:51 UTC
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
Comment 3 Mathieu Saby 2013-05-28 13:58:14 UTC
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
Comment 4 Mathieu Saby 2013-05-28 13:58:35 UTC
I mean highlighted...
Comment 5 Jonathan Druart 2013-05-28 14:19:05 UTC
To remove a category, you should remove all authorised values created for this category.

DEPARTMENT and TERM are introduced by bug 8215
Comment 6 Mathieu Saby 2013-05-28 14:36:36 UTC
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
Comment 7 Katrin Fischer 2013-06-06 06:03:44 UTC
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.
Comment 8 Mathieu Saby 2013-06-09 13:29:58 UTC
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