SIP patron part level holds respond blank

Bug #1525394 reported by Blake GH
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

We have discovered that when the results of a "63" input message contain part level holds, the corresponding titles in the "|CD" are blank:

6300120151211 104201 Y AOhidden|AAhidden|AC|AY1AZF08D

OUTPUT MSG: '64 Y 00020151211 104201001300000022000000000009AOhidden|AAhidden|AEhidden|BHhidden|BV0.00|BDhidden|BEahidden|BFhidden|AQhidden|CDAll dressed in white|CDPrey|CDSister act 2 : back in the habit|CDWinter|CDThe tournament at Gorlan|CDQueen of shadows|CD|CD|CD|BLY|PA20160609|PBhidden|PCResident|PIFiltered|XI20283|AFOK|AY1AZ842A'

in this example, there are three part level holds with blank titles.

Revision history for this message
Blake GH (bmagic) wrote :
Revision history for this message
Thomas Berezansky (tsbere) wrote :

While updating __hold_to_title to support part holds is wonderful, I think we also need to pay attention to these functions:


As well as include Issuance holds (in all three functions).

tags: added: sip
Revision history for this message
Jason Boyer (jboyer) wrote :

I've tested and signed-off on Blake's parts hold addition and have also added issuance holds in this branch:;a=shortlog;h=refs/heads/user/jboyer/lp1525394_more_sip_hold_titles / working/user/jboyer/lp1525394_more_sip_hold_titles

This should complete our current hold type coverage for this feature.

To test, apply the top 2 commits from that branch, place multiple types of holds for a user (at a minimum for this test, Parts and Issuance) and then send a Patron Information Message (63) from a SIP client or telnet and ask for hold details (set the Summary field first position to 'Y'), and you should see an AS field entry for each hold placed. For example, in the concerto data, an I hold on the IEEE title, T hold on The Concerto, and a P hold on Le Concerto gives this Patron Information Response:

64 Y 00020190909 152100000300000000000000000003AOlocal|AAsip-client|AESIP User|BHUSD|BDnaw nope, mnn 54321|BF555-123-4321|AQBR1|ASIEEE International conference on software testing, verification and validation : [proceedings]|ASThe concerto|ASLe concerto|BLY|CQY|PA20220906|PCSIP|PIFiltered|XI238|

tags: added: pullrequest
Michele Morgan (mmorgan)
Changed in evergreen:
milestone: none → 3.4-beta2
Galen Charlton (gmc)
Changed in evergreen:
milestone: 3.4-beta2 → 3.4.1
Changed in evergreen:
milestone: 3.4.1 → 3.4.2
Changed in evergreen:
milestone: 3.4.2 → 3.4.3
Changed in evergreen:
milestone: 3.4.3 → 3.4.4
Changed in evergreen:
milestone: 3.4.4 → 3.5.2
Changed in evergreen:
milestone: 3.5.2 → 3.6.1
Changed in evergreen:
milestone: 3.6.1 → 3.6.2
Changed in evergreen:
milestone: 3.6.2 → 3.6.3
Changed in evergreen:
milestone: 3.6.3 → 3.6.4
Changed in evergreen:
milestone: 3.6.4 → 3.7.2
Revision history for this message
Christopher Burton (cburton) wrote :

I can affirm that Volume/Issuance holds seem to work.

However, in a Part level hold, without a targeted copy, SIP responds with an incorrect barcode pointing to a completely unrelated item. My part level hold for a DVD points to a John Denver CD. Completely different monograph parts and unrelated items.

Revision history for this message
Jason Boyer (jboyer) wrote :

There is an additional commit that I neglected to upload to the initial branch. Here's a rebased version that contains all 3:;a=shortlog;h=refs/heads/user/jboyer/lp1525394_more_sip_hold_titles_2 / working/user/jboyer/lp1525394_more_sip_hold_titles_2

I'd like some more eyes on it and some additional testing if possible. My by-hand testing looked ok with msg64_hold_items_available set to barcode or not, but I'm not using anything fancier than telnet here.

Jason Boyer (jboyer)
Changed in evergreen:
status: New → Confirmed
no longer affects: evergreen/3.4
no longer affects: evergreen/3.5
Changed in evergreen:
milestone: 3.7.2 → 3.7.3
no longer affects: evergreen/3.6
Changed in evergreen:
milestone: 3.7.3 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.