- Article Type: General
- Product: Aleph
- Product Version: 20
- Relevant for Installation Type: Dedicated-Direct; Direct; Local; Total Care
We usually can not create a duplicate barcode in ABC50. However this happens occasionally so we run a weekly report looking for duplicates. In this week's report we located a duplicate with one bib in ABC01 and the other bib in ABC40.
We changed the barcode in the item created by the ILL receive and will probably need to change the request status using SQL. It looks like IMCR borrowed an item (#241444) from IMNU and when the receive was done the item was created with the duplicate barcode.
SQL> select Z30_HOL_DOC_NUMBER_X, z30_rec_key from z30 where z30_barcode = '31951D014551735';
003281812 002493495000010 (item in ABC50 associated with bib record in ABC01)
000000000 005180241000010 (item in ABC50 associated with bib record in ABC40)
Checking the z30_id1 in abc50 util a/17/14, I see that the z30_id1 is not unique:
Z30_ID1 VALID NORMAL NONUNIQUE Z30_BARCODE
As distributed, the z30_id1 and the z30_barcode are *not* unique. This issue is discussed in KB 8192-4664 (Duplicate item barcodes). See SmartLiink below.
KB 8192-4664: Duplicate item barcodes
- Article last edited: 10/8/2013