Walter -
How about this, for the latter part of your request:
/handler?features=a,b,c
with &sort=sum(${features}) desc
That ought to do the trick. At first I thought the #foreach nature of the
list of features was prohibitive, but since you’re literally plugging in the
exact string value and it’s used as a comma-separated list then this should
work.
But with the just a list of subject ID’s I think you’re in custom development
now (or a JavaScript stage in a Fusion query pipeline ;) in building a
SearchComponent that takes a `features` parameter and builds the sort param as
needed from that.
Erik
> On Feb 27, 2017, at 7:17 PM, Walter Underwood <wun...@wunderwood.org> wrote:
>
> We have documents with parameterized features. For a school subject
> (calculus, accounting), we have three sets of features. So for subject=4 and
> subject=186, we have:
>
> feature_a_4: 0.9
> feature_b_4: 1.6
> feature_c_4: 8.2
> feature_a_186: 3.0
> feature_b_186: 2.1
> feature_c_186: 99.2
>
> I’d like to pass in the subject IDs and make a function query (for sorting)
> from those, ending up with
>
> sum(feature_x, feature_y, feature_a_4, feature_b_4, feature_c_4,
> feature_a_186, feature_b_186, feature c_186) desc
>
> That would be used for the sort parameter.
>
> Failing that, it would be nice so just pass in the parameterized portion,
> like this:
>
> /handler?features=feature_a_4,feature_b_4,feature_c_4,feature_a_186,feature_b_186,feature
> c_186
>
> Right now, I can’t even make a solrconfig.xml that will load. I’ve read
> everything I can find on params and function queries.
>
> wunder
> Walter Underwood
> wun...@wunderwood.org
> http://observer.wunderwood.org/ (my blog)
>
>
