Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    SEARCH: no SESSION_ID logged for z39.50 searches in OPAC_SEARCH_LOG

    • Article Type: General
    • Product: Voyager
    • Product Version: 7.2.1

    Description:
    Bug Report Form, Issue 16384-18673

    Module(s): Searching
    Release(s) replicated in: 7.0.1 - 8.1.1
    Last version without bug (if applicable): n/a

    Expected results: z39.50 searches would log a session ID in opac_search_log
    Actual results: z39.50 searches do not log a session ID or a search_type in the opac_search_log table. z39.50 connections spawn a new opacsvr process for those searches, and should log a session ID.

    Workflow implications: Presents a challenge to keeping accurate search statistics.

    Replication steps:
    Ensure opac search logging is enabled in the voyager.ini:
    LOGSEARCH=Y
    Conduct a z39.50 search on a Voyager database. Example:
    In Yaz client, after connecting, conducted the following searches:
    find cat
    find dog
    find bird
    Find the searches you conducted in the opac_search_log table. Note that session_id and search_type fields are empty.
    SQL> select search_date, session_id, search_type, search_string from opac_search_log
    2 where search_date like '13-JUN-12';

    SEARCH_DA SESSION_ID SEARCH_TYPE
    --------- ---------------- -------------------------
    SEARCH_STRING
    --------------------------------------------------------------------------------
    13-JUN-12
    "cat"

    13-JUN-12
    "dog"

    13-JUN-12
    "bird"

    Resolution:


    • Article last edited: 3/5/2015
    //doorbell.io feedback widged