• Article Type: General
• Product: Voyager
• Product Version: 8.1.0

Description:
Bug Report Form for Issue 16384-13729
Module(s): Voy to Primo Extract
Server platform(s) affected: Tested on Solaris
PC OS (if applicable): N/A
Browser & version (if applicable): N/A

Release(s) replicated in: 7.2.3, 7.2.4
Last version without bug (if applicable): N/A

Expected results: If an item has any one status that maps to unavailable, the extract should populate the 949e with “unavailable”.

Actual results: If an item has any one status that maps to available (even if it has a number of other statuses that are mapped to unavailable), the extract populates the 949e with “available”.

Workflow implications: Items that are unavailable to users appear available in Primo

Replication steps:
1. In Circulation, bring up an item record and give an item a status that maps to available and several statuses that map to unavailable.
2. Run Pprimoexp.avail using an .ini file that has AvailFilter=Y
3. If you now look at the extracted record’s 949e, you’ll see that it says “available”, even though the item in question has several statuses that map to “unavailable”.

Other information: The order in which statuses are applied does not appear to matter – reliably, if any one status associated with the item maps to available, the record will extract with a 949e of available.

This issue is a continuation of 16384-6865, which was supposed to be fixed in 7.2.3, but is still ongoing.

Resolution:
Fixed in Primo extract in 8.1.0.

• Article last edited: 3/16/2015