https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17511 --- Comment #34 from Johanna Räisä <johanna.raisa@koha-suomi.fi> --- (In reply to David Cook from comment #30)
(In reply to Johanna Räisä from comment #28)
Have to think how the URI would work with indexing.
I have been thinking about the same thing.
At a glance, with Zebra we're using Koha-Auth-Number with a "w" register, which is fine for integers, but that probably won't work very well with URIs, since it's for storing "words". It's normalized and tokenized. That will lead to problematic indexing.
We could use a "p" register which is normalized and not tokenized but it's possible for 2 different URIs to be normalized into the same data, so that's not ideal either.
Perhaps we should use a "0" register which is not normalized and not tokenized. To use that we'd need to use the 4=3 structure attribute and I don't think we'd be using it as the Bib-1 spec says it should be used (https://www.loc.gov/z3950/agency/bib1.html), but I think it would work with Zebra. I'd have to try it out though.
This sounds good to me, although I have little experience configuring Zebra.
Technically, the is a special "u" register for URLs, but we also need to optionally store integers, so that won't work either.
I don't use Elasticsearch, so I can't speak to it.
I can look Elasticsearch. I have work with it more than I have worked with Zebra. Maybe we should make another bug for this? At least I think this is another enhancement. -- You are receiving this mail because: You are watching all bug changes.