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

Description:
An OPAC user is put into the wrong base. Why?

Resolution:
The base used is determined by the z61_base value of the z61 profile record.

The z61 profile used is determined by the ./com/get_bor_profile program, using the following logic:

If the user is logged on:

Is there a individual z61_rec_key for the patron ID? If so, use it.

Is there a z61_rec_key for the z303_profile_id? If so, use it. (Does the z303 record for this user have a correct value for the z303_profile_id?)

Is there a z61_rec_key for the patron's IP address? If so, use it.

If none of the above, use the z61 with the z61_rec_key "ALEPH" (the default).

If the user is not logged on:

Is there a z61_rec_key for the patron's IP address? If so, use it.

If not, use the z61 with the z61_rec_key "ALEPH" (the default).

Once you have determined which z61 profile is being used ... Does the z61 profile have a correct z61_base value?
select Z61_REC_KEY, Z61_BASE from z61 where Z61_REC_KEY LIKE 'ALEPH%';

Also, does the http://... at the top of the screen have a &local_base parameter? If so, this base will be used instead of the z61_base. The &local_base parameter is added in the ./www_f_eng html file when the user selects a particular base.

Note: It seems that the aleph_start www_base parameter is sometimes used instead of the preceding; see KB 16384-39314. You should set both.

• Article last edited: 10/8/2013