Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Z13-CALL-NO is z30_call_no_2 instead of z30_call_no

    Z13-CALL-NO is z30_call_no_2 instead of z30_call_no

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    Some of our records have both a z30_call_no and a z30_call_no_2. Specifying a PST or LOC expand for these, we find it's the z30_call_no_2 which is being put into the Z13-CALL-NO.

    We want the z30_call_no in the Z13-CALL-NO and the z30_call_no_2 in the Z13-USER-DEFINED-1. How can this be done?

    Resolution:
    Specify this in tab_expand:

    CREATE-Z13 expand_doc_bib_z30

    And then this in tab22:

    CALL-NO 1 Z30 3
    ....
    USER-DEF-1 1 Z30 9

    The ./xxx01/tab/expand_doc_bib_z30 shows you what subfield each z30 field is translated into for the purpose of this expand. For these we see:

    # z30-call-no 3 space X
    # z30-call-no-2 9 space X


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Z13-CALL-NO is blank
      • Z13u (Short Bibliographic Record) does not contain data defined for 461 field
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 18.01
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    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