Skip to main content
ExLibris

  • Subscribe by RSS
    • Aleph
    Ex Libris Knowledge Center

    Why patron ID "SCRyyyymmdd" in z309, z36h, etc., records

    1. Last updated
      00:01, 29 Jan 2016
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23

    Description:
    Working on our annual fiscal year circulation stats reports, we have come across numerous entries in the Z309 table where the Z309_rec_key has  SCRyyyymmdd + Z309-SEQUENCE instead of a patron ID + Z309-SEQUENCE.  Please clarify why Aleph is writing these records in this format?

    I expect to see a Z309_rec_key made up of a valid Patron ID + the Z309-SEQUENCE and I don't know how to interpret these records.

    Resolution:
    As described in the Help for the p_cir_32 ("Remove Patron IDs") service, p_cir_32 replaces the patron ID in historical records (z35, z36h, z37h, z309, etc.) with "SCRyyyymmdd", where yyyymmdd is the execution date. (The "SCR" comes from "scrubbed".)

    This is done for reasons of patron privacy.

     

    For certain records containing the patron ID (such ​as the above), the delete_bor_total program (invoked when a patron is deleted in the GUI or by the cir-23 or file-20 Services) also changes the patron ID to "SCRyyyymmdd" rather than deleting the record.  

    For the purposes of annual fiscal year circulation stats reports, the actual patron ID should not be a factor and the change to SCRyyyymmdd should not be a barrier to gathering accurate statistics.

    • Article last edited: 1/28/2016