The Filter Editor
In the filter editor, you can define queries for granular filtering of the displayed contents.
The filter editor is available here:
- My Tasks module
- Cockpit module (Online Client only)
You can open it with the respective item in the context menu of the column headers.
As a matter of principle, a simple filter in the filter editor consists of a Boolean operator and a condition. Together, the Boolean operator and the condition make up a group. You can determine several conditions per group and several groups per filter.
Defining a Group
To define a group, proceed as follows:
- Selection of the Boolean operator (see 1): Here, select a Boolean operator to connect the conditions.
- Selection of the column header (see 2): All column headers available in the respective module are available for selection (i.e. the range in the My Tasks module is a bit smaller than in the Cockpit module).
- Selection of a relational operator or another operator (see 3): Here, relational operators like "greater than" (>) and "less than" (<) are available.
- Definition of the desired value (see 4): Depending on the condition structure, an input field for free input or multiple options are provided here.
To add another condition or group and to remove groups that are no longer needed, click the Boolean operator and select the respective entry in the menu. Additionally, you can click the respective icons next to the Boolean operator or next to the condition to add () or remove (
) a condition. By default, the Boolean operator "And" is preselected.
Effects of the Boolean Operators
The following example demonstrates the effects of the various Boolean operators. The conditions remain the same, only the Boolean operator is changed.
In our example, we assume that we have two target languages – English and German – and three existing translators – A, B, and C. The following two conditions are specified in the filter editor:
Assigned to | = | Translator B |
Target language | = | German |
"And" search
The result shows all tasks that have been assigned to translator B and whose target language is "German".
"NotAnd" search:
The result is the opposite of the "And" search.
"Or" search:
The result shows all tasks that have been assigned to translator B or whose target language is "German".
"NotOr" search:
The result is the opposite of the "Or" search.
Example: Translator Workload
In the following example, a query is used to display the workload of the translators A, B, and C in order to decide which translators you can currently give more work. For this, we assume that tasks with less than 50 words to translate are to be neglected.
This is what the filter could look like:
Operator | Condition | ||
And | |||
Task state | ≠ | Completed | |
Task state | ≠ | Unassigned | |
Remaining words | ≥ | 50 | |
Or | |||
Assigned to | = | Translator A | |
Assigned to | = | Translator B | |
Assigned to | = | Translator C |
The result shows all unfinished tasks of the translators A, B, and C in which more than 50 words still need to be translated.
The translators with few tasks (see 1) and a small number of words that still need to be translated (see 2) have a smaller workload and may be available for the assignment of new tasks.
Notes
- Please note that the "Remaining words" value indicates the word count of the paragraphs per task that still need to be translated. The word count of the following paragraphs is automatically deducted from this value:
- finished paragraphs
- hidden paragraphs
- Paragraphs locked within the scope of a document preparation task
Please also note that the word count refers to all tasks of a workflow. For example, if a workflow with the "Translation" and "Correction" tasks has 1,000 remaining words, this figure comprises both tasks. To determine the exact word count per task, simply specify the respecting task under "Task type" in the filter editor query.
- The value "@today" stands for the exact time "today 00:00", i.e. for the beginning of today, not for the period "today from 00:00 to 23:59". However, any number of days can be added to the value "@today", e.g. "@today+1" for tomorrow 00:00", "@today+2" for day after tomorrow 00:00", and so on.
By combining these values, you can create queries that cover a time period instead of a point in time. For example, to display all tasks whose due date is today, you could use the following query:
OperatorConditionAndDue Date>@todayDue Date<@today+1This query lists all tasks whose due date is after 00:00 of today but before 00:00 of tomorrow.
- The footer of the Cockpit module shows the applied filter including its components. You can disable the filter temporarily by deactivating the checkbox. Click the
icon on the right-hand side in the footer to open the filter editor in order to modify the query; click the
icon to remove the filter permanently.