Invalid patron status when borrower sublibrary other than "ALEPH" is specified.

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

Description:
We are on version 17.01. When setting up patrons, we applied the sublibrary ALEPH, in the local patron record, as per the instructions of the ALEPH implementation staff. I'm assuming that using ALEPH allows patrons to use any sublibrary. However, now we want to set up a few patrons with a different sublibrary status (e.g. VOLU or WERC) and limit their activity to those sublibraries. When we try to do this, we find that all of our patron statuses are considered invalid with these sublibraries, not just patron status 12.

Resolution:
Applying the ALEPH sublibrary in the local patron record is fine. Since there are values in usm50/tab/tab31 [patron status definition table] for both the ALEPH **and** usm50 sublibraries – regardless of whether you choose “ALEPH” or “USM50” both local patron records will be created.

Patron statuses defined in the ALEPH sublibrary could *potentially* have permissions in any sublibrary; but this is determined by tab16 [loans, due dates, renewal limits] not tab31. For example, if a patron status (i.e. 12) can borrow from WERC but not from VOLU, you would still allow LOAN=Y in tab31 then use tab16 to define on a sublibrary-by-sublibrary basis when/what/where he can/cannot loan in specific situations.

Because of tab16, there is no need to define loan privileges at the sublibrary level in tab31; you can limit their activities per sublibrary in tab16.

All of your patron statuses are considered invalid at the sublibrary level because they were not defined that way in tab31 (they are only defined at the ALEPH and usm50 level).

• Article last edited: 10/8/2013