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

    tab_suf_lib, tab_suf_default, tab_suf_bor_defaults, tab_suf_bor_stats

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

    I see mentions of tab_suf_lib in the log files. Searches of the documentation portal have references to tab_suf_lib, tab_suf_default, tab_suf_bor_defaults, and in version 18 tab_suf_bor_stats. I do not find any mention of these tables in version 17 documentation. Also the little documentation on the tables that there is, does not seem to fully explain their uses and what we need to do to configure or not configure them. Could you enlighten me on their use in our multi-adm setup?

    The SUF ("Shared User File") function is described in 16.02 rep_ver 6081:

    Description: Implementation of Shared Users File (SUF)

    The objective of the Shared Users File is to provide "just-in-case" user records for a group of libraries that agrees to share patron registration and information. When a user-id is input for the "request" function in the WEB OPAC, or when a user-id is input in the CIRC client, if the user is registered at any one of the libraries in the group, but not in the specific library, a user record is system-generated and added to the library's Oracle user database.

    In effect, this means that a user that is registered at any one of the libraries in the group can have privileges at all the libraries. In actual fact, users can be marked as "non-shared", in which case a user record will not be automatically generated.

    In addition, updating a user record at one library causes the record to be updated at all libraries.

    To activate this development you must add 2 flags to ./alephe/aleph_start:

    setenv suf_support Y
    setenv suf_library USR01

    Additional Information

    tab_suf_lib, shared user file

    • Article last edited: 10/8/2013
    • Was this article helpful?