Voyager to Alma Migration Query: Identify MFHDs with Multiple Instances of 852 Subfield b

When migrating from Voyager to Alma, you may want to identfy, review, and clean up any MFHD records that have more than one instance of 852 subfield b. While the MARC21 MFHD format allows the 852$b to be repeatable, the migration to Alma may process additional b subfields in a way that is not desirable ( for more information, discuss this with your migration team).

These two queries, which you can run using Voyager Prepackaged Access Reports, can help you identify those records. 

NOTE that the first query is a BLOB query and can take a very long time to run.

Make table query: Save this query and run it before running the Main Query.

SELECT MFHD_MASTER.MFHD_ID, MFHD_MASTER.SUPPRESS_IN_OPAC,
MFHD_MASTER.DISPLAY_CALL_NO, MFHD_MASTER.NORMALIZED_CALL_NO,
Replace(getfieldraw(getmfhdblob([mfhd_id]),'852',1),Chr(31),'$') AS mfhd852
INTO mfhds_w_852_raw_tbl
FROM MFHD_MASTER;

Main Query (uses the table created in the previous query:

SELECT mfhds_w_852_raw_tbl.MFHD_ID, mfhds_w_852_raw_tbl.SUPPRESS_IN_OPAC,
mfhds_w_852_raw_tbl.DISPLAY_CALL_NO, mfhds_w_852_raw_tbl.NORMALIZED_CALL_NO,
mfhds_w_852_raw_tbl.mfhd852
FROM mfhds_w_852_raw_tbl
WHERE (((mfhds_w_852_raw_tbl.mfhd852) Like "*$b*$b*"));

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.