Job Filters: Metadata Conjunctions

Owned by Andrea Harvey
Last updated: Oct 16, 2023 by Andrea Harvey
4 min read

On This Page

Overview

To filter items by metadata, the target platform must support metadata. If the target platform does not support metadata, the "Metadata Content" custom filter will be disabled.

 

Filtering metadata is not supported when using the Metadata Import function. Any metadata content filters configured with Metadata Import will be ignored.

 

To filter metadata content, both the Filtering and Scripting options need to be enabled on the Advanced setting page. The Metadata Mapping option should not be enabled.

 

The following example excludes the item that is associated with value "Doe1" or "Doe2" for the property value LName metadata column on the Source platform.

Format: 

[Property]="Text 1" OR [Property]="Text 2"

[Property]=Numeric Value 1 AND [Property]=Numeric Value 2

 

Identify the Columns to Filter on

Populate the property name value that corresponds with metadata content column.

{ "transfer" : { "metadata_map": { "schemas": [ { "mappings": [ { "source": { "property": { "name": "LName", "type": "string" } }, "destination": { "property": { "name": "LName", "type": "string" } } } ] } ] } } }

 

 

Filter Using REST API

For metadata filtering, the type attribute can use filter_metadata or metadata. Both configurations work the same. If the target platform does not support metadata, the filter or text definition for the given connection will be ignored.

In addition, metadata filtering rules (rules block) can be defined using either a filter block or text attribute. Filters (filter blocks) include name, op, and value attributes, name is the metadata field name, op is one of the operators defined in the table below, and value is the metadata value used for the comparison. All three attributes are required, even with the empty and not_empty operators. When empty and not_empty operators are used, ensure to configure the value to represent an empty state (e.g. "value": ""). 

Text (text) values must be in a string format with quotes around the value escaped and brackets around the field name (e.g. "[ProtectionLevel]=\"Sensitive\""). Numeric values do not need to be contained in quotes. 

Multiple metadata filters may be joined by AND or OR conjunction clauses. There are two ways to define conjunctions; filters or text. These methods are based on the filter and text methods described above.

Attributes

Operator (filter:op)

Description

Equivalent Text Operators

Filter Example

Text Example

Operator (filter:op)

Description

Equivalent Text Operators

Filter Example

Text Example

eq

equals

=

"[ProtectionLevel]=\"Sensitive\""

not equals

"[ProtectionLevel]!=\"Sensitive\""

less than

"[ProtectionLevel]<100"

less than or equal to

"filter": {
  "name": "ProtectionLevel", 
  "op": "le",
  "value": 100
}

"[ProtectionLevel]<=100"

greater than

"filter": {
  "name": "ProtectionLevel", 
  "op": "gt",
  "value": 100
}

"[ProtectionLevel]>100"

greater than or equal to

"filter": {
  "name": "ProtectionLevel", 
  "op": "ge",
  "value": 100
}

"[ProtectionLevel]>=100"

starts with

= with * appended to the end of the value

"filter": {
  "name": "Author", 
  "op": "starts_with",
  "value": "John"
}

"text": "[Author]=\"John*\""

does not start with

<> or !=

"filter": {
  "name": "Author", 
  "op": "not_starts_with",
  "value": "John"
}

"text": "[Author]!=\"John*\""

ends with

= with * prepended to the beginning of the value

"filter": {
  "name": "Author", 
  "op": "ends_with",
  "value": "Anderson"
}

"text": "[Author]=\"*Anderson\""

does not end with

<> or !=

"filter": {
  "name": "Author", 
  "op": "not_ends_with",
  "value": "Anderson"
}

"text": "[Author]!=\"*Anderson\""

contains

"filter": {
  "name": "Author", 
  "op": "contains",
  "value": "John"
}

"text": "[Author]=\"*John*\""

does not contain

<> or !=

"filter": {
  "name": "Author", 
  "op": "not_contains",
  "value": "John"
}

"text": "[Author]!=\"*John*\""

includes all the values

"filter": {
  "name": "ProtectionLevel", 
  "op": "in",
  "value": ["Not Sensitive"]
}

"text": "[ProtectionLevel] IN (\"Not Sensitive\")"

does not include all the values

"filter": {
  "name": "ProtectionLevel", 
  "op": "not_in",
  "value": ["Sensitive", "Highly Sensitive"]
}

"text": "[ProtectionLevel] NOT IN (\"Sensitive\", \"Highly Sensitive\")"

the value is empty

<>"*" or !="*"

"filter": {
  "name": "Author", 
  "op": "empty",
  "value": ""
}

"text": "[Author]!=\"*\""

the value is not empty

"filter": {
  "name": "Author", 
  "op": "not_empty",
  "value": ""
}

"text": "[Author]=\"*\""


Example 1

The following example will include any files on the source that have a metadata field named "ProtectionLevel" with value of 50 or 100.

 

Example 2

The following example will include any files on the source that have a metadata field named "ProtectionLevel" with value of 50 and "Author" equal to "John.”

 

 

DryvIQ Migrate Version: 5.9.1
Release Date: November 7, 2024