- Article Type: General
- Product: Aleph
- Product Version: 20, 21, 22, 23
We have the problem describe in KB 16384-26785. I’m facing several hundred items in our NewBooks collection (temporary changes) that will have their z30-item-status set to null if we use Restore to put them back into our main collection.
I installed the latest Service P yesterday so at least new items placed in that collection will be fine, but dread dealing with the ones that are already in there.
If I knew exactly what happens when an item is changed temporarily, I might be able to make a SQL statement that could fix the ones affected. At the moment, I have no idea where Aleph stores the original values that will get Restored. I did a quick search of the Aleph 20 Collected Oracle Tables document but didn’t see anything.
The pre-Store sublibrary, collection, item status, etc., item information is stored in a Z30 field in the ADM doc record. If you do util f/4 for the ADM# of an item which has been stored, you will see this Z30 field.
It may be possible to run the p_manage_21 global change in the xxx50 library to add the necessary subfields to this Z30 field.
We 'solved' this by creating a procedure our circ desk workers can follow when they encounter an item with its item_status set to null.
- Article last edited: 10/8/2013