Bug 23779 - Add sample matching rule for authority records on $1xx field matches
Summary: Add sample matching rule for authority records on $1xx field matches
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Tools (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-08 15:41 UTC by Cori Lynn Arnold
Modified: 2020-05-25 21:47 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Importing Auth Record Match options (74.87 KB, image/jpeg)
2019-10-08 15:41 UTC, Cori Lynn Arnold
Details
Example of a 1xx Rule (67.95 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2019-10-09 20:13 UTC, Cori Lynn Arnold
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cori Lynn Arnold 2019-10-08 15:41:38 UTC
Created attachment 93886 [details]
Importing Auth Record Match options

When you import authority records using Tools->Stage MARC records for import the options for checking duplicates are for ISBN , ISSN and KohaBiblio. However, those fields make no sense for checking auth duplications.
Comment 1 Cori Lynn Arnold 2019-10-08 15:42:24 UTC
It should _at least_ look for $1xx fields, but DGI would _love_ to have $001 control number field checking
Comment 2 Katrin Fischer 2019-10-08 20:30:00 UTC
Hi Cori,

the matching rules are fully configurable. The ones you listed below are just some samples that Koha adds out of the box as sample data during instalation. 

Have you tried adding your own? The only tricky bit is knowing the index name.

I found this helpful:
https://bywatersolutions.com/news/match-points-in-koha

I am changing to enhancement.
Comment 3 Cori Lynn Arnold 2019-10-09 19:48:16 UTC
Let me rephrase then, Koha should come out of the box with a sample matching record for 1xx fields for loading Authority Records.
Comment 4 Katrin Fischer 2019-10-09 19:51:58 UTC
(In reply to Cori Lynn Arnold from comment #3)
> Let me rephrase then, Koha should come out of the box with a sample matching
> record for 1xx fields for loading Authority Records.

Yes, I think that would make a lot of sense. It's just a bit more difficult than the standard rules. I think we would want something like:

Score: 50 points

Then 3 matchpoints for each 

100 = 50 points
110 = 50 points
111 = 50 points

So that each of those would make it reach the score needed to match.
Comment 5 Cori Lynn Arnold 2019-10-09 20:13:13 UTC
Created attachment 93941 [details]
Example of a 1xx Rule

Attached is an example of a working 1xx Matching Rule for Authorities
Comment 6 Katrin Fischer 2019-11-02 20:26:10 UTC
I am surprised that the rule attached is working, I would have expected it not to because the Search index information is empty - could it be that it's using the keyword index for matching in this case?
Comment 7 Cori Lynn Arnold 2019-11-13 13:49:10 UTC
(In reply to Katrin Fischer from comment #6)
> I am surprised that the rule attached is working, I would have expected it
> not to because the Search index information is empty - could it be that it's
> using the keyword index for matching in this case?

It does work. Should I add an index? If so, which one do you think?
Comment 8 Katrin Fischer 2020-05-25 21:47:54 UTC
(In reply to Cori Lynn Arnold from comment #7)
> (In reply to Katrin Fischer from comment #6)
> > I am surprised that the rule attached is working, I would have expected it
> > not to because the Search index information is empty - could it be that it's
> > using the keyword index for matching in this case?
> 
> It does work. Should I add an index? If so, which one do you think?

Hi Cori, sorry it took me so long. The indexing of authority records is a little bit of a mystery to me. We just had someone struggling with this on the German mailing list as well.

I believe indexes would be:

100 = Personal-name
110 = Corporate-name
111 = Meeting-name

As listed here:
http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=etc/zebradb/marc_defs/marc21/authorities/authority-koha-indexdefs.xml;h=39b46025f7b28e80c02081e9636be90dc764668e;hb=HEAD

If you get a chance and could try if adding these make a difference in your rule, I'd appreciate hearing about the results.