Feature that Described below is to be valueable for all kind of facet dependency , including existing bundle dependency in core Facet api and also so called Another facet dependency (provided by Facet Bonus module). Let me explain idea for case of using Bundle dependency
Imagine your website represents different products (Batteries ,TV sets,mobiles etc.) of different Makers (Duracell, Sony ,Samsung etc.) As different products have different sets of features (the only common is Makers) you can decide to make different content types devoted to each kind of product and make faceted search on 2 facets Makers and Product type. If you add to some kind of product some new fields specific for it –next natural step is add more facets for more deep drilling. The only thing is to be done additionally is to make that new facets depending on active content type (Bundle dependency).For example if you add Voltage for batteries –user will have possibility to choice it as soon as Batteries will be made active before
It,s I think classical way to use that nice feature of dependency.

It,s Ok -but let see ,what happens after user made Duracell active as his first step
The next step the only can be made is to make Batteries active (It,s the only product made by Duracell) .Obviously it,s smart step as due Dependency he can continue exploring Voltage etc.

But… As smart this step as it is not obvious for user !!! For normal man all steps in search are rational if they narrow result. The choice of one variant is not choice ( may be just in North Korea )))

So my idea is next:

To consider facets values that don’t narrow result as so called “pseudoactive” .So despite of formally user didn’t make them active –all facets that are dependent on it have to be shown.

Comments

SergeyR’s picture

Status: Active » Closed (duplicate)