[Koha-bugs] [Bug 25229] New: Elasticsearch should use the authid (record id) rather than the 001 when returning auth search results
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Tue Apr 21 15:38:37 CEST 2020
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25229
Bug ID: 25229
Summary: Elasticsearch should use the authid (record id) rather
than the 001 when returning auth search results
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5 - low
Component: MARC Authority data support
Assignee: koha-bugs at lists.koha-community.org
Reporter: nick at bywatersolutions.com
QA Contact: testopia at bugs.koha-community.org
To recreate:
0 - Have an environment with both ES and Zebra available
1 - Edit an authority record in the DB to force the 001 and the auth_id to be
different
update auth_header SET marcxml = REPLACE(marcxml,"1707","potato");
2 - Reindex Zebra and ES
3 - View the record in zebra (commands below work on kohadevbox sample data)
yaz-client unix:/var/run/koha/kohadev/authoritysocket
base authorities
find "computer program"
show 1+14
Note that the relevant record has the auth id in the 001 even though the
record doesn't
4 - View the record in Elasticsearch
curl -X GET 'localhost:9200/koha_kohadev_authorities/data/1707?pretty'
Note the 001 is indexed into local number, but the _id of the record
matches authid
5 - Search authorities in the staff client for "Computer prorgram" using Zebra
Note that you can find authid 1707 in the results and view it
6 - Switch search engine to ES and repeat
Note that you have a result that links to authid=potato and it doesn't work
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
More information about the Koha-bugs
mailing list