vxws: Record Holdings API does not generate 866 from 853/863 when 866 present

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Article Type: General
Product: Voyager
Product Version: 8.2.1

Description:
Issue number: 16384-20273
Module: RESTful APIs / Record Holdings
Server platform affected: all
PC OS: n/a
Browser & version: n/a
Releases replicated in: 8.1.2
Last version without bug: n/a

Expected results: Generated 866 fields in Record Holdings API would be built from 853/863 pairs in holdings record.

Actual results: When 866 fields are present in a holdings record, generated 866 field in Record Holdings API pulls existing 866 fields rather than building from 853 and 863 pairs.

Workflow implications: 853 and 863 data are not represented in the holdings data sent by the API.

Replication steps:
In Cataloging, find a holdings record that contains both an 853/863 pair and an 866 field.
Note the contents of these fields.
853 2 3 ‡8 29 ‡a v. ‡b no. ‡u 12 ‡v r ‡i (year) ‡j (month) ‡w m ‡x 01
863 4 0 ‡8 29.360 ‡a 42-44 ‡i 2003-2005
863 4 0 ‡8 29.370 ‡a 45-47 ‡i 2006-2008
866 4 0 ‡a v. 42-47 ‡x Bound in two volumes per year ‡z Some issues missing.

Use the Record Holdings API to retrieve the holdings data. This API should translage the 853/863 pair into a generated 866 _ 7 field.
http://<IP>:<port>/vxws/record/<bibID>/holdings?view=items&patron_homedb=&patron=&patron_group=GUEST&startPos=1&noItems=6
where <IP> is IP of Voyager server where vxws is running; <port> is vxws port; <bibID> is bib for mfhd record above.
Look at the XML returned by the API request and note that the 866 4 0 and the generated 866 _ 7 are the same.
<datafield ind2="0" ind1="4" tag="866">
<subfield code="a">v. 42-47</subfield>
<subfield code="x">Bound in two volumes per year</subfield>
<subfield code="z">Some issues missing.</subfield>
</datafield>
<datafield ind1=" " ind2="7" tag="866">
<subfield code="2">Generated on output from 853/863</subfield>
<subfield code="a">
v. 42-47 Some issues missing.v. 42 - v. 44 (2003 - 2005)v. 45 - v. 47 (2006 - 2008)
</subfield>
</datafield>
When the 866 is not present in the holdings record, the 866 _ 7 is generated from the 853/863:
<datafield ind1=" " ind2="7" tag="866">
<subfield code="2">Generated on output from 853/863</subfield>
<subfield code="a">
v. 42 - v. 44 (2003 - 2005)v. 45 - v. 47 (2006 - 2008)
</subfield>
</datafield>

Workaround: Set Primo to display existing 866 fields in record instead of 866 _ 7.

Resolution:
Fixed in Voyager 8.2.1

Article last edited: 3/16/2015