https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37451 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |caroline.cyr-la-rose@inlibr | |o.com, | |sonia.bouis@univ-lyon3.fr --- Comment #9 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Baptiste Wojtkowski (bwoj) from comment #8)
Hum... I have multiple problems with that FQA
1/ According to our PO, a discharge should not be able to be removed by librarians, and user should not be able to remove it. The correct behaviour would be to create a new borrower. In France in particular, the discharge means that the library account has been closed.
Have you checked the former development from Matthias Meusburger on bug 37344? It's also from Biblibre and it indicates that being able to remove a restriction was intended as we used to show a history. But no matter what: this feature has been in use for many years with the ability to lift the restriction. It's likely to break use cases if changed like that now. I know it would for German libraries.
2/ Atm removing suspension due to discharge is kinda broken, ant it is hard to support it. For example if I remember well, the array you are mentionning... only displays the last discharge. And the account after suspension results in a few minor tweaks on the OPAC, for example Bug 37344. The main issue is that a suspended user with any discharge is considered as discharged.
I agree that it is broken, because the test plan on bug 37344 clearly indicates it should not only show the latest, but all previous discharges. It would be good to investigate that. I believe something broke here and it might explain the problem we are seeing.
I'm a great fan of adding syspref, but maybe we could add one here ?
If a security question is not enough, suggest making this configurable. In this case maybe it could be a new column in the patron restrictions table. This way, we could make this option available to all restrictions onward. But I warn about it not being removable from staff interface at all, because I am almost sure it will create issues. -- You are receiving this mail because: You are watching all bug changes.