Voyager to Alma Migration Query: Identify specific records where item type is not consistent with the item location

When migrating from Voyager to Alma it may be important to identify those records where the item type is not consistent with the item's location.  This query is designed to run using the output of the on-board Prepackaged Access Report that is called "Item Count by Location and Type".  That on-board query allows you to see the number of occurrences of each combination of permanent location and item type.  In other words, it simply provides counts of each pairing.

The following query, which can be run using Voyager Prepackaged Access Reports, will show you the specific items with questionable conbinations as per the on-board prepackaged report described above. When you run this query, it will ask for the LOCATION_NAME and the ITEM_TYPE_NAME.  Both are case senstive and both must be entered exacty as you see them in the "Item Count by Location and Type" query.

SELECT LOCATION.LOCATION_NAME, ITEM_TYPE.ITEM_TYPE_NAME, 
utf8to16([mfhd_master].[DISPLAY_CALL_NO]) AS DISPLAY_CALL_NO, 
MFHD_ITEM.ITEM_ENUM, MFHD_ITEM.CHRON, 
ITEM.ITEM_ID, ITEM_BARCODE.ITEM_BARCODE
FROM ((ITEM_TYPE INNER JOIN ((MFHD_ITEM INNER JOIN MFHD_MASTER 
ON MFHD_ITEM.MFHD_ID = MFHD_MASTER.MFHD_ID) INNER JOIN ITEM 
ON MFHD_ITEM.ITEM_ID = ITEM.ITEM_ID) 
ON ITEM_TYPE.ITEM_TYPE_ID = ITEM.ITEM_TYPE_ID) 
INNER JOIN LOCATION ON ITEM.PERM_LOCATION = LOCATION.LOCATION_ID) 
LEFT JOIN ITEM_BARCODE ON ITEM.ITEM_ID = ITEM_BARCODE.ITEM_ID
WHERE (((LOCATION.LOCATION_NAME)=[Location Name (not CODE):]) 
AND ((ITEM_TYPE.ITEM_TYPE_NAME)=[Item type Name (not CODE):]));

For other queries that may be useful, see my "Surviving Almanado: tips for a successful pre-implementation" presentation's Accompanying Materials.
 
If you need assistance in running custom SQL queries in Prepackaged Access Reports, consult the Voyager Customer Listserv.