• Product: Aleph
• Product Version: 20, 21, 22, 23
• Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

Problem Symptoms:
* A patron's hold request triggers a recall though it shouldn't
* There are old patron records (z305) having a different borrower status

Can the old z305 be deleted without deleting the patron's loans or cause any other problems?
Example 
Old z305:
z305_rec_key=PID000000112
z305_last_update_date='19990226'
z305_expiry_date=20020201
z305_bor_status='02'    This gives the patron the wrong privileges
z305_last_activity_date='00000000'

New z305 (the one shown in the GUI):
z305_rec_key=PID000000112XXX50
z305_last_update_date='20121101'

z305_expiry_date='20141002'
z305_bor_status='14'    Correct privileges
z305_last_activity_date='20121101'

Cause:
Old patron records contain wrong borrower status

Resolution:
* patrons without sublibrary are not in use and can be deleted

Example
885 occurrences of z305 records having blank (' ') instead of valid sublibrary
xxx50@ALEPH18> select distinct(substr(z305_rec_key,13,5)),count(*) from z305
2 group by substr(z305_rec_key,13,5);
**** Hit return to continue ****

(SUBSTR(Z305_REC_KEY COUNT(*)
-------------------- ----------
885
RBRIK 759
RIK50 14095
RRRIK 29

NOTE: There is no service to remove these patrons automatically. If you delete the patrons outside of Aleph, please make sure to export the relevant table (p_file_03 for z305) and update the tables when no one accesses these tables (use aleph_shutdown to ensure this).
 

• Article last edited: 17-Jun-2016