When migrating from Voyager to Alma, you may want to identify, review and clean up any bibliographic records that have multiple 245 fields. While multiple 245 fields is not a problem per se, it is against MARC standards and there is some wisdom in cleaning these records up.
These three queries, which can be run using Voyager's Prepackaged Access Reports, will display bibliographic records with more than one 245 field. Note that this is a series of queries, the first two are Make Table queries and the three must be run in sequence (Query 1, Query 2, and finally Query 3). The third query will produce your results as a list of BIB_IDs.
Note that Query 2 is a BLOB query and may take a very long time to run.
Bibliographic records with multiple 245 fields Query 1: looks for bib records with more than one entry in the 2450 index. It creates the table named Bib multiple 245 table 1, containing a list of the bib IDs:
SELECT BIB_INDEX.BIB_ID INTO [Bib multiple 245 table 1]
GROUP BY BIB_INDEX.BIB_ID, BIB_INDEX.INDEX_CODE
HAVING (((BIB_INDEX.INDEX_CODE)='2450') AND ((Count(BIB_INDEX.BIB_ID))>1));
Bibliographic records with multiple 245 fields Query 2: For the bibs listed by query 1, blob query 2 looks up the full content of each of the 245 fields found by query 1. This query may find cases where the 245 field is legitimately linked with an 880 field. It creates the table named Bib multiple 245 table 2, containing the bib IDs and the first and second 245 fields:
SELECT [Bib multiple 245 table 1].BIB_ID, getfield(getbibblob([bib_id]),"245",1)
AS First245, getfield(getbibblob([bib_id]),"245",2)
AS Second245 INTO [Bib multiple 245 table 2]
FROM [Bib multiple 245 table 1];
Bibliographic records with multiple 245 fields Query 3: For the bibs listed by query 2, query 3 omits the records with a valid 245 880 linkage. The records identified by query 3 are the ones that need to be corrected.
SELECT [Bib multiple 245 table 2].BIB_ID, [Bib multiple 245 table 2].Second245
FROM [Bib multiple 245 table 2]
WHERE ((([Bib multiple 245 table 2].Second245)<>""));
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.