http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14170
--- Comment #2 from Christopher Brannon <[email protected]> --- I'm wondering if this ticket should address a more pressing issue. It is really perplexing as to why we are tracking the status of an item in 4 or more tables. I can find the status of an item in the items, reserves, branchtransfers and issues tables, if not others. This is extremely inefficient, and possibly the reason statuses get jumbled in Koha, I'm finding, on a regular basis. Why not have an itemstatus table that keeps track of an item if it is not available? The reserves table should really only keep track of who is next in the reserves. On loan, waiting, transfers, and even damaged, lost, withdrawn, etc could all be tracked in one table. You could even put the status of on cart for recently returned items in this table. This is an area of Koha that could really use some attention and streamlining, in my opinion. If I am wrong, that is fine. I just think it should be discussed more. It just seems like it could be a lot easier to troubleshoot and eliminate dual statuses. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ 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/
