Google Search Appliance User Experience Guide - Manual (Page 14)

14
Key considerations
When planning your user experience, it is important to note which features will work in combination
together and which features will not. In addition, certain features are only available while searching public
content and certain features require your users to provide credentials. The following table lists the
caveats of some of the enrichment features described in this chapter.
Feature Caveat
Dynamic navigation
● Works for secure searches as of release 6.12—does not
work for secure searches in 6.10 and previous releases.
● Does not work when dynamic result clusters is enabled in
GSA default front ends. Customization is required to work
together. Advise against using these features together
particularly for secure search due to increased load on GSA.
●
There are certain limitations when GSA unification is
enabled. The customer needs to have the same
configuration on all boxes (same attribute and front ends). If
there are multiple front ends, you need to create the same
front end on the secondary boxes (that is, no remote front
end resolution). The configuration needs to be created on all
boxes by the administrator (no auto-propagation).
● Does not work when sidebar elements are enabled.
●
Currency r anges only support the exact format $NN, for
example $23. Values such as 23$ or $ 23 are not supported
for range queries.
●
Dynamic navigation does not support aggregating counts for
similar/normalized metadata attributes. For example "pub"
and "publication" might represent the same metadata
attribute, but their counts are not aggregated. However,
because query expansion for meta data is supported, you
might add a
s ynonym file with the entry {pub, publication} to
get this behavior.
● Can impact performance for secure search if there is a high
number of concurrent users.
● Recommended
only for secure search when using ACLs for
Authorization.