Apparently operator is the wrong container anyway as I want the secondary sort
to be active by default--seems to work by using two sort-order elements in the
proper order:
<search:sort-order>
<search:score/>
</search:sort-order>
<search:sort-order direction="ascending" type="xs:string"
collation="http://marklogic.com/collation/";>
<search:element ns="http://rotunda.upress.virginia.edu/pfe";
name="fullname"/>
</search:sort-order>
On Dec 19, 2013, at 3:02 PM, Shannon Scott Shiflett <[email protected]>
wrote:
> Hello,
>
> is there a way to effect the default relevance sort so as to include a
> secondary sort? I added the sort-order to the options node, but it only
> becomes active when selecting from the sort menu--it does not appear to be
> applied when the results are initially served up. Can this be patched into
> Search API or should I be looking to customize the JavaScript results widget?
>
> <search:operator name="sort">
> <search:state name="relevance">
> <search:sort-order>
> <search:score/>
> </search:sort-order>
> <search:sort-order direction="ascending" type="xs:string"
> collation="http://marklogic.com/collation/";>
> <search:element ns="http://rotunda.upress.virginia.edu/pfe";
> name="fullname"/>
> </search:sort-order>
> </search:state>
> [...]
>
> Thanks,
> Shannon
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general
