When migrating from Voyager to Alma, it may be desirable to identify those BIB records with Mutliple MFHDs.  This can help you to identify those BIBs that have mutiple MFHDs of different format types and "split" them into separate BIB records.  For more information, discuss this with your migration team.

The following consists of two queries that can be run using Voyager's Prepackaged Access Reports. They need to be run in sequence.

The first is a "MAKE TABLE" query that creates a table containing the BIB ID and count of MFHDs for those BIBs with more than one MFHD.  You can run this query and check the results in the table.

The second "main" query uses the data in the table created by the first query to provide information about the BIBs and their MFHDs.  Note that you'll see multiple rows per BIB ID - one for each MFHD record attached to the BIB.

MAKE TABLE QUERY (do not change the name of the table it makes):

SELECT BIB_MFHD.BIB_ID, Count(BIB_MFHD.BIB_ID) AS CountOfBIB_ID INTO MULTI_MFHD
FROM BIB_MFHD
GROUP BY BIB_MFHD.BIB_ID
HAVING (((Count(BIB_MFHD.BIB_ID))>1));

MAIN QUERY:

SELECT MULTI_MFHD.BIB_ID, MULTI_MFHD.CountOfBIB_ID, BIB_TEXT.BIB_ID, BIB_TEXT.AUTHOR, BIB_TEXT.TITLE, BIB_MFHD.MFHD_ID, MFHD_MASTER.DISPLAY_CALL_NO, LOCATION.LOCATION_NAME
FROM ((MULTI_MFHD INNER JOIN BIB_TEXT ON MULTI_MFHD.BIB_ID = BIB_TEXT.BIB_ID) INNER JOIN BIB_MFHD ON BIB_TEXT.BIB_ID = BIB_MFHD.BIB_ID) INNER JOIN (LOCATION INNER JOIN MFHD_MASTER ON LOCATION.LOCATION_ID = MFHD_MASTER.LOCATION_ID) ON BIB_MFHD.MFHD_ID = MFHD_MASTER.MFHD_ID;

Note that the second query can take a long time to run.

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.