Applying template with non-existent call number prefix/suffix results in uncataloged item
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Evergreen 2.3.7
This bug is related to https:/
Here's the manifestation of this bug:
The user opens an existing item in the unified editor, chooses a template and applies it, then clicks the button to "Re-barcode / Update Items".
The user finds that their holding disappears from the bib record, and the item, which can still be retrieved by barcode, is uncataloged.
The problem is a defunct call number prefix or suffix designation stored in the template, so the unified editor attempted to create a new call_number record with a prefix or suffix that does not exist in the database.
In its attempt to run through its chain of envents, the unified editor successfully deleted the old call_number, but did not successfully create the new call_number. Despite the failure to create the new call_number, it attempted to move the item to the non-existent call_number record, resulting in the uncataloged item.
Here are some entries from the server logs showing failure to create the call_number record:
2013-04-30 08:09:28 app101 open-ils.cat: [INFO:19718:
2013-04-30 08:09:28 app101 open-ils.cstore: [ERR :10142:
Key (suffix)=(2404) is not present in table "call_number_
Note that asset.call_
Changed in evergreen: | |
status: | New → Won't Fix |
An update on this:
Our system is now running release 2.4.4 and this is problem still exists.