template for browser track,

[ValWood]

include basic contents in ticket and template header
( paper, datatype, author)

| Column | Contents (Example) | |
|----------|---------------------------------------------------------------------------------------------|-----------|
| 1 (A) | Data type (Mandatory): i.e. Transcripts, Chromatin binding, Nucleosome positioning, Poly(A) sites, Replication origins) | |
| 2 (B) | Track label (Mandatory): See below for format and examples*** | |
| 3 (C) | Assayed gene product (Fkh2) | |
| 4 (D) | Strain background (Mandatory) i.e. h- cdc25-22, leu1-1; (Multiple entries allowed) | |
| 5 (E) | WT or mutant (Mandatory): (strains with only background mutations are considered WT) | |
| 6 (F) | Mutant alleles i.e. clr4delta, dfp1-3A; (Multiple entries allowed) | |
| 7 (G) | Conditions i.e. YES, high temperature; glucose MM, standard temperature + HU | |
| 8 (H) | Comment Free-text field for additional information; (Multiple entries allowed) | |
| 9 (I) | Growth phase or response (Mandatory): i.e. Vegetative growth, meiosis, quiescence, glucose starvation, oxidative stress, heat shock; Multiple entries allowed if the track combines data | |
| 10 (J) | Strand (Forward, reverse) | |
| 11 (K) | Assay type (Mandatory): i.e. Tiling microarray, RNA-seq, HT sequencing | |
| 12 (L) | First author surname (Mandatory) | |
| 13 (M) | Publication year (Mandatory) | |
| 14 (N) | PubMed ID (Mandatory) | |
| 15 (O) | Database i.e. GEO, ArrayExpress | |
| 16 (P) | Study ID i.e. GSE110976, PRJEB7403 | |
| 17 (Q) | Sample ID i.e. GSM3019628, ERS555567; Multiple entries allowed | |
| 18 (R) | Data file type (Mandatory): i.e. bigwig, bed) | |
| 19 (S) | File name (Mandatory): Name given to submitted data file relevant to the track | |

• Format for track label “Assayed gene product” “Data type” “in mutant” “during Growth phase or response” “additional experimental detail of importance (Conditions, Strain background)” “; repeat” “(strand)” “- First author (Publication year)”

• URL for dataset

• Other info

[ValWood]

instead, when we open a browser ticket,

We will provide minimal information, and the template should provide a link to a Google spreadsheeet with the column, rather than putting into the tracker.

Any restricted data could be in a pull down

[PCarme]

I have made this Google Spreadsheet https://docs.google.com/spreadsheets/d/1M19o0VRF_GNK0_fu2tuiPkRnNtrK37yGWlx9aHVSsNc/edit?usp=sharing

@ValWood @kimrutherford Any thoughts or suggestions ?

[ValWood]

Looks good