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
Counts that are the same number of returned documents does /not/ imply that the facet bears no information; think of closures on different paths--they might look the same (same counts) but clicking on them can get you different sets.
Even assuming the above, in Solr it's hard to eliminate facets--we have a lower limit, but not an upper one. without getting way more facets than we need, it's not knowable how many we would have to order to get 25 back. Might be doable with pivots in Solr 4.+?
We have triaged all of the above with mentioning a little about the redundancy in the accordion itself.
The text was updated successfully, but these errors were encountered:
Actually, we can also make this a little better by making the number of facets shown (with a little warning) user selectable like the number of results.
Counts that are the same number of returned documents does /not/ imply that the facet bears no information; think of closures on different paths--they might look the same (same counts) but clicking on them can get you different sets.
Even assuming the above, in Solr it's hard to eliminate facets--we have a lower limit, but not an upper one. without getting way more facets than we need, it's not knowable how many we would have to order to get 25 back. Might be doable with pivots in Solr 4.+?
We have triaged all of the above with mentioning a little about the redundancy in the accordion itself.
The text was updated successfully, but these errors were encountered: