| Summary: | authorised value branches is not visible from dropdown in Admin | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Hugh Rundle <hughr> |
| Component: | Architecture, internals, and plumbing | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED FIXED | QA Contact: | Testopia <testopia> |
| Severity: | minor | ||
| Priority: | P5 - low | CC: | aleisha, jonathan.druart, koha |
| Version: | Main | Keywords: | Academy |
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Hugh Rundle
2017-12-29 02:04:42 UTC
There are 3 authorised value "special categories": branches, itemtypes, cn_source. They are used to link a MARC subfield to a branchcode, itemtype or classification source. They are not proper authorised values (in the sense of the authorised_values table), but are needed to restrict the input. We could add them to the category dropdown list and remove the ability to add value to them (display a friendly message instead to explain the situation). Yep that would be perfect. That way it's clear they already exist, and also that authorised_values is not the place to change them. Something like "[category name] is listed here for information only. To change or add values for [category name] use [appropriate place]. I have just tried: If you try to create a AV category "branches", there is a warning box with "The authorized value category 'branches', 'itemtypes' and 'cn_source' are used internally by Koha and are not valid." That seems enough to me. (In reply to Jonathan Druart from comment #3) > I have just tried: If you try to create a AV category "branches", there is a > warning box with "The authorized value category 'branches', 'itemtypes' and > 'cn_source' are used internally by Koha and are not valid." > > That seems enough to me. I agree, this seems like the message the bug report asks for. Setting to Resolved. |