https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37640
--- Comment #5 from Katrin Fischer <[email protected]> --- Hm, wondering about this one. We also have the case that the external partner doesn't know the patron_id, so we use listPatrons and query by cardnumber, which returns only one patron's information. This way we only need one query to get the information we need and the patron_id to use in further requests. Do we risk breaking things where Koha uses the API internally? Cardnumber isn't a mandatory field necessarily. There are also other routes where the patron_id would still be required, like when looking up checkouts or placing holds. I feel it might make things a little more inconsistent. Small typo here: - description: Embed list sent as a request header + description: Embed list sent as a request header hello -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
