If your workspace already includes a data table with at least the number of rows you need, you can edit individual cells by clicking on the pencil icon in the cell you want to change:

1) Check the box to the left of the row(s) you want to delete, or (to delete the entire table) select all rows from the dropdown

2) Click the three vertical dots at the top and select "Delete Data"

1) From the workspace you want to copy from, select the rows you want to copy (or all rows, if you want the entire table) 

2) Click the three vertical dots at the top and select "Export to Workspace" to select the workspace to copy to

To download all rows
Select the Download all Rows button at the top of the table

To download particular rows
    1. Select the rows to download
    2. Click the three vertical dots to the right of the Download all Rows button and
        select "Download as tsv"

1. Open in your favorite spreadsheet editor to edit. If you are adding columns of metadata, column headers will be the attribute name of the new column in the updated data table. 
2. Save the file as "tab-separated values" or "tab-delimited text"  Your editor may give you a warning, but we assure you, it's fine! Also, Terra will completely ignore the name you give the file. It's the root entity in the first column header that determines the table name in the workspace.  a=A note about "tsv" versus "txt" file extensions   Depending on what spreadsheet editor you use, when you save in the proper format, your spreadsheet file may have either a '.tsv or' '.txt' extension. Terra will accept either of these file extensions.

Click the blue "+" icon at the top right of the table column in the TABLE page of the workspace and follow the directions.

	A note about overwriting table rows
	When your tsv load file has the same entity (name) as a table already in the workspace, you may get an error message when you try to upload about overwriting data (see screenshot). Note that Terra will only overwrite data rows with the same ID (in the first column). If the tsv (load) file includes different IDs, the data rows will be added to the existing table.

The header row defines the workspace table column headers.

Whatever names you give column headers will be what is in the workspace data table.

Terra requires a particular format for the first (ID) column

entity:your-entity-name_id The parts in red (entity: and _id) must be typed in exactly as shown. The entity: is the kind of data in the table. It's what a workflow will use as input. You can name the entity whatever helps you organize your data. For example, the first column header of a table of samples would read entity:sample_id and the first column of a table of unicorns would read entity:unicorn_id.

Additional columns 
For a minimum data table, the second column is generally the input data you'll use for a workflow. If it's FASTQ files (as above), you could use fastq for the second column header. You can use any header name that helps you keep the data organized. 

In your spreadsheet editor it will look like this (you will likely have different values for sample and fastq):

ID (first column)
You can use any name you want for the ID. Note that you cannot have two rows with the same entity_id. You may use the sample_id to connect data in separate tables (see below). 

Additional columns
Additional columns include data and metadata for each entity. For example, in the example sample table, you'd add the link to the FASTQ file in a Google bucket in the fastq column.

	Attributes that reference data files must include the full path name
	gs://bucket_name/file_name

Your editor may give you a warning, but we assure you, it's fine! Also, Terra will completely ignore the name you give the file. It's the root entity (in the first column header) that determines the table name in the workspace. 
 

1.  Click on the "+" sign in the blue circle at the top of the left TABLES column        (in the orange rectangle in the screenshot below)
2. Select the "upload" option 

The name you give your table truly is flexible (unless you want to take advantage of Terra's default entity types with pre-defined relationships). For example, you could make the following tsv file:

When you upload it to the same workspace, you would see a unicorn data table with two unicorns, in addition to the original sample table:

You may have many samples in a data table, but want to do some testing with just three samples. You want to use the same three samples every time, and they're sprinkled throughout the sample table. To avoid having to manually select the exact samples you want every time you run a workflow, you can define subsets of the data in set table.

If you choose a subset of input data and run a workflow on it, Terra will automatically generate a set of the entities you ran on. To learn how to generate a set automatically by running a workflow, see the Data Tables QuickStart Part 3.

Set tables can also be used as inputs for some workflows that accept arrays as inputs

• The Optimus pipeline takes in multiple lanes of a sample, but outputs one file that corresponds to the sample, not the individual read lanes.
• Another example, familiar to cancer researchers, is the CNV_Somatic_Panel_workflow, which generates a single Panel of Normals (PoN) from a list of normal samples. The PoN is used in variant calling to filter out systemic errors that occur when reads are processed.

For hands-on practice using tables to run array data, see the Data Tables QuickStart Part 3 and Part 4.

Sets of entities are also like spreadsheets, and the process to create them from scratch is much the same as for single entity data tables. You'll work in a spreadsheet editor, save as "tab-delimited text" and upload the file as outlined above.

In a sets table spreadsheet, the first column is the unique set ID and the second column is the entity_id (in a different table). There is a row for every member of a set.

	Tip title
	Tip text.

	First column (set ID) header formatting requirements membership:your-entity-name_set_id
	Second column header formatting requirements "your-entity-name" comes from the table that stores the data pieces in the group - such as the sample table.

The parts in red (membership: and set_id) must be typed in exactly as shown, and your-enrity-name must match name of the original data table. It's the table that contains links to the data files that a workflow will ultimately use as input.

Notice in the example below that the same specimen (neurons2k_lane2) is in both mouse-set1 and mouse-set2:

 

Pairs table in Terra

Tables of pairs are also like spreadsheets, and the process to create them from scratch is much the same as for single entity data tables. You'll work in a spreadsheet editor, save as "tab-delimited text" and upload the file as outlined above. 

Pairs table tsv file (in a spreadsheet)

Note that the pairs table references the particpant_id and the sample_ids of the case and the control sample (from the sample table). 

	Tip title
	Tip text.

	First column (set ID) header formatting requirements entity:pair_id
	Second column header formatting requirements case_sample
	Third column header formatting requirements control_sample
	Fourth column header formatting requirements participant

The parts in red must be typed in exactly as shown, and the case_sample and control_sample IDs must match names in the sample data table. It's the table that contains links to the data files that a workflow will ultimately use as input.

Since the pairs table references both the participant_id and the sample_id, you will need to create and upload both participant and sample data tables before the pairs table.

Order to upload

Any tsv that references another tsv must be loaded after the primary reference.

1. Participant tsv
2. Sample tsv
3. Pairs tsv

For example, when you run Mutect2, if you uploaded the tables out of order or without selecting that checkbox, the workflow will fail because it reads from the pair table but has no knowledge of the sample table from which the pair table is supposed to read.