View in #resource-access on Slack
@Theodor: Does anyone know if “Automatic renewals” has been discussed in the context of circulation? Automatic renewal is when the system automaticallt renews a loan according to the renewals policy if no one is queuing for or has requested that item
@cate: >Does anyone know if “Automatic renewals” has been discussed in the context of circulation? Automatic renewal is when the system automaticallt renews a loan according to the renewals policy if no one is queuing for or has requested that item
@Theodor, I haven’t heard this come up and there is no setting for it in the loan policy as it exists today. Tagging a few others as a heads up and in case they may have heard discussions on the topic: @Sean_Thomas , @ecboettcher
@Theodor: I just heard of it from somewhere and wanted to surface it.
thank you @cate
@charlotte: I think I remember, that Koha also has a possibility to set, how many times an automatically renewal can be performed - so you can’t renew the item forever
http://manual.koha-community.org/3.18/en/patscirc.html
@Carsten_Schwill: Hi @cate, we are hoping for automatic renewals (with a limited count) and have implemented endless renewals (for privileged patrons) in the meantime.
@cate et al. - Just discovered this channel and it seems timely. I don’t recall hearing a discussion on automatic renewals within the RA-SIG, but it’s something we can put on the agenda to discuss. We currently have a setting in the Loan Policy editor to cap the number of allowed renewals. Any reason that a library would want the cap on non-automatic renewals and automatic renewals to be different? The form also contains a option for Unlimited Renewals.
@cate: Hi @Sean_Thomas, it would be great if you could run with this . I think the next step is to just get a feature into UXPROD for automated renewals and get that ranked by the early implementers. Depending on the priority coming from that, we can determine if we should prioritize it for SIG discussion now or later.
@Sean_Thomas: Sure, I’ll get an issue in for this. Thanks.