Summary: | ILL : make a connexion between ILL module and accounting in patron account | ||
---|---|---|---|
Product: | Koha | Reporter: | Mathieu Saby <mathsabypro> |
Component: | ILL | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | pedro.amorim, tomascohen |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Mathieu Saby
2024-12-17 08:51:50 UTC
With all these bugs I am wondering: what belongs into the backends and what is a Koha core ILL functionality. I think we need to work out a definition and some clear guidelines here. Also, library workflows in this regard might be very different. We have this feature in our backend. In our ILL workflow the request itself is charged for, even if it cannot be filled. The library might decide to waive the charge in that case, but I think it's more of an exception than the rule. In our backend we can define the charge per patron category and when the request is added the account is charged. We also have the ability to add extra cost (for example some libraries might charge extra for a high number of copies) to the ILL request and a checkbox to decide, if we want this charged to the patron account or not. We use the illrequest_attributes to store the link to the accountlines table. Maybe our documentation might give an idea how it works for us and what a backend can look like: https://wiki.bsz-bw.de/pages/viewpage.action?pageId=17565617&preview=/17565617/99615633/20-11_Handbuch_Fernleihe-2023-05-07.pdf We are reviewing the ILL module in my library. Maybe we will sponsor some enhancements, so indeed it would be useful for us to know what should be done as a plugin or not (In reply to Mathieu Saby from comment #2) > We are reviewing the ILL module in my library. Maybe we will sponsor some > enhancements, so indeed it would be useful for us to know what should be > done as a plugin or not Yes, I think a lot of the things you asked for could be dealt as part of your backend, but there might be some ideas that would be good as plugin hooks/capabilities for the backends. If you want to have a look at ours or have any questions I am happy to answer questions. |