https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23649 --- Comment #31 from Pedro Amorim (ammopt) <pedro.amorim@openfifth.co.uk> --- (In reply to Jason Robb from comment #28)
Weight values over 999 fail and throw this console error:
mappings.pl:44363 POST http://localhost:8081/cgi-bin/koha/admin/searchengine/elasticsearch/mappings. pl 500 (Internal Server Error) (anonymous) @ mappings.pl:44363 dispatch @ jquery-3.6.0.min_26.0600026.js:2 v.handle @ jquery-3.6.0.min_26.0600026.js:2 VM937:1 Uncaught (in promise) SyntaxError: Unexpected token 'D', "DBI Except"... is not valid JSON
Thanks for the clarification on the math!
If I'm only boosting a single search field type (i.e. all my boosts are on itype), things seem to be working fairly well!
I did run into a possible issue when boosting multiple different search field types. It appears to only take one into account. As an example:
1.) Add $(".search_score").toggle(); to IntranetUserJS to see the search score 2.) Search for john > results all score 1 3.) Add a boost of itype > BK > 200 4.) Search for john > records with BK in the 942$c get a score of 200 (some of the results look wrong because of the item-level itypes but the record-level types are boosted correctly) 5.) Add an additional boost of location > GEN > 200 6.) Search for john. The fourth result has BK in the 942$c but the items have locations of AV, and there are additional results after it where both the itype is BK and the locations are GEN.
Shouldn't it be putting results where multiple boosts match higher than results that only match some of the boosts?
Thanks for testing Jason, I believe the last 2 patches address these. Please re test when convenient. Thanks! -- You are receiving this mail because: You are watching all bug changes.