When creating a job through the user interface, the option to ignore (exclude) hidden files during transfers is selected by default. To include hidden files, clear the Ignore hidden items box. 

Shared items are those available to the account but not owned by it. Excluding shared items is useful when multiple accounts are being migrated, ensuring duplicate content is not created on the receiving platform. When the filter is set on a job, DryvIQ will only transfer items that are owned by the account the job is running as. The appropriate permissions will need to be applied to the item once it is transferred (either through permission migration or manual permission mapping) for other accounts to have access to the item on the destination.

The age filter allows you to include or exclude content based on its created on, modified on, and/or last touched date. Use the Date types list to select the date type you want to use. Note that any combination of the dates can be selected. Specify the number of days you want to use in the Within the last field. 

The date range filter allows you to filter content based on its created on, modified on, and/or last touched date. You can choose to use the After or Before date field but not both. Type the date you want to use as the filter or use the calendar tool to select the date. 
 

The file extension filter will include or exclude files based on the file extensions you specify. Simply type the extensions you want to filter separated by commas.

This filter allows you to filter content based on its size (in bytes). You can filter all files greater than or less than a specified size.  

The file type filter allows you to filter content by type (audio, documents, etc.). This filter should be used over the file extension filter when you are looking to filter out a type of content. It allows you to do so without having to specify the various extensions. 

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. 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. 

Format

Metadata should be entered using the one of the following formats:

• [Property]="Text"
• [Property]=Numeric Value
• [Property]="Text 1" OR [Property]="Text 2"
• [Property]=Numeric Value 1 AND [Property]=Numeric Value 2

The following example excludes items with value "Doe" for the property value LName metadata column on the Source platform.

The following example excludes items with value "Doe" or “Smith” for the property value LName metadata column on the Source platform.

Identifying the Columns to Filter

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"
                                    }
                                }
                            }
                        ]
                    }
                ]
            }
}
}

This filter allows you to filter files and/or folders based on the name pattern. An asterisk can be used for exact matches or for prefix or suffix matches. For example, *txt would filter all .txt extensions. You can also use asterisks to surround a pattern to filter file and/or folder names. For example, using *test* would filter all names that contain “test.” Use semicolons for multiple match patterns. For example, *test*;*draft* would filter all names that contain “test” or “draft.” 

This filter allows you to include or exclude specific files or folders from the source connection based on the exact path you specify. Paths are case sensitive and should be specified using the proper case as it exists in the folder or file path.

1. In the Rule type list, select Specific file or folder.
2. Click the Edit link at the end of the Select a specific file or folder to filter field.
3. A modal appears. Either navigate to the file or folder you want to filter or click Manually enter a path to type the exact path. The path will be relative to the source path and should start with a forward slash (/) as in the example below. Paths are case sensitive and should be specified using the proper case as it exists in the folder or file path.
    

4. Once you specify the path, click Use this path.
5. The path displays in the Select a specific file or folder to filter field for your reference.
6. Click Done to complete adding the filter to the job.

Editing a Filter

1. Click Edit next to the filter.
2. Click Edit again on the Select a specific file or folder to filter field.
3. Use the modal that appears to edit the path.
4. Once you specify the path, click Use this path.
5. The path is displayed in the Select a specific file or folder to filter field for your reference.
6. Click Done to finish editing the filter.

Removing a Filter

1. Click Edit next to the filter.
2. Click the Delete rule link that appears under the filter information.
3. Click Yes when prompted to verify you want to delete the filter.