Bug 21224 - Relator term in 100$e should not be used with Authority linker script
Summary: Relator term in 100$e should not be used with Authority linker script
Status: RESOLVED DUPLICATE of bug 21826
Alias: None
Product: Koha
Classification: Unclassified
Component: MARC Authority data support (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-14 20:25 UTC by Joy Nelson
Modified: 2020-04-08 18:01 UTC (History)
2 users (show)

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


Attachments
LOC PCC Guidelines for the Application of Relationship Designators in NACO Authority Records. http://loc.gov/aba/pcc/documents/OpCo-2016/PCCSCSSCTTFAuthRDsGuidelinesFinal20160412b.docx (34.51 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2018-08-14 20:25 UTC, Joy Nelson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joy Nelson 2018-08-14 20:25:07 UTC
Created attachment 77802 [details]
LOC PCC Guidelines for the Application of Relationship Designators in NACO Authority Records.   http://loc.gov/aba/pcc/documents/OpCo-2016/PCCSCSSCTTFAuthRDsGuidelinesFinal20160412b.docx

Subfield $e should not be used in Authority records.  It can (and should) be used in bibliographic records (RDA).  When the linker runs it will not match if the bib record has 100$e field and the authority does not.  The linker needs to ignore the $e in the bibliographic record and match on the other subfields only

Example the following bib marc tag
100\\$aSendak, Maurice $eauthor

should match the authority record with the following 100 tag.
100\\$aSendak, Maruice
Comment 1 Myka Kennedy Stephens 2019-12-11 22:32:02 UTC
With Elasticsearch enabled, I am finding that the linker is now successfully ignoring $e and matches to an existing authority record. I've been testing on master. The linker does have other issues, but I don't think this is an issue anymore -- at least not when Elasticsearch is enabled.

Would someone check with Zebra and then update the status? I hesitate to change the status of this bug in case it is still a problem with the linker + Zebra.
Comment 2 Phil Ringnalda 2020-04-08 18:01:16 UTC
Yes, it was fixed by bug 21826

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