Hi all,
I found a scenario where it seems overdues were't going out for a checkout/issue that had a branch that no longer exists in Koha. The item itself belonged to a new branch, and the branch used to check it out had been deleted. There's no referential integrity between the issue table and the branches table, so nothing would've happened there automatically. Looking at the code for overdue notices (which was terrifyingly long and in need of a refactor), it seemed like maybe it would've been fine that the issue didn't have an existing branch (because the overdue rules table entries still existed for the old branch), but. in the end it wasn't worth the time chasing down this edge case. I thought I'd share the experience here though just in case someone else had experienced this issue or was scrambling to explain the same behaviour. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595
_______________________________________________ Koha-devel mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
