Bug 23861 - Add authorised value categories description option
Summary: Add authorised value categories description option
Status: NEW
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: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-21 19:21 UTC by Caroline Cyr La Rose
Modified: 2023-08-08 19:02 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 Caroline Cyr La Rose 2019-10-21 19:21:21 UTC
I really like the way the authorised values page looks now. I think it's much more user friendly with the descriptions and the categories all laid out and not in a drop-down.

Right now, the descriptions for each category are "hardcoded" in the template. Would it be feasible to move those in the DB? That way, when we add new categories, we would be able to add our own description. For example, if I add a category for RDA media type, I would be able to add a description saying it's meant to be used with 337$a.
Comment 1 Pablo AB 2020-04-27 08:10:16 UTC
On bug 17216 it was created the authorised_value_categories table. Probably should be added a new column there for the description of each category, and therefore add to the UI a Modify button to change it.
Comment 2 Katrin Fischer 2020-04-27 11:14:31 UTC
At the moment these messages are in the template and can be translated - if we move to the database they won't tanslate or translations have to be provided separately (and at the moment can only be one language at a time).
I'd say if we move, we could still provide the text for the standard ones in the template, but allow to add your own additionally?
Comment 3 Pablo AB 2020-04-27 18:59:05 UTC
If using templates complicates the issue too much I would move everything to description column. AFAIK it would be similar to what happen with tag names on frameworks, by default hardcoded on the .sql. The user can then change it at wish. IMO is much more important to have the feature of add/modify AV cats descriptions.
I see users creating categories with spaces and diacritics as a workaround, to have more meaningful names. I'm not sure if this could have adverse consequences (Bug 7013). Also related: Bug 20307.
Comment 4 Katrin Fischer 2020-04-27 19:22:48 UTC
I think we could have both. Please note that the descriptions are a very new addition - for a long time they were no instructions. So while I agree it would be nice to have, I don't see the same urgency or error potential I think.
Comment 5 Ray Delahunty 2023-08-04 04:45:30 UTC
I am passionate about documenting as I go, so it would be great to be able to add descptions to AVs. We have created dozens, for 'subject funds' below funds, and lots of various fiscal periods for use in report date range selectors, and others besides. Documenting these briefly would help colleagues understand where/how/why these are used.
Comment 6 Joseph Alway 2023-08-08 18:31:18 UTC
It would be nice for this to be a thing. I'm using a custom Authorized Value for use with one of our reports. Not being able to enter a description for the Authorized Value Category is just a little annoying.

https://wiki.koha-community.org/wiki/SQL_Reports_Library#Suggestion_Report_with_selection_by_Status
Comment 7 Joseph Alway 2023-08-08 19:02:19 UTC
(In reply to Katrin Fischer from comment #2)
> At the moment these messages are in the template and can be translated - if
> we move to the database they won't tanslate or translations have to be
> provided separately (and at the moment can only be one language at a time).
> I'd say if we move, we could still provide the text for the standard ones in
> the template, but allow to add your own additionally?

This sounds reasonable to me. What seems like the most likely scenario is that someone will be adding/editing custom authorized value categories. Which is where I found that I couldn't edit the description or even provide one when I added the category.