Pick and Scan: Location Name ---------- sets perm_location=0
- Article Type: General
- Product: Voyager
- Product Version: 9
Description:
Bug Report Form for Issue 16384-16881 / VYG-4403
Module(s): Pick and Scan (Cataloging, Circulation, System Administration)
Release(s) replicated in: 8.0.0
Last version without bug (if applicable): n/a
Expected results: When running Pick and Scan, no data would be altered for a field if no change is selected in the Item Options.
Actual results: If a location_name is made up of only dashes, i.e., ------------, when executing Pick and Scan, the item’s perm_location will be set to 0.
Workflow implications: Items cannot be opened or edited afterward because the location_id of 0 is not a valid location that belongs to any security profile or policy definition.
Replication steps:
In SysAdmin, create a new location. Give it any Code you wish, and make the name a series of dashes with nothing else: ----------
Add the location to the appropriate circulation & cataloging security profiles and policy definitions.
Log in to Circulation or Cataloging, find an item record and note the barcode.
Open Pick and Scan and choose a change to make (i.e., give the item a new Statistical Category) in the Item Options tab.
Click on the Items tab and enter the barcode from the item you found and click the checkbox to execute your change.
Note that in the change list that prints when you execute, the Permanent Location shows as “No Change”.
If you now open the item record. In Circulation, you can view the record, but if you choose Edit Item, you receive message: “Your security profile does not allow you to edit items from” and in Cataloging, the item is retrieved and immediately gives the message “Permanent location is not an authorised location. Record may not be saved”
If you go back into SysAdmin and change the Location Name to include an alphanumeric character or a different symbolic character (tested successfully with ampersand, semicolon and period), Pick and Scan will not clear the item’s location.
Other information: Similar to issue 15897, caused by a blank location name. Fixed by adding location name (and only able to save without location name due to a different bug).
Workaround: If using dashes for display purposes (i.e., location name to appear blank in OPAC request forms or notices) use periods instead of dashes.
Resolution:
VYG-4403 is resolved in Voyager 9.0.0 and higher.
- Article last edited: 3/5/2015