[Bug 37195] New: Add ILL as option to TrackLastPatronActivityTriggers
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37195 Bug ID: 37195 Summary: Add ILL as option to TrackLastPatronActivityTriggers Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs@lists.koha-community.org Reporter: magnus@libriotech.no CC: pedro.amorim@ptfs-europe.com, tomascohen@gmail.com This has a couple of tricky aspects to it, I think. Basically, the problem is that for some patrons their only activity in the library could be to request article copies/prints through ILL. At least the way it works in Sweden, with ILL based around Libris, an ILL reques for a book would update lastseen, when the book is issued to the patron. But a request for an article copy/print would not update lastseen, because the ILL is just handled in the Libris backend, and there is no loan or other activity that is tracked today. The solution is probably to update lastseen from the Libris backend when a copy/print is marked as received, like so: $patron->update_lastseen('activity'); But that "activity" needs to be activated in TrackLastPatronActivityTriggers. Questions: - Should we add a generic "ill" activity? Or would it make sense to have e.g. "ill_loan" and "ill_copy"? - Would it be OK to have "ill" listed as an activity for TrackLastPatronActivityTriggers even if the ILL module is not activated? - Would it make sense to have an activity in TrackLastPatronActivityTriggers that perhaps does nothing out of the box, but relies on the different backends to actually call update_lastseen? Or could the ILL module itself call update_lastseen, and not rely on the backends to do it? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37195 --- Comment #1 from Pedro Amorim <pedro.amorim@ptfs-europe.com> --- Would simply having "Place an ILL request" as an option satisfy this use case? I suggest this be handled in core sub backend_create. It would update a patron's lastseen regardless of the type of request, or if it results in a loan or not. It would also be in line with current options (very specific, single, actions), and future use cases can also be considered to be implemented the same way e.g. "Cancelling an ILL request". (In reply to Magnus Enger from comment #0)
- Would it be OK to have "ill" listed as an activity for TrackLastPatronActivityTriggers even if the ILL module is not activated?
It would be okay imo (not critical), but I think ideally it shouldn't list the option if ILLModule is disabled. Although I can see the following happening: 1) "Place an ILL request" option is enabled in TrackLastPatronActivityTriggers 2) ILLModule gets disabled 3) TrackLastPatronActivityTriggers sys pref is updated ("Place an ILL request" is now gone because it wasn't listed thus not submitted) 4) ILLModule gets enabled 5) TrackLastPatronActivityTriggers does not have the "Place an ILL request" enabled. Not very relevant or critical, but something to keep in mind if this is a first (having conditional list options in a sys pref) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37195 --- Comment #2 from Magnus Enger <magnus@libriotech.no> ---
Would simply having "Place an ILL request" as an option satisfy this use case? I suggest this be handled in core sub backend_create. It would update a patron's lastseen regardless of the type of request, or if it results in a loan or not.
Yeah, that sounds like an excellent idea. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37195 Inkeri Hakulinen <inkeri.hakulinen+bugz@helsinki.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |inkeri.hakulinen+bugz@helsi | |nki.fi --- Comment #3 from Inkeri Hakulinen <inkeri.hakulinen+bugz@helsinki.fi> --- I agree that simple "place an ILL request" would be the best option to update patron's lastseen. I would also like that this option was visible in the trackLastPatronActivityTriggers list even though the ILL module was disabled. It would help people who are just thinking about whether to start using ILL module or not, to see right away, that this option is there. Of course it should be with instructions, that this does nothing, if ILL module is disabled. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org