Quick Filters

By default, Across provides a number of filters referred to as quick filters. You can use these by selecting the quick filters (icn_cTerm_quickfilter) from the drop-down list and then activating and adapting one or several quick filters in the Search options tab.

These filters are available:

Filters
Available for
System attributes
Term search,
Fuzzy search,
Entry search,
Index search
Instances
Date
Users
Definitions
Entry search, Index search
Status
Term search,
Fuzzy search
Homographs
Index Duplicates
Index search

The individual filters are connected by AND operations. For example, this enables searching for terms that were created after a certain date and whose state is Unreleased.

In contrast, the search details within the individual filters are connected by OR operations. For example, when searching for terms with the subjects "Finance" and "Business" being selected via multiple selection, the search will return terms belonging to the "Finance" subject or the "Business" subject.

The following items illustrate the function of each filter.

System attributes

Using the search filter System attributes, you can search for entries and/or terms to which specific system attributes have been assigned. You can search for entries and/or terms containing the standard system attributes "Project", "Relation", and "Subject" and for those containing user-defined system attributes.

Instances

The search filter Instances enables the filtering of entries or terms by crossTerm instances. The filter is organized hierarchically. At the top level, you can first select the required crossTerm instance. At the next level, you can filter the entries or terms by the utilized entry and term picklists or text fields.

Server

The search filter Server will only be available if you use crossGrid and your Across Server acts as Trusted Servers. The two quick filters System attributes and Instances are integrated in the Server filter.

First, you can select a server context. You can select your local crossTerm pool and/or the crossTerm pools of other Master Servers. At the next level below, you can filter entries and terms by system attributes and instances. For crossTerm pools of a Master Server, you can also define the filter criteria Created by and Modified by.

Users

The search filter Users enables the filtering of entries/terms by local Across users (i.e. by users with identical server context). It is possible to search for entries/terms created or modified by these users.

cTeM_quickfilter_benutzer

The two search areas Created by and Modified by are connected by an AND operation. By activating both areas, you can, for example, search for terms created by a specific user and modified by another user.

Date

The search filter Date can be used to filter all entries or terms by modification or creation date. The search can be limited to a certain number of days or months back or to a period between two dates.

Status

In crossTerm there are two options for marking the state of a term: Released and Not released. You can use the Status filter to filter the search results according to these criteria.

Homographs

Using the Homographs filter, you can search crossTerm on the basis of homographs. You can search either only for terms for which homographs exist in crossTerm or for terms for which no homographs exist in crossTerm.

Definitions

Use the filter Definitions to search for entries with or without definitions in the source language.

Index Duplicates

When performing an index search, you can use the Index duplicates filter to search for entries with or without index duplicates.

Index duplicates can come about e.g. due to errors when entering the index values. Index duplicates are on hand if two different entries contain two identical values. For example, this would be the case if the index "ISO ID" contained value "1234" in two entries.

The quick filter enables the systematic search for these index duplicates in order to see whether the duplicates were intended or came about due to errors. Moreover, the index values can indicate whether two entries should be merged. For example, identical index values would suggest a merge, as opposed to different index values.

Attention

The search for index duplicates is performed in the index only, which is currently selected in the corresponding drop-down list.

The search for index duplicates is case-insensitive. An index duplicate is thus on hand if two index values differ in uppercase/lowercase spelling only (e.g. “ISO_1234” and “iso_1234”).