https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36996 --- Comment #4 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #3)
(In reply to David Cook from comment #2) I think this is a different thing. They don't want to hide the items, they want a simplified version of availability and Nick just meant "a yaml preference".
Exactly, I just meant using the same structure for defining the rules
Koha uses several fields and attributes to determine availability (damaged, restricted, notforloan...) and not all systems are happy to deal with that.
But I wonder about the functionality that was built into the z39.50 responder - didn't that have a similar goal?
This extends that functionality - currently it checks the various statuses - if none are found then the item is available. This adds a new check, based on a system preference, that will add a status of 'SYSPREF' to the list If no statuses are found, then we pass a single 'AVAILABLE' status If other statuses are found, they can either be sent as a single field, with all statuses concatenated, or multiple fields, one per status -- You are receiving this mail because: You are watching all bug changes.