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. Knowledge Articles
    4. Voyager Headings Change Queue tables

    Voyager Headings Change Queue tables

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Question
    2. Answer
    3. Additional Information
      1. HEADING_CHANGE_QUEUE table
    • Product: Voyager
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

     

    Question

    What are the Headings Change Queue tables.

    Answer

    There are three tables related to changed headings:

    1. The HEADING_CHANGE_QUEUE table identifies authority records whose 1XX fields have changed.  This table is the entry point to use when searching for information about changed headings.  For each authority record whose heading has changed, there is one entry in this table for each of the authority record’s entries in the HEADING table. This table is populated automatically when applicable changes are made to authority records.

    In other words, this table has a row for each entry in the change queue.1

    1. The HEADING_CHANGE_FIELDS table has a row for each BIB record to be changed. This table is populated by running Catjob 12
       
    2. The HEADING_CHANGE table links HEADING_CHANGE_FIELDS and HEADING_CHANGE_QUEUE. This table is populated by running Catjob 11.

     

    1In some situations the data in the tables will not correctly reflect the what appears in the Cataloging Client's Global Headings Change Queue.  These "orphan Rows" in one or more of the tables will not appear in the change queue. Contact Support to have "orphan rows" removed from the tables.

    Additional Information

    HEADING_CHANGE_QUEUE table

     

    • CHANGE_DATE (date). The date on which the 1XX field in the authority record changed.
    • HEADING_ID_NEW (number). The HEADING_ID from the HEADING table for the entry for the current version of the authority record’s 1XX field.
    • HEADING_ID_OLD (number). The HEADING_ID from the HEADING table for the entry for the previous version of the authority record’s 1XX field.
    • HEADING_QUEUE_ID (number). A sequential number assigned by Voyager to every entry in the queue. Used to link to the other heading change tables.
    • INDEX_TYPE (1 character). The INDEX_TYPE code from the HEADING table.
    • PROCESS_FLAG (1 character). This is obsolete and no longer used. Use instead HEADING_CHANGE.PROCESS_FLAG (where value changes from N to Y when a heading is marked for processing in the queue).
    • REC_ID (number). AUTH_ID
    • REC_TYPE (1 character). A code (‘H’ or ‘S’) that indicates whether the authority record represents a heading (beginning with subfield |a) or a subdivision
       

    • Article last edited: 02-Sept-2021
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Voyager Gobal Data Change replace part of a string
      • Voyager hold shelf expiration date and library closed days
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      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