| Summary: | "Scheduled for automatic renewal" text displays even when not renewable | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Mirjam Vantieghem <mirjam.vantieghem> |
| Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | trivial | ||
| Priority: | P5 - low | CC: | bdaeuber, dcook, gmcharlt, jessica.andersson, kebliss, kkrueger, kyle, martin.renvoize, mary.woodward, mkstephens, mteal, nick, nwendt, pedro.amorim |
| Version: | 23.11 | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20575 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41518 |
||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Bug Depends on: | 25393 | ||
| Bug Blocks: | |||
|
Description
Mirjam Vantieghem
2024-02-07 15:38:49 UTC
I think this was a choice on 25393 - to mark that a checkout had auto-renewals enabled. (In reply to Mirjam Vantieghem from comment #0) > Since 23.11, on the checkouts page both in Staff client and OPAC, when a > certain item is not renewable, e.g. because it is on hold or max renewals > reached, the text "Scheduled for automatic renewal" still appears which is > confusing. > > E.g. In the OPAC it says "Not renewable (on hold)", but right below it, it > still says "This item is scheduled for auto renewal." In the Staff client it > shows "On hold" and below that "(Scheduled for automatic renewal)". Are you able to provide a detailed test plan to reproduce this? Also current values of "No renewal before", "No automatic renewal before" and "Automatic renewal" in the circulation rules. It may be that there is no bug here, as both messages being shown is an expected use case, I believe. It may be that in the situation you describe, a manual renewal is not possible "right now" (because its on hold) but an automatic renewal **attempt** is still going to happen for that specific checkout when the time for the cron to run comes, hence the message. It may be the case that the hold is cancelled in the meantime, and in such event the automatic renewal would succeed, hopefully. I agree that the text being presented may be confusing, but this was done for transparency reasons, i.e. provide full information of what is going on. The alternative would be to just show "Not renewable (on hold)" and nothing else, but an auto renewal attempt would still take place for that checkout eventually. I'm not saying there is no bug here, but the above is the reasoning behind the implementation decisions. In a practical scenario, the desirable behavior would be for the message about automatic renewal to be informed by how many renewals are remaining, so that when there are no renewals remaining, the message about scheduled automatic renewal would disappear. Here's another idea that might be simpler but have the same effect. What if the text "Scheduled for automatic renewal" was changed to something like "Automatic renewal enabled"? Would this still communicate the same information (auto-renew is turned on) without implying that an actual renewal is scheduled and pending? Just changing the text means that the two messages would continue to appear together when no renewals were remaining. If it is still too confusing to see an auto-renew message when no renewals are remaining, then it would be ideal for the visibility of the auto-renew message to reference the renewal status so that it would not appear when an item is not renewable. I think removing the second line of text "This item is scheduled for automatic renewal" would be less confusing for patrons. In 24.11, the text "scheduled for automatic renewal" appears for all patrons. Even for patrons who has opted out this function. The text appears in both opac and staff client. I also just noticed today that the message "Scheduled for automatic renewal" appears for patrons opted out of automatic renewals. (In reply to Kristi Krueger from comment #7) > I also just noticed today that the message "Scheduled for automatic renewal" > appears for patrons opted out of automatic renewals. Noticing the same thing as well in 24.11. This is an issue for us as well - it's confusing for staff. It looks like the original intent of this bug was written up regarding a patron signed up for automatic renewal, but the "Scheduled for automatic renewal" shows up for items checked out are not eligible for renewal. Should the issue that "Scheduled for automatic renewal" shows up for patrons who have opted out of automatic renewals be a separate bug? It doesn't seem like this part would be as complicated to address as the original issue. (In reply to mteal from comment #10) > It looks like the original intent of this bug was written up regarding a > patron signed up for automatic renewal, but the "Scheduled for automatic > renewal" shows up for items checked out are not eligible for renewal. > Should the issue that "Scheduled for automatic renewal" shows up for patrons > who have opted out of automatic renewals be a separate bug? It doesn't seem > like this part would be as complicated to address as the original issue. That's a good question... I think you're probably right. Looking at the OP... yeah I suppose that is a different issue. We do have the output of CanBookBeRenewed at hand in svc/checkouts, but we'd need to interrogate it and do lots of if/elsif/elses I think. It would probably be a bit of work but it might be worthwhile to do... -- Looking at "svc/checkouts", it looks like it just reports "auto_renew" enabled if auto_renew is enabled for the checkout. That endpoint should probably also show borrowers.autorenew_checkouts, and then only show "Scheduled for automatic renewal" in koha-tmpl/intranet-tmpl/prog/js/checkouts.js if both oObj.auto_renew and oObj.patron_auto_renew are true. Since I think ./misc/cronjobs/automatic_renewals.pl only selects checkouts where both the item has auto_renew and the borrower has autorenew_checkouts... Looking at the original description again... I think as Nick said in Comment 1... maybe it does make sense saying it's scheduled for automatic renewal even if it's not renewable. Because the automatic renewal script will still check it. And if they get notices they might get a notice saying that the automatic renewal has failed. I think in this case "Scheduled for automatic renewal" just means that it's flagged as an automatic renewal item. Hmm... I could see both sides of that. *** Bug 40775 has been marked as a duplicate of this bug. *** I have opened bug 41518 to only show "Scheduled for automatic renewal" if issue.auto_renew and borrowers.autorenew_checkouts are both set, since that's the criteria required for automatic_renewals.pl to consider the issues for automatic renewal. (In reply to David Cook from comment #14) > I have opened bug 41518 to only show "Scheduled for automatic renewal" if > issue.auto_renew and borrowers.autorenew_checkouts are both set, since > that's the criteria required for automatic_renewals.pl to consider the > issues for automatic renewal. If folk could try out that patch, I'd be grateful. Thanks! (In reply to David Cook from comment #12) > Looking at the original description again... I think as Nick said in Comment > 1... maybe it does make sense saying it's scheduled for automatic renewal > even if it's not renewable. Because the automatic renewal script will still > check it. And if they get notices they might get a notice saying that the > automatic renewal has failed. > > I think in this case "Scheduled for automatic renewal" just means that it's > flagged as an automatic renewal item. > > Hmm... I could see both sides of that. As I said in Bug 40775, ideally it could be context aware. Regardless of whether or not something is flagged for autorenewal, a patron wants to know if it is going to renew. I think everyone appreciates that might change, but knowing in the present moment is helpful. We actually tried toggling that column off to prevent confusion, but a number of patrons said that they checked the column to see what items they should read or watch first so they could get the items back for the person waiting; we want to encourage that sort of behavior. I think it's especially frustrating to show that if the autorenewal limit has been reached. |