When migrating from Voyager to Alma, duplicate (in other words, non-unique) item barcodes will be changed to "-". This may not be desirable and you may want to fix any duplicate item barcodes before migration (talk to your migration team for more information). The following two queries can assist you in identifying duplciate item barcodes.
This first query, which you can run in Voyager's Prepackaged Access Reports, should help you to identify duplicate barcodes in your database and fix them.
SELECT ITEM_BARCODE.ITEM_BARCODE, Count(ITEM_BARCODE.ITEM_ID) AS CountOfITEM_ID
GROUP BY ITEM_BARCODE.ITEM_BARCODE
This second query, when run, will ask you for a barcode number and return the barcode number, location, call number, enumeration, chronology, copy, and item ID for each item to which the barcode is attached.
SELECT ITEM_BARCODE.ITEM_BARCODE, LOCATION.LOCATION_CODE,
AS Display_Call_No, MFHD_ITEM.ITEM_ENUM,
MFHD_ITEM.CHRON, ITEM.COPY_NUMBER, ITEM_BARCODE.ITEM_ID
FROM LOCATION INNER JOIN (((ITEM_BARCODE INNER JOIN ITEM
ON ITEM_BARCODE.ITEM_ID = ITEM.ITEM_ID) INNER JOIN MFHD_ITEM
ON ITEM.ITEM_ID = MFHD_ITEM.ITEM_ID) INNER JOIN MFHD_MASTER
ON MFHD_ITEM.MFHD_ID = MFHD_MASTER.MFHD_ID)
ON LOCATION.LOCATION_ID = ITEM.PERM_LOCATION
WHERE (((ITEM_BARCODE.ITEM_BARCODE)=[Bar code:]));
For other queries that may be useful, see my "Surviving Almanado: tips for a successful pre-implementation" presentation's Accompanying Materials.
Posted as is. If you need assistance in running custom SQL queries in Prepackaged Access Reports, consult the Voyager Customer Listserv.