Bug 31642 - Additional contents: Allow free text in location field for html blocks
Summary: Additional contents: Allow free text in location field for html blocks
Status: ASSIGNED
Alias: None
Product: Koha
Classification: Unclassified
Component: Tools (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Marcel de Rooy
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-28 12:12 UTC by Marcel de Rooy
Modified: 2022-09-28 12:35 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcel de Rooy 2022-09-28 12:12:39 UTC
I ran into this limitation on e.g. bug 31503. I want to add locations that match authorised values for category CONSENT_TYPE. But Koha only allows a selected set of locations for html blocks.

If we could allow picking a field from the combo or typing free text, we provide more flexibility in the use of this feature.

Obviously this triggers a development discussion on field names. We have category, location and code. And their use becomes a bit unclear.
Category is the most clear one. Although html and pages are quite similar.
Location is opac or staff etc. for news and pages. But is used as a kind of block name for html_customizations.
Code is used to group the records for default and translated languages for an item in all categories. The name is rather obscure.
While describing this, bug 31383 comes to mind again..