https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12063
--- Comment #17 from Koha Team Lyon 3 <[email protected]> --- Hi Katrin, Hi Marcel, >From what I have understood, but I may be wrong, patrons can put an expirationdate to say that they're not interested in this reservation if it's not available for them after this date. Here, we change the date after the item was check-in, so available for the patron. In this case, the first information isn't useful anymore. I haven't tested if there's a change of behaviour if the patron isn't the first in the holding list, but I don't think so. >From a functional point of view, I don't think that's an issue to overwrite expirationdate. But, It can be perhaps a problem if the library want to make statistics to know an average of the time between the expirationdate and the waitingdate... or some tricky things we sometimes wants to know. And, I can understand that it may be not in the "coding line" and that's a dirty way of doing... you can say that better than me. Sonia -- You are receiving this mail because: You are the assignee 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/
