The latter is something we’ve never had clear access to in Zebra.
The former replaces the search index documentation from the Koha manual. This is where Koha shows you which parts of your MARC records get indexed for searching and then how those search indexes are weighted for use in relevancy ranking of search results. Once you’ve switched to Elastic, you’ll see a new link in the Catalog section of Administration: Search Engine Configuration. So a search for "bram stoker dracula" would not find the novel (as "bram stoker" is in the author and "dracula" is in the title), but might find you the 1992 film titled Bram Stoker's Dracula. More specifically, on Elastic 6 and later, if ElasticsearchCrossFields is turned off, Koha will look for all of your search terms in all of your search indices, but only return titles where all of your terms were in the same index. If your Koha system using Elastic 6 or later, you need the ElasticsearchCrossFields system preference to be set to "Enable." Otherwise keyword searches will return inaccurate results. If your Koha system is using Elastic 5 or earlier, you need the ElasticsearchCrossFields system preference to be set to "Disable." Otherwise, all searches will fail.
All ByWater partner libraries currently using Elastic are using Elastic 6. You can see your Elastic version in the About Koha page of your staff client. Currently, Koha is capable of using either version of Elastic. This system preference was created in response to a change between Elastic versions 5 and 6. The ElasticsearchCrossFields system preference That means switching back to Elastic requires a little extra work on the server end that we can take care of for you. If you do switch back to Zebra, Elastic will not continue to keep itself updated while you use Zebra. That means that one could use the system preference to go back to Zebra at any time - though we’d generally prefer that you didn’t, as we’d like to see and fix any Elastic issues you’re having. For now, Koha’s still using Zebra in a few places outside of catalog searching, so it’s still around. Once Elastic has been set up on your server and we’ve flipped this switch for you, Zebra is going to continue to run and keep itself updated. If you flip this switch before that’s been done, you won’t get any search results at all. There’s some setup that needs to happen on your server to get Elastic installed and running. Switching to Elastic is not quite as easy as just flipping this switch, though. There are only two choices here, Zebra and Elastic. Which search engine Koha uses is determined by the system preference SearchEngine. Please also see our post about searching in Koha using Elastic. As such, this post focuses on Elastic in those two versions of Koha.
0 kommentar(er)
