Alphabetic character in z13u numeric-only LKR field
- Article Type: General
- Product: Aleph
- Product Version: 19.01
Description:
In our ABC60 library, we have found two z13u records with an alpha character in the z13u_user_defined_4 field. The ABC60/tab/tab22 defines this as
ABC60/tab/tab22:
USER-DEF-4 1 LDR
02 z13u_rec_key \
03 doc_number ................003865628
....
02 z13u_user_defined_4_code ....LKR
02 z13u_user_defined_4 .........a000776976
02 z13u_rec_key \
03 doc_number ................002948925
....
02 z13u_user_defined_4_code ....LKR
02 z13u_user_defined_4 .........W000524159
These should be completely numeric fields. How did the alpha characters get there and how should these be corrected?
Resolution:
The z103's look like this because the LKR fields in the ABC60 doc records they come from have these [erroneous] characters.
ABC60 003865628:
LKR L $$aHOL$$lABC01$$ba000776976
ABC60 002948925:
LKR L $$aHOL$$lABC01$$bW000524159
This happens because the cataloger types this data into the field at some point.
It is possible, using the ./abc60/pc_tab/catalog/permission.dat, to prevent the update of the LKR field by catalogers.
- Article last edited: 10/8/2013