Attribute Filter Rules

The filter rules define the logic of the attribute filter. A filter needs at least one rule and can have any number of rules. In the filter editor, a single rule is represented as one row in the rules table.

A filter rule consists of the following:

Left operand (Search In)
The attribute for which to filter. Choose the left operand from the list of all available attributes. The available attributes vary based on the filter type.
For terminology database filters, the list contains both terminology database entry and terminology database term attributes. These attributes include:
- Created By (Term/Entry)
- Created On (Term/Entry)
- Modified By (Term/Entry)
- Modified On (Term/Entry)
For translation memory filters, the attributes include:
- Created By
- Created On
- Modified By
- Modified On
- Entry Origin (the AIS path pointing to the asset the entry originated from)
- Import Job ID
Operator
Creates the logic between the left operand and the right operand(s). The available operators can be grouped as: equality operators (“ equals ” and “ not equals ”), comparison operators (“ less than ”, “ greater than ”, “ less than or equal to ”, and “ greater than or equal to ”), range operators (“ between ” and “ not between ”) and wildcard operators (“ matches ” and “ not matches ”).

Numeric ranges are inclusive. For example, if you had an Import Job ID range of 1001 to 1020, entries with an Import Job ID of 1001 and 1020 will be returned (as well as those between).
One or two right operands (based on the operator type) (Search For)
The values to which the left operand is compared using the operator. The second right operand is available only for the range operators.

Multiple rules can be combined using the rules operators. The available rules operators are the two Boolean operators: “ and ” and “ or.” When combining multiple rules using both of these Boolean operators, the “ or ” operator has precedence.

Add rules to the filter by clicking the Add Rule button. Delete rules by checking the box next to the rule(s) and clicking the Delete Rules button. To save changes to the filter, click OK.

Rules of the Rules

Not every attribute type (left operand type) can be combined with every operator. The table below describes which operator types are available to which attribute type.

Attribute Type/Operator Type	Equality	Comparison	Range	Wildcard
Text Field	X	X	X	X
Text Area	X	X	X	X
Selector	X	X	X	X
Date	X	X	X
Integer	X	X	X
Boolean	X

In addition, the following rules and restrictions apply:

Date Type Attributes

When searching for Date type attributes, the right operands must be in the “ mm/dd/yy ” or “ mm/dd/yy hh:mm ” formats (or the equivalent format for the Regional Setting you have selected). The wildcard operators (“ matches ” and “ not matches ”) are not supported for Date type attributes. Meaningful date operators include the following:

equals
not equals
between
less than or equal to
greater than or equal to
less than
greater than
not between

Note: WorldServer uses the date ranges whenever an "equals date" query is performed; if you are doing a day search using a date only format (for example, mm/dd/yy), it will default to a date range of midnight of current day to 1 millisecond before midnight of the next day.

Boolean Type Attributes
When searching for a Boolean type attribute, the string “ true ” must be entered in combination with the “ equals ” operator to filter the entries that have the Boolean attribute “ checked.” To filter entries with the Boolean attributes “ unchecked,” the “ not equals ” operator should be used with the string “ true ” in the right operand.
Wildcard Operators
The “ match ” and “ not match ” operators can be used in conjunction with the wildcard “ * ” when filtering by attributes of type Text Field, Text Area, or Selector. For example, the right operand values could be: ca*, *ar or *a*.
Created By/Modified By Attributes
These default Text Field attributes contain information about the user that created or modified those entries.
When an entry is created or modified in WorldServer, the values of these attributes are stored in the following format:
```
first_name <space > last_name <space > (user_name)
```
When the entries are imported from a third-party system, these built-in attributes may have different formats and information stored. Because of these formats and differences, the “ equals ” operator is not very effective, and the “ matches ” operator is suggested. For example the right operand could be: *admin*.

Examples

Using these rules, you can create filters get information like the following:

To return all the entries created by this user for the last 10 days, you would specify Created By and Created On fields.
To return all entries produced from the /doc/en/mydocument.html file, you would specify the Entry Origin field.