Summary: | Store biblio OPAC visibility in biblio table | ||
---|---|---|---|
Product: | Koha | Reporter: | David Cook <dcook> |
Component: | OPAC | Assignee: | Owen Leonard <oleonard> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | ||
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: |
Description
David Cook
2022-10-12 23:14:55 UTC
In theory, every bib record change would trigger an evaluation of whether or not the bib is "suppressed", and every item change should trigger an evaluation of whether or not that item is "hidden". There would also need to be an evaluation of whether or not the bib is suppressed if all its items are hidden. We'd also need a maintenance script then, because if items make a record hidden can be changed on the fly. It would make things a bit less flexible for libraries again... having to ask someone to run jobs server side if often not an easy thing for them. Maybe this makes more sense for OpacSuppression only as a first step? (In reply to Katrin Fischer from comment #2) > We'd also need a maintenance script then, because if items make a record > hidden can be changed on the fly. It would make things a bit less flexible > for libraries again... having to ask someone to run jobs server side if > often not an easy thing for them. Flexibility is what got us into this mess in the first place... > Maybe this makes more sense for OpacSuppression only as a first step? Sure. |