WISHLIST Add SIP Support for BF field on type 10 checkin responses

Bug #1528301 reported by Blake GH on 2015-12-21
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Wishlist
Unassigned
SIPServer
Wishlist
Unassigned

Bug Description

It would be nice if SIP would respond with the patron's phone number for triggered checkin holds.

The specific example request is:
09N20151211 13001720151211 130017APinstituion|AOinstituion|ABbarcode|ACsip3gf00b4r|CH|BIN|AY0AZE559

and an example response is:

101NYY20151211 130018AOinstituion|ABbarcode|AQlibrary|AJOld school|CK001|CRshelf|CShide|CTbranch|CYpatron barcode|DApatron name|CV01|AY0AZCDE2

We would like the response to include:

|BFhold_phone_notify_number

Thomas Berezansky (tsbere) wrote :

Looking at my copy of the specs I only find BF defined for patron information responses, not checkin response. As such I imagine very little out there even looks for it on checkins.

Blake GH (bmagic) wrote :

We have a library moving away from CircIT to Bibliotheca - and there is an issue here with the checkin fill hold notify phone number. CircIT would ask the server for the phone number on a separate query after the checkin filled a hold. Bibliotheca's software will not. We have asked them to change their software and they will not. So, I am changing ours.

Blake GH (bmagic) on 2016-06-09
tags: added: pullrequest
Changed in evergreen:
assignee: nobody → Blake GH (blake-j)
assignee: Blake GH (blake-j) → nobody
Martha Driscoll (mjdriscoll) wrote :

We have a library using an automated handler and asked for the phone number to be included on the hold slips. This is going to work great for them. The vendor (pv-supa) can add the phone number once it is included in the checkin message.

I have tested this and confirm that the hold phone number is included in the BF field of the checkin message when a hold is present on the checked-in item.

Michele Morgan (mmorgan) on 2017-04-05
Changed in evergreen:
milestone: none → 3.0-alpha
Galen Charlton (gmc) wrote :

Since including the BF field in the checkin response message is both an extension to the protocol /and/ exposes more personally identifiable information for patrons, it needs a configuration guard similar to the relais_extensions_to_msg24 (with a default value of false).

I'm removing the pullrequest tag on that basis, but the patches otherwise look good; they just need a supplement.

Changed in evergreen:
importance: Undecided → Wishlist
Changed in sipserver:
importance: Undecided → Wishlist
Changed in evergreen:
status: New → Confirmed
Changed in sipserver:
status: New → Confirmed
tags: removed: pullrequest signedoff
Changed in evergreen:
milestone: 3.0-beta → 3.next
Elaine Hardy (ehardy) on 2019-03-08
tags: added: sip wishlist
Jason Boyer (jboyer) wrote :

I've added an institution setting to enable this extension and have 2 new signoff branches based on current master at

Evergreen: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1528301_hold_phone_checkin_so / working/user/jboyer/lp1528301_hold_phone_checkin_so

SIPServer: https://git.evergreen-ils.org/?p=working/SIPServer.git;a=shortlog;h=refs/heads/user/jboyer/lp1528301_config_check / working/user/jboyer/lp1528301_config_check

Jason Boyer (jboyer) on 2019-09-09
tags: added: pullrequest
Jason Boyer (jboyer) on 2020-02-10
Changed in evergreen:
milestone: 3.next → 3.4.3
Jason Boyer (jboyer) on 2020-02-10
Changed in evergreen:
milestone: 3.4.3 → 3.5-alpha
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers