Have you checked the overlay setting for your patron
barcode in M,I,C,M -> PATRON record (m2btab.p) ->
D (DATA not overlaid)?
Our setting for the patron barcode is P BARCODE(b(:k)).
This tells the load software to replace any existing
barcode with an incoming barcode, add an incoming
barcode if the target patron does not contain a barcode
and retain any existing barcode if an incoming record
does not contain a barcode.
The setting you want would be P BARCODE(b(:d)), though
if the barcode for a particular patron is always the
same in the records from your admin dept, it doesn't
matter whether the setting is (b(:k)) or (b(:d)).
With this setting any existing barcode is retained
whether an incoming record contains a barcode or not,
and a barcode in the incoming record is added only if
the target record does not contain a barcode. If both
the target and the incoming records contain a barcode,
the incoming barcode is discarded.
It sounds like your load table has been set up with the
protection P BARCODE(b). With this setting any barcode
in the target record is always retained and a barcode in
the incoming record is added as a duplicate barcode.
Well, that's the theory. If your overlay protection
setting is either P BARCODE(b(:k)) or P BARCODE(b(:d))
and barcodes are duplicated, then there may be something
seriously wrong with your patron load table.
> Just wondered if anyone else had experienced problems
with the automatic
> creation of duplicate patron barcodes as partially
described below.
> We import our student patron records from "Academic
Affairs", a Keele admin.
> dept. Whereas other data changes are overlaid
correctly, the patron barcode
> field, which does not require updating, is being
duplicated in a new field.
> When a reader wishes to place a hold for example,
Innopac goes into a tizz
> as it does not know which of the duplicate p.barcodes
to select!
> Malcolm Taggart, Keele
Mieko
-----
Mieko Yamaguchi
University of Wales Bangor
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|