Description

Our PLIF records are specifying the Aleph patron number (z308 ID type 00) as the match-point.  As shown by the following SQL, there are many cases where multiple z303 records have been generated for the same patron name:

> s+ [usr_library]
SQL> select z303_name, z303_rec_key from z303 where z303_name in (select z303_name from z303 group by z303_name having count(*) > 1);

Resolution

If there are multiple patrons with the same name, these z303's could represent records which have been (correctly) created for different patrons.   If the tab100 CHECK-UNIQUE-NAME-BIRTH is set to "Y" and the z303_birthdate field is populated, these should *definitely* represent records correctly created for different patrons.

Otherwise, incorrect duplicates could be generated by 
 * file-20 in cases where the input record specifies an incorrect match-point:  no match will be found and the system will create a new z303, etc., for the patron with the z303_rec_key specified in the input file as the patron ID. Or
 * manually in the GUI, if the staff member fails to match properly on the existing z308 type 00 ID.

The cir-23 Service can be used to delete particular Aleph patron IDs.  It will *not* delete patron record numbers which have items on loan and, unless an override is specified, it will not delete patrons with fine records or hold requests.
 

See also, the article How to locate duplicate patron records .

• Article last edited: 06-Sep-2016