Bug 23311 - Normalization Rules set up in Record Matching Rules in Administration Module
Summary: Normalization Rules set up in Record Matching Rules in Administration Module
Status: RESOLVED MOVED
Alias: None
Product: Koha
Classification: Unclassified
Component: Documentation (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-07-12 17:33 UTC by Kelly
Modified: 2020-11-17 20:06 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kelly 2019-07-12 17:33:25 UTC
Currently, when researching Record Matching Rules in the 18.11 Koha Manual, the manual defines the Normalization Rules as:

“Koha only has one ‘Normalization rule’ that removes extra characters such as commas and semicolons. The value you enter in this field is irrelevant to the normalization process.”

However, currently, there are 4 options for Normalization Rules: remove spaces, upper case, lower case and Legacy Default.  

It would be helpful if these normalization rules were clarified in the manual for users. For example What does it mean Legacy Default? What does Uppercase mean?
Comment 1 Daphne Hoolahan 2020-07-17 13:51:55 UTC
There is new information in the 20.05 documentation advising you to use the Normalization rule: Control-number so I'm guessing that's a new normalization rule.
It would also be good to have an example of a rule for Authority records.
Comment 2 Katrin Fischer 2020-07-18 13:16:44 UTC
Hi Daphne,

I found this:
https://koha-community.org/manual/20.05/en/html/administration.html?highlight=normalization#adding-matching-rules

Koha only has one ‘Normalization rule’ that removes extra characters such as commas and semicolons. The value you enter in this field is irrelevant to the normalization process.

Can you share where you saw the information about "Control-number"?
Comment 3 Katrin Fischer 2020-07-18 14:32:54 UTC
Hi Daphne, 

adding "Control-number" to normalization rule in the past did not hurt, but didn't do anything either as far as I can tell. 

In the back of my mind I seem to remember talking to Nicole about our matching rule (we use 001 for the union catalog imports), and as we did have that entry in the past, I think this is how it ended up in the manual.

I've tried to add any information I could find to the manual and have updated the screenshots:

https://gitlab.com/koha-community/koha-manual/-/merge_requests/372

I hope this can help a little bit.