Learn how to use DRS URIs as inputs to workflows in two different ways.
You can use DRS URIs as inputs to workflows in two ways: 1) via the data table, or 2) via direct paths in the workflow inputs configuration. In both cases, the workflows should access and process the data without further intervention. See example screenshots of each below.
DRS URIs, egress, and your data's cloud locationFor data files with copies in both Google and Azure cloud storage, Terra will resolve DRS URIs to fetch the data from the cloud of your VM. In other words, when working in Terra on GCP, Terra will automatically use files stored in GCS, and when working in a Terra on Azure workspace, Terra will pull the Azure data file. This saves egress costs by avoiding copying data from a different cloud provider. This applies to some important datasets like open access 1000 genomes.
DRS URIs in a workspace data table
Note: The workflow configuration references the table with the format "this.object"
Closeup view
DRS URIs entered directly as workflow input
Closeup view
Configuring workflows with DRS URIs (PFB or TDR prefix)
If you export your data table from a data repository or the Terra Data Repo, it includes a pfb or tdr prefix in the data table.
You must include the pfb or tdr prefix when running a workflow on data from a tableThe (required) attribute syntax is this.pfb:file-type
or this.tdr:file-type
.
Note: This syntax will show up in the drop-down menu when you click into the attribute field (see screenshot below - click on image to enlarge).