http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14370
Nicole C. Engard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #8 from Nicole C. Engard <[email protected]> --- (In reply to Katrin Fischer from comment #7) > Hi Joy and Marcel, > > still pondering this too - I think for me "Restricted" means that there are > 'limits' to its use - like only allowing it to be used on-site. While I > would use a 'notforloan' if I didn't want a checkout. I am still wondering > what would make the most sense here. > > Suggestion: > - Block positive values from 'normal' checkout (can add exception for > on-site later) > - Don't block negative values from checkout > - Always allow holds? (in difference from notforloan?) I'm in agreement with a lot of you here. I always taught libraries not to use the restricted access values because it was so very very unclear what it did. That said, having it only block access with 1 value seems contrary to other authorized values. I like Katrin's suggestions: - Block positive values from checkout - Don't block negative values from checkout As for holds though - I'm really not sure. Basically it sounds to like restricted is no different from not for loan in this scenario. Before this I thought restricted just put a label on items that were restricted and did nothing - while that too seems strange, it at least was different from not for loan. I don't now if I helped at all here ... -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
