Rendering of Search Scopes
CentraSite will always return the registry objects that match the search scopes currently available in the recipe.
When rendering the search results, search scopes in the recipe are considered in a hierarchical order. This rendering behavior can be best understood with the following scenarios:
The predefined default scope
Everything overrides all other predefined and custom scopes in the search recipe. If you have, for example, an
Assets scope already defined in the recipe, when you add the scope
Everything to the recipe,
CentraSite automatically removes the existing scope
Assets from the recipe and returns all the registry objects that match the
Everything scope. On the other hand, if you have, for example, the
Everything scope already defined in the recipe,
CentraSite will not allow you to add any of the other predefined or custom scopes in the recipe.
Similarly, if you have, for example, a
Service scope already defined in the recipe, then you add the scope
Assets to the recipe,
CentraSite automatically removes the existing scope
Service from the recipe and returns all the registry objects that match the
Assets scope. On the other hand, if you have the
Assets scope already defined in the recipe,
CentraSite will not allow you to add any of the other predefined or custom scopes in the recipe.
However, if the search recipe for example includes scopes other than the scope
Everything,
CentraSite will allow you to add any number of scopes in the recipe and return a collection of registry objects that match the scopes currently in the recipe.
If at any time you revert back to the Search Results page, the results are rendered based on the most recent search scopes added to the search recipe.
