Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Redefining Patron Type

    Redefining Patron Type

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Description:
    We have an idea for changing the way that we use the Patron Type that we are thinking about for our Aleph 20 upgrade.

    Currently, the patron types that we use are essentially redundant with the patron status codes. E.g., Faculty have patron status 01 and patron type FA. Graduate students have patron status 04 and patron type GR. My understanding is that the patron type is present for statistical purposes, e.g., it is recorded in loan records, hold records, history files, etc. But I don't think it plays a functional role, e.g., whether a patron has certain privileges. Since we currently have a one-to-one mapping of statuses and types, we don't get any real value out of the types we currently have defined.

    The idea is to change to a small number of types to indicate which institution the user is affiliated with. That is, a Notre Dame faculty member would have status 01 and type ND, while a Saint Mary's faculty member would have status 01 and type SM. A Notre Dame Grad Student would then have status 04 and type ND.

    Do you have any thoughts on this in general? Are there issues that we would need to address? Also, the only table where I've found setting for this is pc_tab_exp_field_extended.eng. Are there any other tables, or configuration that I need to be aware of?

    Resolution:
    Some multi-ADM sites assign a unique prefix in the util g/2 last-bor-id (the Aleph-assigned patron ID) for each xxx50 library (such as "NDU" in ndu50, "SMC" in smc50, etc.) If you were starting from scratch, that might be a good idea, but changing this for existing patrons is not really feasible -- so, yes, I think that setting the patron type to represent the college would be a good idea.

    You write: "My understanding is that the patron type is present for statistical purposes, e.g., it is recorded in loan records, hold records, history files, etc."

    The following grep shows the Oracle records the BOR-TYPE is found in:

    barnabas.library.nd.edu-18(1) HCC50-ALEPH18>>grep BOR-TYPE Z*
    Z305: 02 Z305-BOR-TYPE PICTURE X(2).
    Z35: 02 Z35-BOR-TYPE PICTURE X(2).
    Z36: 02 Z36-BOR-TYPE PICTURE X(2).
    Z36H: 02 Z36H-BOR-TYPE PICTURE X(2).

    The Z35 is the central record for circ statistics, so its inclusion there is the critical piece.

    pc_tab_exp_field_extended.eng is the only Aleph table you need to change for these new BOR-TYPE values.


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Recreating Z103 records in BIB library only
      • Redirect from http to https breaks RESTful API: "Document is empty"
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 20
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved