http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7001
Katrin Fischer <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #28 from Katrin Fischer <[email protected]> 2012-01-11 05:20:33 UTC --- >* I wonder about the utility of "New Notice" at all - if we can only define >notices within the codes in the default data (is that true?) then copying them >from the defaults is probably the easiest way to go. Or, make the code field a >drop down to select the type of notice so one doesn't mess up and put a quick >slip under the cataloging module (like I did in my testing because I wasn't >paying attention). Hi Liz, defining your own notices can make sense. One example is overdues where you tell the notice triggers which notices to use. It's not relying on a special code there. And there are some other places where it only relies on the correct module (acq and serials). -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug. 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/
