Indeed, selecting the best price for January OR April OR November and
sorting on it isn't possible with this solution (if that's what you mean).
However, any combination of selecting 1 month and/or 1 price-range and/or 1
fare-type IS possible.
2010/12/1 lee carroll
> Hi Geert,
>
> Ok I think I f
Hi Geert,
Ok I think I follow. the magic is in the multi-valued field.
The only danger would be complexity if we allow users to multi select
months/prices/fare classes. For example they can search for first prices in
jan, april and november. I think what you describe is possible in this case
just
Also, filtering and sorting on price can be done as well. Just be sure to
use the correct price- field.
Geert-Jan
2010/12/1 Geert-Jan Brits
> Ok longer answer than anticipated (and good conceptual practice ;-)
>
> Yeah I belief that would work if I understand correctly that:
>
> 'in Jan [9]
> in
Ok longer answer than anticipated (and good conceptual practice ;-)
Yeah I belief that would work if I understand correctly that:
'in Jan [9]
in feb [10]
in march [1]'
has nothing to do with pricing, but only with availability?
If so you could seperate it out as two seperate issues:
1. ) showi
Sorry Geert missed of the price value bit from the user interface so we'd
display
Facet price
Standard fares [10]
First fares [3]
When traveling
in Jan [9]
in feb [10]
in march [1]
Fare Price
0 - 25 : [20]
25 - 50: [10]
50 - 100 [2]
cheers lee c
On 1 December 2010 17:00, lee carroll wrote:
Geert
The UI would be something like:
user selections
for the facet price
max price: £100
fare class: any
city attributes facet
cityattribute1 etc: xxx
results displayed something like
Facet price
Standard fares [10]
First fares [3]
in Jan [9]
in feb [10]
in march [1]
etc
is this compatible wit
Hmmm, that's getting to be a pretty clunky query sure enough. Now you're
going to
have to insure that HTTP request that long get through and stuff like
that
I'm reaching a bit here, but you can facet on a tokenized field. Although
that's not
often done there's no prohibition against it.
So, w
"if first is selected in the user interface and we have 10 price ranges
query would be 120 cluases (12 months * 10 price ranges)"
What would you intend to do with the returned facet-results in this
situation? I doubt you want to display 12 categories (1 for each month) ?
When a user hasn't select
Hi Erick,
so if i understand you we could do something like:
if Jan is selected in the user interface and we have 10 price ranges
query would be 20 cluases in the query (10 * 2 fare clases)
if first is selected in the user interface and we have 10 price ranges
query would be 120 cluases (12 mont
I'd think that facet.query would work for you, something like:
&facet=true&facet.query=FareJanStandard:[price1 TO
price2]&facet.query:fareJanStandard[price2 TO price3]
You can string as many facet.query clauses as you want, across as many
fields as you want, they're all
independent and will get the
10 matches
Mail list logo
