When migrating from Voyager to Alma, you may want to identify those BIB records that have an OCLC number in 035 subfield 9 but have no 035 subfield a.
These queries, which you can run using Voyager Prepackaged Access Reports, find BIB records that lack a control number in 035 subfield a, but that also have an OCLC control number in 035 subfield 9.
Additional information: In migrations between integrated library systems, record control number data may have been migrated from either the 001 or the 035$a into an 035$9 field. Staff can review records that have an OCLC number in the 035$9, and that have no other control number. Determine if the OCLC number in 035$9 is still valid in OCLC by searching WorldCat. If the number is valid, you can change the subfield value from $9 to $a. If the OCLC number is no longer valid, then change the subfield value from $9 to $z.
The main query may contain several lines of 035 data in a long text field, if the record includes multiple 035s. Adjust the row height of the results in Access or in Excel to see all 035 data.
Subquery: Save this subquery with the name "Bibs_with_no_035a_subq", but don't run it.
WHERE (((BIB_MASTER.BIB_ID) Not In (SELECT BIB_INDEX.[BIB_ID]
Main Query (run this query):
SELECT BIB_INDEX.BIB_ID, BIB_INDEX.INDEX_CODE, BIB_INDEX.NORMAL_HEADING,
getfieldrawall(getbibblob([BIB_INDEX].[bib_id]),'035') AS bib035
FROM BIB_INDEX INNER JOIN Bibs_with_no_035a_subq
ON BIB_INDEX.BIB_ID = Bibs_with_no_035a_subq.BIB_ID
AND ((BIB_INDEX.NORMAL_HEADING) Like "*OCOLC*"));
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.