| Summary: | Normalization Rules set up in Record Matching Rules in Administration Module | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Kelly <training> |
| Component: | Documentation | Assignee: | Bugs List <koha-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | dch, dubyk |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Kelly
2019-07-12 17:33:25 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. 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"? 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. |