Thanks everyone.

Encouraged by your successes I was not getting a match on the 010$a but noticed the contents had at least one space in it.
I set up a test record without any spaces and found it is matching now.

So it may be the index definitions for the 010$a in authorities that needs to allow for phrase or it may be that the 010$a should always have no spaces (or other white space).

For those that are using the 010$a can anyone say if they know if any of their 010$a have space(s) in them? The example I had been using was:

"n  81032458 "
That is two spaces after the "n" and one at the end.

Many thanks. It may be we need to change the contents of the 010$a to exclude spaces and on the import too.

Thanks again.
Ian
On 22/12/2015 17:19, Hillyard, Cecil wrote:
We use this a lot to download batches of authority records from SkyRiver

In Record Matching rules:

Match points: Match point 1
        Search index: LC-card-number
        Score:  1000
Matchpoint components
        Tag: 010
        Subfield:s a
        Offset: 0
        Length: 0

You just have to make sure that your current records do have 010s to match on.

__________________
Cecil Hillyard
Washoe County Library
Techinical Services
775-327-8338

-----Original Message-----
From: Koha [mailto:[email protected]] On Behalf Of Tomas Cohen 
Arazi
Sent: Tuesday, December 22, 2015 8:50 AM
To: Christopher Davis
Cc: Koha
Subject: Re: [Koha] Staging and matching authority records

Chris, we had trouble getting a matching rule for authorities. We ended up 
using the 001 field I recall. It makes use of the Zebra indexes, so it is 
important that you put the right one.

2015-12-22 13:40 GMT-03:00 Christopher Davis <[email protected]>:

Ian,

Joy's correct, while MARC authority records can have ISBNs, they
typically do not. Sorry to lead you astray :-$

--

Christopher Davis, MLS
Systems & E-Services Librarian
Uintah County Library
[email protected]
(435) 789-0091 ext.261
uintahlibrary.org
basinlibraries.org
facebook.com/uintahcountylibrary


On Tue, Dec 22, 2015 at 9:29 AM, Joy Nelson <[email protected]>
wrote:
Ian-
If you have the matching rule set up to match on the 010 subfield a
using the LC-cardnumber index, then the matching should happen if 1.
your authority records are indexed 2. you have 010$a in your
existing records AND in the incoming records
(and
matches do exist).

(I'm assuming here that you've also specified the incoming file is
an authority file, not a bibliographic file. )

I'm not sure that using a 020 will assist you in matching as that is
a bibliographic tag, not an authority tag.  And I do not believe the
020 is indexed for authority records.  A tag must be indexed in
order to be
used as
a match point.

When troubleshooting, I generally find a record I know should match
and
then
look at the 010$a in the incoming file and existing record to see if
there
is anything that would potentially cause the match to fail.

-Joy


On Tue, Dec 22, 2015 at 9:22 AM, Christopher Davis <
[email protected]>
wrote:
Ian,

Off the top of my head, I thought that you might want to tried
adding MARC authority field 020 (ISBN) as a match point to your
matching point rule? Not every MARC authority record will have a
LCCN (although most do).

Good luck and Merry Christmas,

Christopher Davis, MLS
Systems & E-Services Librarian
Uintah County Library
[email protected]
(435) 789-0091 ext.261
uintahlibrary.org
basinlibraries.org
facebook.com/uintahcountylibrary


On Tue, Dec 22, 2015 at 9:06 AM, Ian Bays
<[email protected]>
wrote:
Hi.

We are trying to stage some authority records to match existing
authority records to overlay them.
We have used the matching for bibliographic records successfully
before
but
are having difficulty with matching authority records.
The version of Koha is 3.20.01.000 and we are MARC21 using dom
indexing
and
icu chains.

Before getting into the details, can I ask if anyone has any
experience
of
matching authorities (staging and managing) with any success?

We are trying to match on the 010$a and looking at the matching
rules documentation in:


http://manual.koha-community.org/3.20/en/catadmin.html#recordmatchingr
ules
Thanks in advance.

Ian

--
Ian Bays
Director of Projects, PTFS Europe Limited Content Management and
Library Solutions

_______________________________________________
Koha mailing list  http://koha-community.org
[email protected]
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list  http://koha-community.org
[email protected]
https://lists.katipo.co.nz/mailman/listinfo/koha



--
Joy Nelson
Director of Migrations

ByWater Solutions
Support and Consulting for Open Source Software
Office: Fort Worth, TX
Phone/Fax (888)900-8944
What is Koha?

_______________________________________________
Koha mailing list  http://koha-community.org [email protected]
https://lists.katipo.co.nz/mailman/listinfo/koha





--
Ian Bays
Director of Projects, PTFS Europe Limited
Content Management and Library Solutions
+44 (0) 800 756 6803 (phone)
+44 (0) 7774 995297 (mobile)
+44 (0) 800 756 6384 (fax)
skype: ian.bays
email: [email protected]

_______________________________________________
Koha mailing list  http://koha-community.org
[email protected]
https://lists.katipo.co.nz/mailman/listinfo/koha

Reply via email to