Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Voyager

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Voyager
    3. Community Knowledge
    4. Voyager to Alma Migration Query: Identify Bib Records with an OCLC number in the 035 subfield 9 but no 035 subfield a

    Voyager to Alma Migration Query: Identify Bib Records with an OCLC number in the 035 subfield 9 but no 035 subfield a

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    Created By: Laura Guy (contact)
    Created on: 10/20/2020

     

     

     

     

     

     

     

    When migrating from Voyager to Alma, you may want to identify and review those BIB records that have an OCLC number in 035 subfield 9 but have no 035 subfield a.

     OCLC numbers are the foundation of bibliographic matching and de-duplication.  Bibliographic records should ideally have a single, unique source identifier.

    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.

    SELECT BIB_MASTER.BIB_ID
    FROM BIB_MASTER
    WHERE (((BIB_MASTER.BIB_ID) Not In (SELECT BIB_INDEX.[BIB_ID]
    FROM BIB_INDEX
    WHERE (((BIB_INDEX.INDEX_CODE)="0350")))));

    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
    WHERE (((BIB_INDEX.INDEX_CODE)="0359")
    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.

    Posted as is. If you need assistance in running custom SQL queries in Prepackaged Access Reports, consult the Voyager Customer Listserv.

     

     

     

     

    Report

     

     

     

    View article in the Exlibris Knowledge Center
    1. Back to top
      • Voyager to Alma Migration Query: Identify "Brief" Bib Records
      • Voyager to Alma Migration Query: Identify Bibliographic or MFHD records with typos at the beginning of the URL in the 856 field
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Community Content Type
      How To
      Product
      Voyager
    2. Tags
      This page has no tags.
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved