Ever since we brought up our system in 1994, INNOPAC's inability to
detect 0123456789 and 0123456789 (pbk.) as duplicates has baffled us.
Having said that I don't believe the ISBN is a reliable match point
for overlay - with apologies to people who have heard me say this
before. :-)
The most reliable way to overlay existing bib records is to use a
unique control number as the match key, e.g. bib record number, order
number or the bibliographic utility number (in many libraries using
OCLC records the 001 is the OCLC number). I don't know if there's any
way you can add a match key in the records you receive from BNB. If
you can it may be possible to have your load table tweaked to allow
overlay by one of the control numbers.
Since both the ISBN itself and any additional info such as (pbk.) are
in the same subfield (a), I don't think tweaking the load table will
strip out any extraneous information. I think that the known issue
about ISBN validation failure is not connected with the inability to
overlay records with extraneous information in the ISBN field.
On Thu, 17 Jan 2002, Catherine O'Sullivan wrote:
> I'm using FTS to load MARC21 records supplied from BNB. All the
> records exist in basic form in the system having been created at
> the acquistions stage. The problem I'm having is that the ISBN
> field will not overlay when it has extraneous information such as
> (pbk.) and/or price information. Out of a file of 91 records only 22
> have been overlaid which is a large amount of tinkering. I have
> seen that there is a known issue with ISBN validation failing with
> additional numerical information in this field but is there some way
> of forcing the overlay that I haven't found? I have found the manual
> of little help on this subject.
>
> I'm using m2btab.b and the ISBN is set to
> BIBLIOGRAPHIC ISBN/ISSN(i) 020-024 ALL
Mieko
-----
Mieko Yamaguchi [log in to unmask]
Technical Services Manager/System Coordinator +44 (0)1248 382970
Main Library, University of Wales Bangor, UK +44 (0)1248 382979 (Fax)
|