Summary: | Allow multiple suppression values | ||
---|---|---|---|
Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
Component: | Searching | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | george, sbcornell |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 23406 | ||
Bug Blocks: |
Description
Andrew Fuerste-Henry
2020-07-31 13:16:29 UTC
+1 - good idea +1! In order to make it easier for staff to assign the suppression value, I redefined 1 to "Suppressed in OPAC" but now the line "Suppressed in OPAC" doesn't display on search results or detail pages. More flexibility in defining suppression values, please! Now that we fixed bug 23406, I wonder how we could make this work best. The template check could be something like: - if not empty or 0 - if value >= 1 ? (In reply to Sarah Cornell from comment #2) > +1! > > In order to make it easier for staff to assign the suppression value, I > redefined 1 to "Suppressed in OPAC" but now the line "Suppressed in OPAC" > doesn't display on search results or detail pages. > > More flexibility in defining suppression values, please! This problem was now fixed by bug 23406 - it should show now when using an authorised value that has a code of 1 and any description. |