Z353 entries not getting created when adding new patrons

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

Description:
With our upgrade from version 17 to version 18 we have encountered a problem where when we add a patron the only entries that are created in the Z353 table are the global entries. In version 17 we had global and local entries. The problem is that if you have the 'Display Local Patrons Only' box checked in the Patron List you do not see entries for the newly created patron even though they have a Z305 record in your ADM.

The original Z353 table was built in version 17 when the Z305 records were all stored in the SYS50 library. p_cir_25 was run in each individual ADM to create the original Z353 entries. In version 17 the Z353 table was updated whenever a patron was updated, deleted, or added. This included entries for the global level and local level, normally 6 entries per patron. In version 18 the only entries that are getting created are the entries for the ALEPH level. The entries for the ADM Z305 records are not getting created.

Additional note: If I delete the ADM Z305 record that entries for that ADM record get deleted from the Z353 table. If I delete the ALEPH level Z305 it has no effect on the Z353 table, the patron is still visable in the browse list.

So, what do we have set up incorrectly? How are we supposed to get the Z353 entries created on new patrons?

More: I had a patron that had only a local ICC50 Z305 record and no ALEPH level z305 record. They were showing up with the 'Local patron' box checked. I added an ALEPH level Z305 and they were no longer a local patron. The update of the Z353 table with the ALEPH level information caused the ICC50 entries to be wiped out.

Resolution:
ALEPH z353's are being created and no xxx50 z353's are being created. This means that if you have the 'Display Local Patrons Only' box checked in the Patron List you do not see entries for a newly created patron even though they have a Z305 record in your ADM.

I found that this was because the site had user_list_aleph_local set to "N". Changing user_list_aleph_local to "Y" corrected the problem.

The use of the user_list_aleph_local has changed in version 18. The System Librarian’ Guide - Circulation has been changed as follows (on page 63) to reflect this:

BorrowersOnly=N
Defines if the "Display Local Patron Only" check box in the Patron List is selected by default:

• If set to Y, only patrons with at least one local record are displayed.
Whether or not patrons whose only local record is ALEPH are
displayed depends on the setup of the user_list_aleph_local parameter
in pc_server_defaults.

• If set to N, all patrons are displayed.

changed to:

BorrowersOnly=N
Defines if the "Display Local Patron Only" check box in the Patron List is selected by default:

• If set to Y, only patrons with at least one local record are displayed.

• If set to N, all patrons are displayed.


And page 74 of the same doc changed from:

setenv user_list_aleph_local
Defines whether the "ALEPH" patron is to be considered a Local Patron or not.
Possible values:
• Y - ALEPH is considered a local patron.
• N - ALEPH is not considered a local patron.
If set to N, patrons whose only Z305 local patron record is the ALEPH record, will
not be displayed in the Patron List if the checkbox "Display Local Patron Only" is

to:

setenv user_list_aleph_local

In version 18-up, setenv user_list_aleph_local should always be set to “Y”.

• Article last edited: 10/8/2013