The Filter Function can be used to specify a subset of records that must be available in the Termbrowser. Once a filter has been set, the browse controls will only browse and display the records that adhere to the filter restrictions. The search function will also only search for terms that are included in the filtered data.
The filter can be used to show:
•all the records that fall under a specific Termbase;
•all the records listed under a specific project or combination of projects;
•all the records that were created or edited by a specific user;
•all the records that were created or edited within a certain period;
•all the records that contain (or do not contain) certain fields;
•all the records that contain (or do not contain) fields with specific values.
These functionalities can be used separately or in combination to obtain a very specific subset of data. Note that the more complex the filter is set, the more time it will take for the system to reload the specific terms contained within the filter definition. Try to keep the filter definition as simple as possible in order to minimise delays. Also, think logically about the filter you are defining. It is possible to define filters that will never return any results and you should try to avoid setting the filter to produce such results.
Once a filter has been set, you can set the source language to further limit the records available in the Termbrowser.
The information panel
The status of the filter is clearly indicated on the information panel and the following states can be seen:
1.No Filter is set;
2.Filter is set; each showing the number of records available in the Termbrowser.
The Filter dialog overview
The Filter button at the left-hand side of the filter panel opens the Filter Dialog, where filters can be configured and applied to the Termbase.
The Filter Dialog, are divided into several sections:
1.Select termbase (a selection must be made before the other filter panels will be displayed).
Here you can select the Termbase to which the filtered records should belong. A list of all available Termbases will be displayed when you click on the drop-down list.
2.Project filters
The Project filters are only shown once a Termbase has been selected in the Select Termbase list. Multiple projects can be added on this filter and the association between the projects can be specified by either the AND or the OR operator.
3.User & Date filters
Allows you to filter according to records that a specific user created or changed and can also be specified to apply the filter from, to and between specific dates.
4.Field filters
Filters can be specified on specific fields and combinations of fields.
5.Controls
The selected filter configuration can be applied to the Termbase by clicking on the Set Filter button.
The Clear button removes the data from the filter and clears all selections from the Filter Dialog.
The Close button closes the dialog WITHOUT applying the filter to the data.
Open and Close the Filter Dialog
1.Click on the Filter button on the Control panel.
2.The Filter dialog will open.
Note: It might take a little while for the dialog to load.
3.To close the dialog, click on the Close button.
4.The Filter dialog will close without implementing recent settings.
Clear the Filter
1.Open the Filter dialog (refer to the Open and Close the Filter Dialog).
2.Click the Clear button on the Filter dialog controls.
3.Click the Close button to close the Filter dialog and clear the filter.
Filter operations to avoid
Certain Filter operations might take a lot of time to complete depending on the amount of data in the Termbase. Listed here are the Filter operations that should preferably be avoided.
Projects
•Any project that has “Contains” and “Does not contain” toggled in between AND or OR Fields
•Any field that has a field value specified with it in between ANDs or ORs
•Any field that has “Contains” and “Does not contain” toggled in between ANDs or ORs
General
•A combination of the entities above will cause the filter to process a huge amount of data, which will in turn take a long time to return any results.
•A combination any of the entities above or both of them, used in conjunction with a user filter will more than likely cause the filter to be slow.
NB: If a filter is specified that takes a bit of time to return results, the systems reaction time will be slower for other system operations (e.g. Searching, Exporting). So it may be better to redefine the filter after the results are returned.