Patterns Matching
Patterns filed type uses patterns matching to filter input.
Example of such fields from Storage Settings view:
- Ignore Files Patterns and Include Files Patterns
- Transcode Exclude Patterns and Transcode Include Patterns
- Don't Upload Patterns
Currently patterns matching fields support two formats:
Unix filename pattern matching
This allows a pattern matching by using Unix shell-style wildcards. For example: *.xml - will match paths ending with .xml extension.
This also works for matching folder names. For example: media cache files - will match any path that contains provided folder name.
Regular expression matching
This allows a more advanced pattern matching by using regular expressions.
To distinguish from Unix filename pattern matching a value must be stored in a custom format like this: re:/your_custom_regex/
For example: re:/(?i).*\.(mp4|mov|jpg|png)$/ - will match paths ending with either mp4, mov, jpg or png extensions.
Ignore Files Patterns
Ignore Files Patterns field provides an ability to exclude content from being ingested by a storage scan by using the patterns matching.
Default Ignore Files Patterns
Here is the list of the default ignore files patterns for an ISG storage with relative short descriptions:
| Ignore Files Patterns | Description |
|---|---|
| *.iconikagent | iconik Agent temporary files |
| *.fcpcache | Final Cut Pro Cache file |
| *.cfa | Premiere Pro Conformed Audio File |
| *.pek | Premiere Pro Peak File |
| *.ims | Adobe's Index Metadata Stream |
| media cache | Stores conformed audio (.cfa), peak files (.pek), and other temporary files generated during media import and playback |
| media cache files | Similar to or the same as "media cache" – holds temporary files like .pek, .cfa, and video previews for faster performance |
| adobe premiere pro auto-save | Stores automatically saved backup project files at set intervals |
Scan performance impact of patterns matching
A larger list and greater complexity of used patterns can affect a scan speed making it longer.