https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26498
--- Comment #2 from Fiona Borthwick <[email protected]> --- (In reply to Katrin Fischer from comment #1) > Can you explain the use case a bit more? > > The expiration date is how long the hold will be "valid" in the system > before it's filled (then it's pickup date...). So we would limit the holds > to be only valid for x by default... And the users would see he date in > their patron accounts? Hi Katrin, Holds can live on the system forever without being filled and we have customers who want to manage this. A member of staff or a user can manually enter an expiry date when placing the hold but if they do not, then the expiry date is blank which means that the hold never expires. We have customers who ask us to assign expiry dates to their holds. Then if they are not filled in that time period, the hold will expire. So yes what you say here "we would limit the holds to be only valid for x by default..." is what we would like. I suppose it would be useful or the patrons to see this information in their accounts. Hope this makes sense! -- 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] https://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/
