https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30484 Bug ID: 30484 Summary: Interlibrary Loans should have the ability to send notices based on request supplier updates Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs@lists.koha-community.org Reporter: andrew.isherwood@ptfs-europe.com It should be possible for the Interlibrary Loans module to inform a user when a request supplier makes a pertinent change to an outstanding request. Scenario defined by customer to be fulfilled by this bug: - A user places an ILL request for a journal article via the RapidILL backend. - RapidILL fulfil the request with an electronic resource. - The user is notified of the request fulfilment via their chosen communication method, the notice contains the link and password required to access the requested resource. The intended solution will add a mechanism to allow Koha ILL to periodically check outstanding requests with suppliers for updates and act accordingly. As an aside, there is a known customer requirement for notices to be sent when requests are modified locally, this requirement will be catered for in the design of the solution. Details of the intended implementation: - An ILL backend, or core Koha ILL, can define one or more "update processors", these are functions that can perform an action when supplied with an update meeting the criteria they're interested in - An ILL request will be given the ability to obtain its latest status with the supplier, known as an "update" - "Updates" can then be passed to "update processors" that are interested in them, which can then perform whatever actions they wish. Generic - Core Koha ILL will provide: - An object to encapsulate supplier updates - A base class from which "update processors" can be subclassed - Functions to gather updates from backends and orchestrate the processing - A notice template which will be used to send update notices - A shell script that can be run to initiate the process For the customer use case defined above: - The RapidILL backend will: - Provide the ability to retrieve the latest update from the RapidILL API - Define a SendArticleLink processor -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.