Local patron records created automatically in other (ADM) libraries
- Product: Aleph
- Product Version: 20, 21, 22, 23
- Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care
Description
In our multi-adm setup, with xxx50, xxx51, and xxx52 libraries, when a new Global and Local patron record is created in xxx50, and we then go to look at this new patron in xxx51, we find that there's an XXX51 record in the Local Patron list. (Same with xxx52.)
Why is the system creating Local Patron records for these other libraries when all we want is the single record in xxx50?
Resolution
We see that the "XXX51" line in the xxx51 Local Patron List has no values in the Patron Status, Description, etc., columns. This means that it does not actually exist; it's just a potential. If you check the xxx51 z305 for this Aleph patron number, you will see that there isn't any.
These potential Local Patron records should just be ignored.
- Article last edited: 16-Aug-2016