FILEWATCHER DMEDIA FULL

If no pattern is provided, the default pattern is used: Details are in this topic: File Watcher: File Name Patterns. We recommend using a regex interpreter, such as, to test the behavior of your file pattern. File Pattern: A Java regular expression that captures filenames of interest and can extract and use information from the filename to set other properties.Include Child Folders: A boolean indicating whether to seek uploadable files in subdirectories (currently to a max depth of 3) of the Location to Watch you specified.Note that if you use the root location here, you should also set a Move to Container location to avoid a potential loop when the system tries to make a copy to the same location 'before analysis'.Learn more about setting the file and/or pipeline roots for your folder.Site and Application Admins can watch an absolute path on the server's file system (beginning with a '/'), or a location outside the local filesystem, such as on the local machine or a networked drive.

Users with 'Folder Admin' or higher can watch locations relative to the container root.

FILEWATCHER DMEDIA FULL

Use '.' to indicate the pipeline root directory itself (or you could also enter the matching full path).

This can be a path relative to the local container's pipeline root, beginning with './'.

Confirm that this directory exists before saving the file watcher configuration.

Location to Watch: File location to watch for uploadable files.

Enabled: Turns on detection and triggering.

Assay Provider: Use this provider for running assay import runs.

For example, an elevated 'service account' could be used. It is strongly recommended that this user has elevated permissions to perform updates, deletes, etc.

Run as username: The file watcher will run as this user in the pipeline.

By default the option you clicked to open this wizard is selected but you can change this selection from available options on the dropdown menu.

Pipeline Task: The type of filewatcher task you want to create.

Type: Currently supports one value 'pipeline-filewatcher'.

Description: A description for the trigger.

Configuration options and on-screen guidance may vary for each task type. The two panels of the Create Pipeline Trigger wizard define a file watcher.

Manage File Watcher Triggers: Click to see the table of all currently configured file watchers.

Click one of the links below Create a trigger to.

If enabled modules include any script pipelines, they will also be listed.

Different types of folders include different built in file watcher tasks.

Depending on your project's enabled module set, options for trigger creation may vary.

In a study folder, you can instead click the Manage tab, then click Manage File Watchers.

Navigate to the folder where you want the files to be imported, i.e.

You can change this default behavior and specify that the files be moved to a different location during configuration of the file watcher. When files are detected, by default they are moved (not copied) to the LabKey folder's pipeline root where they are picked up for processing. If file name patterns are not sufficiently distinct, you may encounter conflicts among file watchers acting on the same files. Use caution when defining multiple file watchers to monitor the same location. Multiple file watchers can be set up to monitor a single directory for file changes, or each file watcher could watch a different location.Įach File Watcher can be configured to be triggered only when specific file name patterns are detected, such as watching for '.xlsx' files, etc. When new or updated files appear in a monitored directory, a specified pipeline task (or set of tasks) will be triggered. Learn more or contact LabKey.įile Watchers monitor directories on the file system and perform specific actions when desired files appear. Premium Feature - Available with all Premium Editions of LabKey Server.

Filewatcher dmedia