When migrating from Voyager to Alma, you may want to cleanup bad item barcodes.  This typically occurs due to operator error.  Identifying and fixing these barcodes may be wise.

This query, which can be run using Voyager Prepackaged Access Reports, will prompt for the correct number of digits for your library's barcodes and display a list of those barcodes that differ:

SELECT ITEM_BARCODE.ITEM_BARCODE,
LOCATION.LOCATION_CODE, ITEM.COPY_NUMBER,
utf8to16([mfhd_master].[DISPLAY_CALL_NO])
AS Display_Call_No, MFHD_ITEM.ITEM_ENUM,
MFHD_ITEM.CHRON
FROM (((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)
INNER JOIN LOCATION
ON MFHD_MASTER.LOCATION_ID = LOCATION.LOCATION_ID
WHERE (((Len([ITEM_BARCODE]))<>Val([Enter correct item barcode length])))
ORDER BY LOCATION.LOCATION_CODE,
utf8to16([mfhd_master].[DISPLAY_CALL_NO]),
MFHD_ITEM.ITEM_ENUM, MFHD_ITEM.CHRON;

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.