You certainly could if inclusions rendered in search cards, but apparently we don't do this (yet?):
http://test.dwagn.org/wagn/inclusions_in_search_cards
There may be another way to do it...anyone?
--John Abbe
I don't think inclusions rendering in search cards would help here, actually, if I understand the use case.
Aren't we talking about having it so that, for example, I can have three drop downs in a row for car brand, make and model. When I choose the brand, I want it to narrow the makes. Then when I choose the make it narrows the model, right?
The solution there would have to be a javascript one, so that the WQL was getting updated with values that haven't touched the database.
If we were dealing with a solution where we'd already stored the user's selection before moving on, we could do this now with WQL without messing with the inclusion stuff.
--Ethan McCutchen.....Tue Feb 22 11:58:43 -0800 2011
I should say, a js solution like this could have a lot more uses -- there are lots of other more common ways that you might want to modify a form based on a previous answer.
--Ethan McCutchen.....Tue Feb 22 11:59:36 -0800 2011
Ah, a nice use of faceted search, which we would certainly want to support whenever we do faceted search. Unfortunately not something we're likely to get to super-soon, right?
--John Abbe.....Tue Feb 22 12:15:30 -0800 2011
definitely not until we've finished the module architecture.
--Ethan McCutchen.....Tue Feb 22 13:13:34 -0800 2011
Ethan nailed the use case. No prob, thanks for the feedback! Not a must-have in my case, but it helps getting precise input from users.
--Michael (Not signed in).....Wed Feb 23 07:04:40 -0800 2011
implement faceted search
--John Abbe.....Sat Feb 26 13:13:44 -0800 2011