Bug 35485 - Error staging authority MARC record if a match is found
Summary: Error staging authority MARC record if a match is found
Status: RESOLVED DUPLICATE of bug 26611
Alias: None
Product: Koha
Classification: Unclassified
Component: Tools (show other bugs)
Version: Main
Hardware: All All
: P5 - low blocker (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-05 02:07 UTC by Aleisha Amohia
Modified: 2023-12-06 04:18 UTC (History)
0 users

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 Aleisha Amohia 2023-12-05 02:07:12 UTC
To reproduce:

1. Set up a record matching rule

Match threshold: 100
Record type: authority

Matchpoint 1:
Search index: local-number
Score: 100
Tag: 001

2. Create an authority record

3. Save the authority record in any format (maybe marcxml)

4. Go to Stage MARC for import in Cataloguing Home

5. Upload your downloaded MARC for the authority record. Set the following settings:

Record type: authority
Record matching rule: Your new 001 matching rule

6. Stage for import. Notice the job FAILS. There appears to be no useful error messages in logs, but the job results say '1 records not staged because of MARC error'
Comment 1 Aleisha Amohia 2023-12-05 02:12:51 UTC
Confirm we get this error in every version 22.05.x and above
Comment 2 Katrin Fischer 2023-12-05 20:50:24 UTC
Hi Aleisha, could this be bug 26611? Fixed in Backported to 22.05.x for upcoming 22.05.17 release.
Comment 3 Katrin Fischer 2023-12-05 20:51:05 UTC
(In reply to Katrin Fischer from comment #2)
> Hi Aleisha, could this be bug 26611? Fixed in Backported to 22.05.x for
> upcoming 22.05.17 release.

... no longer upcoming of course, I just copied the note from the other bug :)
Comment 4 Aleisha Amohia 2023-12-05 22:30:15 UTC
(In reply to Katrin Fischer from comment #2)
> Hi Aleisha, could this be bug 26611? Fixed in Backported to 22.05.x for
> upcoming 22.05.17 release.

Thanks Katrin but unfortunately I don't think it is. I get this error in all versions, including upstream/master.
Comment 5 Aleisha Amohia 2023-12-06 04:18:27 UTC
I'm not sure what I did differently but tested it again today and seems to work on upstream.

*** This bug has been marked as a duplicate of bug 26611 ***