---- Reported by mcoalwell@nekls.org 2009-05-22 21:29:22 ---- Changing a checked-out item's status to LOST doesn't do anything but change its catalog status to LOST. Formerly, changing a checked-out item's status to LOST would immediately remove it from a patron's checkouts and show it as a lost item with replacement cost under the Fines tab). Some time recently this stopped working correctly. Koha Manual says: "If a replacement charge trigger is specified, the item [is] marked returned, removing it from the patron's account, and a charge is levied (even if it is $0) in accordance with the item replacement cost." ---- Additional Comments From jwagner@ptfs.com 2009-05-26 12:20:12 ---- What version are you at? I just tested on a version 3.01.00.032 system, and lost seems to be functioning correctly there. It removed the item from the user's checkout queue and recorded a fine against it. ---- Additional Comments From rch@liblime.com 2009-05-26 20:24:10 ---- I think this behavior is due to the shortcoming in Koha's treatment of authorised values, wherein it sometimes gives particular authorised values magical powers. In this case, the LOST authorised value '1' should trigger a charge. If you create three authorised values that all reflect some 'lostness', only one of them will trigger the charge. This is an overall weakness of the authorised values implementation; the same problem happens with NOT_LOAN: zero and negative values have special meanings. ---- Additional Comments From mcoalwell@nekls.org 2009-05-26 20:45:34 ---- (In reply to comment #2) > I think this behavior is due to the shortcoming in Koha's treatment of > authorised values, wherein it sometimes gives particular authorised values > magical powers. In this case, the LOST authorised value '1' should trigger a > charge. > If you create three authorised values that all reflect some 'lostness', only > one of them will trigger the charge. > > This is an overall weakness of the authorised values implementation; the same > problem happens with NOT_LOAN: zero and negative values have special meanings. > Yes, the magical power of 1=LOST is precisely what I am missing. Is there a reason the magic has gone from our installation? Is there a way to get the magic back? I understand that only 1=LOST has the Koha magic. But it seems to have disappeared from 3.01.00.014, our version. ---- Additional Comments From smoreland@nekls.org 2009-05-27 17:58:08 ---- Tested this in our newly updated installation today and it works as expected. Feel free to close. ---- Additional Comments From mcoalwell@nekls.org 2009-05-28 02:52:34 ---- Would love to know what happened to the LOST function, and how it magically returned. Glad to have it back. ---- Additional Comments From smoreland@nekls.org 2009-08-04 17:11:51 ---- *** This bug has been marked as a duplicate of http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=2803 *** --- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:08 UTC --- This bug was previously known as _bug_ 3249 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3249 Actual time not defined. Setting to 0.0 CC member jwagner@ptfs.com does not have an account here CC member rch@liblime.com does not have an account here