You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pagefind's default behavior when showing sub-results seems to be: show the first 3 sub-results, implicitly ranked by the order in which they appear on the page.
So, the search term "smoke asthma" returns
because of this
even though "Mold in homes" has one hit with a score of 39574, and "Secondhand smoke at home" has 3 hits with scores of 69456, 51029, and 51029.
Each result contains all matching sub-results, so we could figure out how to overwrite the displayed sub-results with an arbitrary number sorted by balanced_score.
Would be moot if the pagefind team changes the default behavior, and I might submit an issue over there.
The text was updated successfully, but these errors were encountered:
NB: a lot of our site-search terms are for neighborhoods - neighborhood names, including ZIP Codes. Search should absolutely return useful results for neighborhood names, ZIPs, etc.
Write readme/documentation covering tags to use, weighting standards, links to useful documentation (eg HX -> weight equivalence)
Revise Key Topic title weighting
Ensure good data-features weighting
Add ZIPs to NR weighting
"Get data for TITLE about NEIGHBORHOOD" on data-explorer/single.html or section.html with low weight so that a neighborhood search turns up Data Explorer opportunities.
pagefind's default behavior when showing sub-results seems to be: show the first 3 sub-results, implicitly ranked by the order in which they appear on the page.
So, the search term "smoke asthma" returns
because of this
even though "Mold in homes" has one hit with a score of 39574, and "Secondhand smoke at home" has 3 hits with scores of 69456, 51029, and 51029.
Each result contains all matching sub-results, so we could figure out how to overwrite the displayed sub-results with an arbitrary number sorted by
balanced_score
.Would be moot if the pagefind team changes the default behavior, and I might submit an issue over there.
The text was updated successfully, but these errors were encountered: