Summary: | Reservations Notification for return shelf | ||
---|---|---|---|
Product: | Koha | Reporter: | Mathias Hein <mathias.hein> |
Component: | Notices | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | ||
Version: | unspecified | ||
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
Mathias Hein
2023-10-13 14:28:12 UTC
The mailing list is usually a good starting point to discuss workflows like this. I think we might already have what you need, maybe: If you are using self checks that communicate via SIP2 there is the HoldsNeedProcessingSIP system preference. If activated, holds returned at the self check will not immediately be set to waiting, but remain in a processing status that you can use to find them via a report. The JSON API for reports can then be used with a little jQuery to display the number of holds in this status anywhere you want in Koha basically. Or you could just place a link to the report somewhere using HTML customizations. The processing status requires another checkin, that then sets the item to waiting and alerts the patron who has placed the hold. Depending on your equipment/supplier you can also find out about on hold items via SIP and use this to inform the user about a separate location the item should be placed in. What is the name of the report or how would it have to be created and how would it be specified there? Maybe I can test this in a demo to see if it works technically. But the chosen approach sounds good. The report would be written with SQL with the columns you want to display and added to the "Saved reports". Have a look at the reports module - it's super useful. It could look a bit like this: select (select title from biblio bi where bi.biblionumber = i.biblionumber) as Titel, i.itemcallnumber as Signatur, i.barcode AS Barcode, r.borrowernumber AS Benutzernummer, r.reservedate AS Vormerkdatum, r.biblionumber AS Titelsatznummer, r.timestamp AS Zeitstempel from items i, reserves r where r.found = 'P' and i.biblionumber = r.biblionumber order by r.timestamp DESC The interesting bit here is the 'where reserves.found = "P"' If you go the easier route, a link could be added using the IntranetmainUserblock or IntranetNav system preferences. |