Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    xxx50 tab_filing_call_no does not produce correct LC sort

    • Article Type: General
    • Product: Aleph
    • Product Version: 17.01

    Description:
    The distributed 16.02, 17.01, etc., usm50 tab_filing_call_no does not produce a correct LC sort. The lc_call_no routine should be inserting special characters -- ! # " -- to create a correct sort.

    This SQL shows that it is not:
    SQL-USM50> select z30_call_no_key from z30 where z30_call_no_type = '0';

    This is happening because the distributed ./usm50/tab/tab_call_no_key has the add_call_no_type line before the lc_call_no line. The addition of "0" in front of the number causes the lc_call_no filing routine to not work.

    **The distributed ./usm50/tab/tab_filing_call_no table needs to changed so that the

    0 L add_call_no_type

    line is *after* the

    0 L lc_call_no

    line.**

    Resolution:
    This is corrected in the version 18 usm50 tab_filing_call_no:

    0 L del_subfield
    0 L to_blank &()-[]<>?,/:
    0 L lc_call_no
    0 L add_call_no_type
    0 L pack_spaces

    Additional Information

    usm50, 16.02, filing, call number


    • Article last edited: 10/8/2013