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

    p_item_05 doesn't work for SuDocs (or other non-LC classifications)

     

    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

     

    Description:
    The item-05 Service does not work with other defined classifications.
    We ran a service with Superintendent of Documents Classification selected for Call No. Type and the output was empty.

    We also saw a message: "failed to access location index".

    Please indicate what configuration we have to complete to support lists based on any classification.


    Resolution:
    You have 462,000 type 3 (SuDocs) call numbers:

    abc50@ALEPH20> select count(*) from z30 where z30_call_no_key like '3%';
    **** Hit return to continue ****

    COUNT(*)
    ----------
    462398

    Almost all of these have z30_call_no_key's which include the initial "$$h":

    abc50@ALEPH20> select count(*) from z30 where z30_call_no_key like '3 $$h%';
    **** Hit return to continue ****

    COUNT(*)
    ----------
    462313


    Compare this to your LC call numbers (type "0"):

    abc50@ALEPH20> select count(*) from z30 where z30_call_no_key like '0 $$h%';
    **** Hit return to continue ****

    COUNT(*)
    ----------
    0


    The SuDocs records *can* be retrieved by p_item_05 -- if this "$$h" is included in front of the call number characters in the From-Key and To-Key parameters.

    The reason these z30_call_no_key's include the "$$h" is that your abc50 tab_filing_call_no has no routine specified for type "3"; p_item_06 (which does the initial build the z30_call_no_key) uses the default "#" routine: 

    # L add_call_no_type
    # L to_lower
    # L pack_spaces

    which lacks "del_subfield". {The type "0" (LC) includes it.} 

    I suggest that you make the tab_filing_call_no changes described in KB's 8192-3690 and 16384-43794, and then run p_item_06 to rebuild the z30_call_no_key's. Then you will not need to include the $$h in your call# ranges.

     

     


    • Article last edited: 12-Mar-2016
    • Was this article helpful?