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

Description:
We run our PLIF load twice a year, at the beginning of Fall and Spring Semesters. During the fall we noticed that the fields we wanted protected in the ACTIONs were protected in the ABC50 but were altered in the Local patrons. Is there something we should be doing to extend this to the Locals?

Is there a way to batch check the check boxes in the Global Patron "Patron Loader Protected Fields? And by checking these boxes does that protect patron status in the local patrons?

Resolution:
The z303_plif_modification values display as checkboxes in the GUI Circ Global Patron screen. The values are:

A = Do not modify the borrower’s address records (Z304).
B = Do not modify the borrower’s status (Z305-BOR-STATUS).
D = Do not modify the borrower’s expiry date (Z305-EXPIRY-DATE).
E = Do not modify the borrower’s e-mail address (Z304-EMAIL-ADDRESS) in the address record (Z304). Or
1 = Do not modify all borrower’s records (Z303, Z304, Z305 and Z308).

It seems that the field which you are trying to protect is the z305_bor_status (which appears in the Local Patron
Information as the "Patron Status"). Is that correct?

If so, then your choices are to have "1" ("Complete Record") or "B" ("Patron status") set.

p_file_20 is not able to update the z303_plif_modification field.

You can set the Z303-PLIF-MODIFICATION for GUI-created patrons in tab_fast_patron_register, but the z303_plif_modification in a PLIF-created record is blank.

If you want to prevent the update of the z305_bor_status by p_file_20 for PLIF-created records, the only way to do this (aside from checking the box for each patron in the GUI Circ) is to use SQL to update the z303_plif_modification. The values are separated by space, for example, "B E".

Note: You should be sure to back up the z303 table before doing any SQL update.

• Article last edited: 10/8/2013