When migrating from Voyager to Alma it may be helpful to identify, review and perhaps "fix" MFHD records that have a call number but are not indexed properly in Voyager due to the lack of an 852 first indicator value.

While it is acceptable to have MFHDs with no call number, when there is a call number in the MFHD there should be an 852 field first indicator value.

This query, which can be run using Voyager's Prepackaged Access Reports, will identify those MFHD records.

​SELECT MFHD_MASTER.MFHD_ID, LOCATION.LOCATION_CODE,
MFHD_MASTER.NORMALIZED_CALL_NO, MFHD_MASTER.DISPLAY_CALL_NO,
MFHD_MASTER.CALL_NO_TYPE, MFHD_MASTER.CREATE_DATE FROM MFHD_MASTER INNER
JOIN LOCATION ON MFHD_MASTER.LOCATION_ID = LOCATION.LOCATION_ID WHERE
(((MFHD_MASTER.NORMALIZED_CALL_NO) Is Null) AND
((MFHD_MASTER.DISPLAY_CALL_NO) Is Not Null));

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.