[Bug 18436] New: Add home library to the SIP2 patron info response 64
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18436 Bug ID: 18436 Summary: Add home library to the SIP2 patron info response 64 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs@lists.koha-community.org Reporter: george@shoutbomb.com QA Contact: testopia@bugs.koha-community.org CC: colin.campbell@ptfs-europe.com Koha's SIP2 server should provide additional patron related info, in this case the patron's home library. This will be a new segment and should be the key not the name. The following is an example from another ILS SIP2 response with the segment AQ providing the home library info. SIP2:response:: 64 00020170412 183400000000000001000000000000AOzzz|AA21391999999999|AEWALKER JONNY|AQpcl|BZ0050|CA0020|CB0250|BLY|CQY|BHUSD|CC10.|BD12655 S KOHA AVE, HELLO, AZ, 99999|BF111-222-3333|DJWALKER MOLLY|PB19950808|PCres|PE20190412 235900|PS20190412 235900|ZYres|AY2AZB936 Thanks... George -- 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=18436 Marc Véron <veron@veron.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |veron@veron.ch -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18436 --- Comment #1 from Marc Véron <veron@veron.ch> --- Created attachment 62183 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=62183&action=edit Bug 18436: SIP: Add home library to the SIP2 patron info response 64 This patch adds the patron's home library code as AQ segment to response 64 (patron information) To test: - Set up Koha SIP2 server ( https://wiki.koha-community.org/wiki/Koha_SIP2_server_setup ) - Test without patch, verify that AQ segement does not appear in response 64 - Apply patch, stop / start SIP2 server (maybe restart plack and memcached as well) - Verify that AQ segment with patron's home library code appears in response 64 -- 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=18436 Marc Véron <veron@veron.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |Needs Signoff Assignee|koha-bugs@lists.koha-commun |veron@veron.ch |ity.org | Patch complexity|--- |Trivial patch -- 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=18436 --- Comment #2 from Colin Campbell <colin.campbell@ptfs-europe.com> --- Would be useful to know which supplier has added the AQ field to the 64 response as the published sip2 and sip3 specs define it as permanent item location -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18436 george@shoutbomb.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off --- Comment #3 from george@shoutbomb.com --- The example was from Sirsi Dynix (Horizon). My understanding now is that the AO segment can be an option for providing the patron home "UsePatronBranchForPatronInfo; If ON, the SIP patron information response (64) will use the patron branch rather than the institution ID in the AO field." The issue I have with this is that multiple third party access may encounter a conflict. But this patch is a nice to have. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18436 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |In Discussion CC| |nick@bywatersolutions.com --- Comment #4 from Nick Clemens <nick@bywatersolutions.com> --- Why not use the existing functionality to send patron's homebranch in the AF field? send_patron_home_library_in_af="1" -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18436 --- Comment #5 from Colin Campbell <colin.campbell@ptfs-europe.com> --- (In reply to Nick Clemens from comment #4)
Why not use the existing functionality to send patron's homebranch in the AF field?
send_patron_home_library_in_af="1"
AF is a screen message. I'm assuming that the point of this feature is to supply the information to be used by the sip unit and that will expect it in a specific field. In practice suppliers are unlikely to even attempt to parse such data out of AF. I'd still be interested to know which machine supplier is requiring AQ (I was asking about SIP devices not LMSs above), if we dont have one then AF would be the logical place if we want to display this info. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18436 --- Comment #6 from george@shoutbomb.com --- We provide a solution that supports multiple ILS providers and SIP2 is the underlying service across those various ILS. When I cannot provide the needed feature using SIP2 I have to look to the ILS in hopes that they have an "api" that provides third-party support. In this case there was a need to derive the patron "home library" and this was not available via SIP2 and there are no third party api. So, the path was to ask for a change to SIP2, otherwise plan B was to develop a work around that in the long run was not sustainable. In the end I was able to verify that this patch works, but they were not ready to accept this patch. Instead, there was an option to utilize the AO segment to provide the patron home library. I am hoping they will incorporate this patch at a later point. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18436 --- Comment #7 from george@shoutbomb.com --- We provide a solution that supports multiple ILS providers and SIP2 is the underlying service across those various ILS. When I cannot provide the needed feature using SIP2 I have to look to the ILS in hopes that they have an "api" that provides third-party support. In this case there was a need to derive the patron "home library" and this was not available via SIP2 and there are no third party api. So, the path was to ask for a change to SIP2, otherwise plan B was to develop a work around that in the long run was not sustainable. In the end I was able to verify that this patch works, but they were not ready to accept this patch. Instead, there was an option to utilize the AO segment to provide the patron home library. I am hoping they will incorporate this patch at a later point. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18436 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|In Discussion |RESOLVED Assignee|veron@veron.ch |koha-bugs@lists.koha-commun | |ity.org --- Comment #8 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- It seems like this suggestion is not standard compliant and we now provide other API that this information could be drawn from (think ILS-DI or REST API) I am closing, please reopen if you see a need for this still. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org