In VuFind you can enter a comment when placing a hold. This comment is currently not visible in Koha. May contain important information for handling in Koha and should therefore be transmitted.
Hi Roland, as we don't know how your Koha and VuFind interact with each other, we have no way of fixing this for you. We'd need more information and also a way to determine if this is a Koha or a VuFind issue. If you can give a step by step how the same problem appears when placing a hold from Koha, that could help.
Hi Katrin, It's an issue in both sides - on the Vufind as well as on the Koha side. I already fixed this issue for my organisation and I will try to supply a proposal for a patch for Koha as well. It'll take some time, because I first have to get familiar with the procedures, how changes are implemented in Koha. I am currently reading the documentation and will come up with a proposal. It's a rather small enhancement on the Koha side and I hope it doesn't break anything else. BTW: we are using the KohaILSDI driver on the VuFind side which interacts with ilsdi.pl on the Koha side. Are there other and probably better ways for this kind of communication with VuFind?
(In reply to Roland Keck from comment #2) > Hi Katrin, > > It's an issue in both sides - on the Vufind as well as on the Koha side. > > I already fixed this issue for my organisation and I will try to supply a > proposal for a patch for Koha as well. It'll take some time, because I first > have to get familiar with the procedures, how changes are implemented in > Koha. I am currently reading the documentation and will come up with a > proposal. It's a rather small enhancement on the Koha side and I hope it > doesn't break anything else. > > BTW: we are using the KohaILSDI driver on the VuFind side which interacts > with ilsdi.pl on the Koha side. Are there other and probably better ways for > this kind of communication with VuFind? KohaILSDI is now the best approach. Until the REST API in Koha (and appropirate driver in VuFind) is "finished". KohaILSDI driver does mix using ILS-DI and database access.
I believe it would be an option to use the REST API now - should this be closed?
Can be closed