The Grouping Properties page enables you to establish and configure the collection of custom properties that will be available for use in grouping controls. Custom properties provide metadata for a given document, such as the document author, last-modified date, document type, etc.
Finding the Grouping Properties Page
To find the Grouping Properties page:
1. Go to the Search Tabs page for the site and site level at which your grouping property will apply. See “Search-Tab Configuration and Inheritance” for details.
2. Click on the search tab to which you want to add the grouping property and select Configure Search Tab from its action menu. This opens the Search Tab Configuration page.
3. Click on the Grouping Properties link under the Property Settings heading on the Search Tab Configuration page. This brings you to the Grouping Properties page.
See below for details about the information, settings, and features provided on the Grouping Properties page.
|Note: all meta data properties that you wish to use must be available and configured as a managed properties in SharePoint before you can configure them as grouping properties for Ontolica.|
Interpreting the Grouping Properties List
The Grouping Properties page provides a list of properties currently available for grouping controls on your selected site and search tab. You can see the following information here:
• Property ID: These are listed in the ID column. This is how the property is identified on the various Ontolica configuration pages.
• Property Name: These are listed in the Name column. This is how each property is identified by users.
• Managed Property: Grouping properties are an Ontolica concept; they are named and configured using settings provided by Ontolica. However, each property must also be known to SharePoint and its search engine as a managed property. Usually, there are many more managed properties in SharePoint than would be relevant as grouping properties for Ontolica. The Managed Property column shows the name of the SharePoint managed property that is mapped to each listed Ontolica grouping property.
• Inheritance Status: As with most Ontolica settings, grouping properties are inherited along the lines of your SharePoint site structure. Icons in the Inherited column indicate whether each property has inherited some or all of its settings from a higher-level site as follows:
|This icon in the Inherited column indicates a result action that has been inherited from a higher site level without any local overrides. You can break the inheritance and make custom settings for the local site by using the action menus (see below). The icon is shown in gray for actions that are hidden starting at the current level and below.|
|This icon in the Inherited column indicates a result action that was originally inherited from a higher site level but has since been customized. These actions no longer track updates made at higher site levels—all settings are now defined locally. These local overrides are also inherited by child sites (if any). You can reinstate the inheritance of any of these actions by using the action menus (see below). The icon is shown in gray for actions that are hidden starting at the current level and below.|
|(no icon||Result actions that do not show an icon in the Inherited column have been created at the local level and are not available at higher levels. These actions will be inherited by child sites (if any).|
|This icon in the Inherited column indicates a result action that has been both created and hidden at the local level (see below for details about hidden actions).|
|Note: Even at the top, farm level you will see inheritance indicators. Result actions (and other settings) shown as inherited or customized at this level are inheriting their settings from the Ontolica factory defaults. You can think of the defaults as existing as a virtual site level immediately above the farm level. This provides a good way to handle upgrades to Ontolica, enabling new defaults to be loaded into your system during an upgrade without affecting your configuration work so far. You can override, revert and/or hide any of these settings at the farm level as required, just as on other levels. See below for the relevant commands.|
Using the Grouping Properties Toolbar
A toolbar is provided at the top of the Grouping Properties page. It provides buttons for performing each of several tasks, as outlined below.
|Click here to return to the page you were on just before coming to the current page.|
|Click here to add a new grouping property for your current site and search tab. This opens the Add Grouping Property page. The settings provided here are the same as those for configuring an existing property (see “Creating and Configuring Grouping Properties”)|
|Click here to reload the current page. This will reveal updates made by the system, other users or in other browser windows while the current page remained open in your browser.|
Using the Grouping Properties Action Menus
Each property listed on the Grouping Properties page provides an action menu with commands for acting on a selected property. As usual in SharePoint, the action menu appears when you hover the mouse pointer over the property; the name then acts like a drop-down list with some combination of the commands summarized below.
|This entry appears for properties that have been inherited and not (yet) customized. Select this entry to capture the currently inherited settings and break the inheritance, which means that changes made for this property higher up in the hierarchy will no longer affect it at the current level or below. This entry will also bring you to the page for configuring the selected property (see “Creating and Configuring Grouping Properties”).|
|This entry appears for properties that are either defined or customized at the current level. Select this to open the page for configuring the selected property (see “Creating and Configuring Grouping Properties”).|
|Select this entry to create a new property that initially has the same settings as the selected one. This opens the Copy Grouping Properties page, which enables you to configure the new copy (these settings are the same as those offered when you edit or create a new property). You must at least assign a new and unique ID to the new copy.|
|To rearrange the properties, click on a target property and select one of these entries. Note that non-customized, inherited properties cannot be moved.|
| If you would like to disable a property temporarily, or suppress it for just a few branches of your hierarchy, select its Hide Property entry (this entry is only active for properties that are not currently hidden). Hidden properties will show “(Hidden)” after their name on the Grouping Properties page (e.g., “Author (Hidden)”) and will also show grayed icons in the Inherited column. Hidden properties will not appear to users at the level at which they are marked as hidden, nor will they appear for any of the sites below that branch of the hierarchy (including sites for which a newly hidden property previously had local overrides). Hidden properties will furthermore not appear to administrators on the Grouping Properties page for any of the sites below the level at which a given property was hidden.
To reactivate a hidden property, find the site level at which the property is marked as hidden, open its action menu and select the Show Property entry (this entry is only active for properties that are currently hidden). The property will once again be visible to all users and administrators at that level and below. If local overrides existed for a lower-level property before it was hidden, then those overrides will be reinstated when the property is again set to be shown.
|This entry appears for customized, inherited properties. Select this entry to discard local overrides and re-instate inheritance, which means that these properties will continue to track configuration changes made to its parent.|
|This entry is only active for properties that are defined at the current level. Select it to delete the selected property. Note that if the deleted property has been customized at a child level, then that property will remain at that child level and will no longer be marked as inherited.|