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

Description:
We discovered today that over 1500 of our patron records have the Patron Address, Patron Status, Patron Email and Expiration Date fields checked as protected. We don't think we could have accidentally done that to so many records. What processes, besides manually updating the patron record in Circulation, can set these fields? Can the p_file_20 PLIF loader itself set those fields as protected?

Resolution:
p_file_20 does not update the Z303-PLIF-MODIFICATION fields.

It is most likely that this field was set by the Z303-PLIF-MODIFICATION line in the $usr_library/tab_fast_patron_register at the time the patron was created. On your server, this is:
Z303-PLIF-MODIFICATION=A B D E

If you want to allow update of all of these fields by the PLIF, you should change it to blank:
Z303-PLIF-MODIFICATION=

See Support Knowledge Base record 4941 for more information.

(keywords: faq p-file-20 file_20)

• Article last edited: 10/8/2013