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

    Call-slip & hold-request-slip forms; creating customized hold-slip-request form

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

    What forms are used in printing call slips and hold request slips? (We don't do hold requests; to us, the request slip is a "call slip".)

    How would we create a customized form?

    Request slips are printed by the ue_06 request daemon and by the p_cir_12 GUI Service. (See KB 3925 for a comparison of the two.)

    The hol-order-slip.xsl form, though having the title "Call Slip", is used only by the Cataloging print function and is *not* the form printed by ue_06 in filling a request.

    The form which ue_06 uses when the item is not available is hold-request-wait.xsl; in the case where the item *is* available it uses hold-request-slip.xsl.

    A site can create customized versions of hold-request-slip.xsl with "-nn" suffixes: hold-request-slip-00.xsl, hold-request-slip-01.xsl, etc.

    Which hold-request-slip-nn form is used by ue_06 is controlled by column 9 ("Format number of hold slip template") in the ./abc50/tab/tab39.

    Similarly, the p_cir_12 GUI submission screen has a "Call Slip Format" option which can be used to specify 00, 01, etc., in order to control the form used.

    Note that when a hold-request-slip-nn.xsl form is changed you *must* do util i/6 *and* stop/restart ue_06, and when tab39 is changed you must restart the pc_server and stop/restart ue_06.

    Note: a form can also be included in the ./abc50/tab/form_print_method, with a particular Form Format in column 2. You should also check for the form in form_print_method.

    If Aleph can’t find the customized report, say, “hold-request-slip-00.xsl”, because it was deleted or renamed, Aleph will revert to the base report, “hold-request-slip.xsl”. On the other hand, if you modify the base report, say, “hold-request-slip.xsl” and somehow a new report called “hold-request-slip-00.xsl” gets created (via XSL creator or otherwise), and if tab39 /col. 9 has “00”, the new file (that ends with “-00”) will get used the next time Util I / 6 and Util E / 6 are run. NOTE: if this new file (“-00”) gets created and Util I / 6 and Util E / 6 are not run for say one month, it will be at that time that Aleph picks up the new (“-00”) file.

    · If you change the customized report (or call slip) and save it as “hold-request-slip-10.xsl”, in addition to running Util I / 6 and Util E / 6, you also have to modify the corresponding GUI reports to point to the new customized report. See the article " Customization of pc_b_eng and error_eng files in version 17-up **MASTER RECORD** " (KB 8192-824) for a description of this process.

    Since the XML file is stored in the a-tree pc_b_eng, you have to copy it to the u-tree pc_b_eng:

    o $ pcb
    o $ mkdir /opt/exlibris/aleph/u20_1/alephe/pc_b_eng
    o $ cp p-cir-12.xml /opt/exlibris/aleph/u20_1/alephe/pc_b_eng/
    o $ vi p-cir-12.xml

    o Look for the <control> <argname> and <label> tags that refer to the report in question, and then change the <default> tag to “10” or whatever your custom form is. Also, change the <value> and <display> tags under <cbitem> to match your new custom report.

    o You don’t need to do anything other than restart the PC server for Aleph to pick up this change.

    o For example:
    <label>Call Slip Format</label>
    <display>CHD Custom Call Slip</display>

    • Article last edited: 10/8/2013