You are here:

Search for Inconsistent Tags

You can use field-based search to locate associated document sets that are not tagged consistently. This feature can be used on single value, multivalue, hierarchy, date, and numeric fields. It can also be used on the Review State field.

Input your search criteria into either the Keyword Search box or the Search Query Editor (SQE). The syntax is not case sensitive.

The basic field-based search pattern is:

<query> <action> <relationship type>.withIdenticalValues(<internal field name 1>, <internal field name 2>)

Note: To apply the search to all documents in the project, input * as the query. If you input an actual search query, add in the associated document types of interest before searching for inconsistent tags.

The action and relationship type options for this type of search are described below:

Action
Syntax	Meaning
drop	Returns only documents that do not have consistent values in the specified field. That is, related document sets that have consistent values in the specified field not returned. Also drops document sets that have no tag in the specified field, because, to the system, this means those documents are consistently tagged.
keep	Keeps related document sets that have consistent values in the specified field. Also returns document sets that have no tag in the specified field, because, to the system, this means the field is consistently tagged. Also returns standalone documents, that is, documents that do not have any family members, because, to the system, these one document "sets" are consistently tagged.

Relationship Type
Syntax	Meaning
duplicate	Identical documents, identified using MD5 hash analysis. Note: A document that does not have duplicates is considered by the software to be its own duplicate group of size one. To restrict a search to documents with actual duplicates, add keep duplicate.size > 1 to the query. Example This query returns duplicate groups of size greater than one where each document in a group has identical values in the Responsiveness field. * keep duplicate.size>1 keep duplicate.withIdenticalValues(ax_responsiveness)
nearduplicate	Documents identified by algorithm as differing only slightly in content, such as different formatting, numbers, typos, or small variances in text.
thread	Running email communications with succeeding replies or forwards, as identified by header analysis.
eob	An email that is content-inclusive of all earlier emails in the thread. Note: A standalone document, even if it is a non-email, is considered by the software to be a single document end of branch group. To restrict a search to actual end of branch groups, add keep eob.size > 1 to the query. Example This query returns end of branch groups of size greater than one where each document in a group has identical values in the Responsiveness field. * keep eob.size>1 keep eob.withIdenticalValues(ax_responsiveness)
family	Any part of a document family, that is, a parent, an attachment or an embedding.
custom	Available only when custom associations are in use in a project.

Below are the internal field names of commonly used default fields for Axcelerate 5. To obtain the internal field name of other fields, ask your Administrator.

Internal Field Names for Common Default Fields
Axcelerate 5 Default Field Name	Internal Field Name
Responsiveness	ax_responsiveness
Privilege	ax_privilege
Issues	ax_issue
Workspace	ax_workspace
Review State	ax_review_state
Document Date	meta_docdate
File Size	rm_filesize

Be aware that your Case Manager may rename a default field, for example, they may rename the Responsiveness field to Relevant. In this case, the internal field name remains ax_responsiveness.

Axcelerate 5 also contains a number of empty, preconfigured fields that can be activated and customized for use. The internal field name for these types of fields does not change if they are renamed. For example, if you activate the first preconfigured hierarchy field and name it Witness Documents, its internal display name remains ax_cust_hrchy_a.