---- Reported by nengard@gmail.com 2010-02-25 14:08:22 ---- It would be nice to define what modules your authorized value is created for - the list of authorized values is getting a bit long and it would be great if when on the patron record you only see authorized values specific to patrons and when on cataloging you only see value categories specific to cataloging ... etc etc. --- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:25 UTC --- This bug was previously known as _bug_ 4264 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4264 Actual time not defined. Setting to 0.0
"large" enhancement to write, because it will require a new table for "authorized values headers". Could be useful though, but not a high priority
Hi Nicole, is this still valid? Where you thinking of something like the groups and sub groups we have for reports, but for authorized values?
Maybe this could work similar to the groups/subgroups on reports? We have a table for categories now, so the development would no longer be that big.
This might still be a pretty handy optional feature. For example we have several Authorised value categories that belong to the ERM module now and this is repeatedly stated in the description, but it would be so much nicer to have a separate sortable/searchable column for these.
Yes, it would be nice to organize the authorized value categories in some way. It may make it easier to find things. Right now, one just has to know where it is used if the title or description is not obvious.