Both of these web service calls return the facets in the same order, despite
the "fsort" param being different.
http://biocache.ala.org.au/ws/occurrences/search.json?q=establishment_means%3Ana
tive&qc=data_hub_uid:dh2&facets=uncertainty&flimit=100&foffset=0&pageSize=0&fsor
t=index
http://biocache.ala.org.au/ws/occurrences/search.json?q=establishment_means%3Ana
tive&qc=data_hub_uid:dh2&facets=uncertainty&flimit=100&foffset=0&pageSize=0&fsor
t=count
A starting place may be the fact that this facets has the new "fq" attribute in
its "fieldResult" data (?).
FYI, this WS call is used by the "choose more" popup of facet values in the
search results facets column - when you click the table column header to sort
the facets.
Original issue reported on code.google.com by nickdos on 19 Mar 2014 at 2:45
Original issue reported on code.google.com by
nickdos
on 19 Mar 2014 at 2:45