| Summary: | Clarify wording when deleting a bib attached to orders | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
| Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | normal | ||
| Priority: | P5 - low | CC: | m.de.rooy, severine.queune |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| 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: | |||
|
Description
Andrew Fuerste-Henry
2020-01-17 14:57:03 UTC
(In reply to Andrew Fuerste-Henry from comment #0) > From detail.pl, when attempting to delete a bib that is connected to any > uncanceled orders in acquisitions, we receive the message: "Warning: This > record is used in X order(s). Deleting it could cause serious issues on > acquisition module. Are you sure you want to delete this record?" > > This message would be more helpful if it distinguished between open and > closed orders. Deleting a bib connected to an open order will cause serious > issues. Deleting a bib connected to closed orders will not. > > I see three possible fixes: > - Change the message to specify "This record is used in X open order(s) and > Y closed order(s). Deleting a record used in open orders could cause serious > issues ..." > - Change the message to only appear if the bib is used in orders connected > to an active budget and give a count of only orders connected to an active > budget. > - Complete bug 16872 to entirely block the deletion of bibs in open orders, > then remove this warning. If we're not allowing the deletion of bibs from > open orders, then it's not a big deal. I am ok with the first and last suggestion, but in doubt about the 'only in active budgets'. Sometimes libraries may mark a budget form last year inactive and change the budget on receiving the item. I think differentiating between open and closed would work well enough. (In reply to Katrin Fischer from comment #1) > (In reply to Andrew Fuerste-Henry from comment #0) > > From detail.pl, when attempting to delete a bib that is connected to any > > uncanceled orders in acquisitions, we receive the message: "Warning: This > > record is used in X order(s). Deleting it could cause serious issues on > > acquisition module. Are you sure you want to delete this record?" > > > > This message would be more helpful if it distinguished between open and > > closed orders. Deleting a bib connected to an open order will cause serious > > issues. Deleting a bib connected to closed orders will not. > > > > I see three possible fixes: > > - Change the message to specify "This record is used in X open order(s) and > > Y closed order(s). Deleting a record used in open orders could cause serious > > issues ..." > > - Change the message to only appear if the bib is used in orders connected > > to an active budget and give a count of only orders connected to an active > > budget. > > - Complete bug 16872 to entirely block the deletion of bibs in open orders, > > then remove this warning. If we're not allowing the deletion of bibs from > > open orders, then it's not a big deal. > > I am ok with the first and last suggestion, but in doubt about the 'only in > active budgets'. Sometimes libraries may mark a budget form last year > inactive and change the budget on receiving the item. I think > differentiating between open and closed would work well enough. +1 for Katrin, that's extactly our workflow, we change budget only on receipt. |