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

    Defining Google Book Search to display 776 and 020

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

    Desired Outcome Goal:
    Define Aleph tables properly for the Google Book Search API (-- which is set to search on 'isbn' in full-set-tail-xxxx).
    Since, for ebooks, the isbn is most accurately located in the 776$z, it should look for that first. Then the 020.

    Procedure:
    1. When a column is being *added* to xxx01 $data_tab/www_tab_short.eng it also needs to be added to $alephe_root/www_f_eng/short-a-tail-xxxx and ./short-a-body-xxxx.

    2. In regard to the use of particular subfield(s) for a particular field, www_tab_short.eng column 8 is the Edit_field Identifier. Add lines such as the following to edit_field.eng:

    1 # 776## A
    2 z A ^


    1 # 020## A

    2 # A ^

    3. The full display is controlled by xxx01 $data_tab/edit_doc_999.eng. Add a line such as the following to use the entry you created in ./edit_field.eng for #2 above (and display just the subfield "z").
    (The "A" in column 6 is the edit_field Identifier.)

    ## 7760# A LLinking notes Y E W

    Additional Information

    edit_doc_999 does not have the ability that www_tab_short does, to look first for a 776 field and, if not found, an 020 field: if both are present, they will both display. But if the 776 is first, the user should see that first....

    Category: Web OPAC (500)


    • Article last edited: 10/8/2013