vxws: no delimiter in generated 866 for Record Holdings API

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

Article Type: General
Product: Voyager
Product Version: 8.2.1

Description:
Bug Report Form, 16384-52564

Date: 2 November 2012
Module(s): vxws / RESTful API (Record Holdings)
Release(s) replicated in: 7.2.0 – 8.1.2
Last version without bug (if applicable): n/a

Expected results: When multiple fields are sent in an 866 _ 7 generated summary holdings statement, they would be separated with a semicolon or some kind of delimiter.

Actual results: When multiple fields are sent in an 866 _ 7 generated summary holdings statement, there is no separation and the statements run together.

Workflow implications: Holdings statements are difficult to read in Primo.

Replication steps:
In Cataloging, find a holdings record that has an 853 field and multiple 863 fields, i.e.:
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.240 ‡a 45-46 ‡i 2006-2007
863 4 0 ‡8 29.241 ‡a 47-48 ‡i 2008-2009

Use Record Holdings API to retrieve holdings information:
http://<IP>:<vxws port>/vxws/record/58953/holdings?view=items
(where 58953 is bib ID for example mfhd above)

The API will generate an 866 _ 7 field from the 853/863 fields. In the XML returned, note that there is nothing to separate the data (such as semi-colon or line break) from the two 863 fields in the generated 866:

<datafield ind1=" " ind2="7" tag="866">
<subfield code="2">Generated on output from 853/863</subfield>
<subfield code="a">
v. 45 - v. 46 (2006 - 2007)v. 47 - v. 48 (2008 - 2009)
</subfield>
</datafield>

Workaround: None, though depending on data in mfhds, may be able to make display changes in Primo that do not utilize 866 _ 7.

Resolution:
Fixed in Voyager 8.2.1

Article last edited: 3/16/2015