Difference between revisions of "FlyBase:Author Reagent Table (ART)"

From FlyBase Wiki
Jump to navigation Jump to search
m (updated reagent table template link)
 
(24 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
Wider use of identifiers and recognized symbols increases the transparency and reproducibility of biological research, while aiding curation into research databases.  
 
Wider use of identifiers and recognized symbols increases the transparency and reproducibility of biological research, while aiding curation into research databases.  
  
A spreadsheet format is convenient and flexible for the researcher and provides commonly used download options for readers of publications.
+
The table is designed to be used regularly during the course of a research project, recording reagents as they are received and/or used. Lab-wide use of a common reagent form would facilitate tracking of reagents within the lab.
  
The table is designed to be used regularly during the course of a research project, recording reagents as they are received and/or used. Lab-wide use of a common reagent form would facilitate tracking of reagents within the lab.  
+
A spreadsheet format is convenient and flexible for the researcher and provides commonly used download options for readers of publications. Use of the same format throughout (reagent data collection, submission for publication, post-publication downloads) reduces error-prone copying and pasting steps.
  
 
Providing information in a structured format that allows bulk downloads greatly facilitates curation into research databases.  
 
Providing information in a structured format that allows bulk downloads greatly facilitates curation into research databases.  
Line 11: Line 11:
 
In addition to reagents, unambiguous identification of specific genes studied is particularly helpful for genetic and genome databases, as well as for the larger research community.
 
In addition to reagents, unambiguous identification of specific genes studied is particularly helpful for genetic and genome databases, as well as for the larger research community.
  
<h1>Guidelines for creation of the Author Reagent Table</h1>
+
<h1>Download the ART template</h1>
  
 
{|class="wikitable"
 
{|class="wikitable"
 
|-
 
|-
|style="text-align: center; padding: 15px;"| <big>[http://flybase.org/journal/reagent_form_v2/Reagent.table.v2_template.xlsx Download template in XLSX format] [[Image:Reagent_table_tiny.png|link=http://flybase.org/journal/reagent_form_v2/Reagent.table.v2_template.xlsx |alt=Alt text|Title text]]</big>
+
|style="text-align: center; padding: 15px;"| <big>[http://flybase.org/journal/reagent_form_v2/Reagent.table.v2_template.xlsx Download template in XLSX format] [[Image:Reagent_table_blank_small2.png|link=http://flybase.org/journal/reagent_form_v2/Reagent.table.v2_template.xlsx |alt=Alt text|Title text]]</big>
 
|}
 
|}
 +
 +
<h1>Guidelines for creation of the Author Reagent Table</h1>
 +
 +
[http://flybase.org/journal/reagent_form_v2/ReagentTable.v2.1.guidelines.docx These guidelines are also available in .docx format].
  
 
Some of the constraints below are imposed to allow automated parsing of the table.
 
Some of the constraints below are imposed to allow automated parsing of the table.
Line 22: Line 26:
 
<h3>Columns (general):</h3>
 
<h3>Columns (general):</h3>
 
<ol>
 
<ol>
<li>Column order and headings must be preserved.</li>
+
<li>'''Column order and headings''' must be preserved.</li>
<li>Columns A-I should not be removed, even if not used.</li>
+
<li>Columns A-E should not be removed, even if not used.</li>
<li>Columns can be appended (J, K, etc.) for internal use.</li>
+
<li>Additional columns can be appended (F, G, etc.) for internal use.</li>
 
</ol>
 
</ol>
  
 
<h3>Rows (general):</h3>
 
<h3>Rows (general):</h3>
 
<ol>
 
<ol>
<li>Row titles must be preserved.</li>
+
<li>'''Row titles''' (preceding the parentheses) must be preserved.</li>
<li>Row one (column headings) should not be removed; row 2 (headings with instructions) may be removed.</li>
+
<li>Row one (column headings) should not be removed.</li>
 +
<li>Row two (headings with instructions) may be removed.</li>
 
<li>Order of the rows can be changed.</li>
 
<li>Order of the rows can be changed.</li>
 
<li>Clustering of multiple reagents of one type recommended, but is not mandatory.</li>
 
<li>Clustering of multiple reagents of one type recommended, but is not mandatory.</li>
 
<li>Colors are entirely optional: can be removed or changed.</li>
 
<li>Colors are entirely optional: can be removed or changed.</li>
 
<li>Data types indicated on template that are not used can be removed.</li>
 
<li>Data types indicated on template that are not used can be removed.</li>
<li>Data types not represented in the template: use “other”. (If appropriate, contact us about adding a category.)</li>
+
<li>Data types not represented in the template: use “other”.</li>
 
</ol>
 
</ol>
  
<h3>Column A: Data type (mandatory)</h3>
+
<h3>Column A: Reagent type (mandatory)</h3>
 
<ol>
 
<ol>
<li>Row titles cannot be changed</li>
+
<li> Row title (preceding parentheses) cannot be changed.</li>
<li>See additional information in the section “Rows (general)” above.</li>
+
<li> For information concerning specific reagent types, see “Descriptions of reagent types” section below.</li>
 +
<li> If appropriate, include species within parentheses. Use full genus and full species for first mention; thereafter, initial for genus may be used.</li>
 +
<li> If appropriate, indicate sex after species (within the parentheses); separate by comma, space.</li>
 +
<li> See additional information in the section “Rows (general)” above.</li>
 
</ol>
 
</ol>
  
<h3>Column B: Experimental species (mandatory)</h3>
+
<h3>Column B: Designation used in publication (mandatory)</h3>
 
<ol>
 
<ol>
<li>Use genus initial with full species OR full genus and full species</li>
+
<li>This is a free-text field; there are no formatting constraints, except for separation of multiple entries by semi-colon, space.</li>
<li>Use “NA” rather than leaving blank</li>
+
<li>Should indicate exactly how the reagent is referred to in the publication.  If several designations are used for one reagent, can include more than one entry, separated by semi-colon, space. If one designation has been used to refer to several different reagents, list each reagent separately and include a unique identifier or description parenthetically.</li>
 +
<li>If there is a semi-colon within the designation used, add double quotes around the entire phrase.</li>
 +
<li>Additional defining information can be included parenthetically (if brief).</li>
 
</ol>
 
</ol>
  
<h3>Column C: Symbol/name used in publication (mandatory)</h3>
+
<h3>Column C: Source or reference (mandatory)</h3>
 
<ol>
 
<ol>
<li>This is a free-text field (no formatting constraints, except for separation of multiple entries by semi-colon, space).</li>
+
<li>If reagent obtained from a public source, such as a stock center or company, list resource name.</li>
<li>Should indicate exactly how the reagent is referred to in the publication. If several designations are used for one reagent, can include more than one entry, separated by semi-colon, space. If one designation has been used to refer to several different reagents, list each reagent separately and include a unique identifier of some sort.</li>
+
<li>If not obtained from public source, but a published description is available, list the DOI or PMID for the publication.</li>
 +
<li>If reagent newly created in the publication, enter “this paper”.</li>
 +
<li>If none of the above, enter “other” and explain in Additional Information (Column E).</li>
 +
<li>If it is appropriate to indicate both a publication and a lab or researcher that provided the reagent, list the publication in this field and the lab or researcher in Additional Information.</li>
 
</ol>
 
</ol>
  
<h3>Columns D-F: Source (one of D-F mandatory)</h3>
+
<h3>Column D: Identifiers (not mandatory; use if possible)</h3>
<ol>
 
<li>Use of multiple columns allows sorting of source information into public repositories, publications, and laboratories.</li>
 
<li>In order of preference: use column D, if possible.</li>
 
<li>Columns D and F are free-text fields.</li>
 
<li>Column E should be in the form of a PubMed ID or the text “this paper”.</li>
 
</ol>
 
 
<h3>Column G: Identifiers (not mandatory; use if possible)</h3>
 
 
<ol>
 
<ol>
 
<li>Use the format “ID_source:identifier” with a colon and no spaces. Separate multiple entries with a semi-colon, space.</li>
 
<li>Use the format “ID_source:identifier” with a colon and no spaces. Separate multiple entries with a semi-colon, space.</li>
<li>If possible, use the recommended abbreviation for the ID_source (see below)</li>
+
<li><span style="color:red">PLEASE DO NOT GUESS</span>. If you are not certain, leave column D blank and enter in the ‘Additional Information’ (column E) any pertinent information about the origin of the reagent (e.g. laboratory from which reagent was obtained).</li>
 +
<li>If possible, use the recommended abbreviation for the ID_source; see list in last section, below. These are also included in the downloadable [http://flybase.org/journal/reagent_form_v2/ReagentTable.v2.1.guidelines.docx ART Guidelines, .docx format].</li>
 
<li>Multiple identifiers, even if redundant, are useful for validation. In some case a more general identifier (for a stock, for instance) can be combined with a more precise identifier (for the allele of interest in that stock).</li>
 
<li>Multiple identifiers, even if redundant, are useful for validation. In some case a more general identifier (for a stock, for instance) can be combined with a more precise identifier (for the allele of interest in that stock).</li>
 
<li>Inclusion of database identifiers is strongly encouraged to facilitate accurate incorporation of published data into appropriate biological databases.</li>
 
<li>Inclusion of database identifiers is strongly encouraged to facilitate accurate incorporation of published data into appropriate biological databases.</li>
 
</ol>
 
</ol>
 
+
<h3>Column H: New Reagent (mandatory for newly described reagent)</h3>
+
<h3>Column E: Additional information</h3>
 
<ol>
 
<ol>
<li>Use if “this paper” entered in Column E</li>
+
<li>Mandatory if column C entry is “this paper” or “other”. Description of new reagent or laboratory from which reagent obtained.  (Free text)</li>
<li>Free-text field (no constraints on format).</li>
+
<li>For antibodies, indicate dilution in parentheses (to avoid auto-formatting problems).</li>
 +
<li>Other pertinent information, including pointers to supplementary information or Methods section, if appropriate.  (Free text)</li>
 
</ol>
 
</ol>
  
<h3>Column I: Comments (optional)</h3>
+
Additional columns can be added for internal purposes (and removed prior to submission for publication): tracking acquisition by the lab, lab-specific stock numbers, storage location in the lab, comments about problems or QC, etc.
<ol>
 
<li>Free-text field</li>
 
<li>For public consumption</li>
 
</ol>
 
  
Additional columns can be added for internal purposes (and removed prior to submission for publication): tracking acquisition by the lab, lab-specific stock numbers, storage location in the lab, comments about problems or QC, etc.
+
<h3>Descriptions of reagent types</h3>
 +
<ul>
 +
<li>'''Gene''' (indicate species) - not strictly a reagent, but unambiguous identification critical for genetic research and genetic databases.</li>
 +
<li>'''Strain, strain background''' (indicate species) - applies to whole organism; includes bacterial and virus strains or isolates. Indicate sex, if applicable.</li>
 +
<li>'''Genetic reagent''' (indicate species) -  applies to mutations and variants <span style="color:red">in whole organism</span>, including transgenically introduced constructs. For transgenic lines, indicate host species. Indicate sex, if applicable.</li>
 +
<li>'''Cell line''' (indicate species) -  if a primary cell line, describe in Additional Information.  Indicate sex, if applicable.</li>
 +
<li>'''Transfected construct''' (indicate species) - <span style="color:red">in cell line</span>. Generally, indicate species of cell line; use species of construct component if that is more relevant and explain in Additional Information.</li>
 +
<li>'''Biological sample''' (indicate species) - any other biological entity, ranging from isolated tissue to defined population; describe in Additional Information.  Indicate sex, if applicable.</li>
 +
<li>'''Antibody''' - include host organism common name and clonality (e.g., “mouse monoclonal”); include dilution used in Additional Information (within parentheses to avoid auto-formatting problems).</li>
 +
<li>'''Recombinant DNA reagent''' - traditional cultured clones, plasmids, cDNAs, etc., including recombinant DNA libraries.</li>
 +
<li>'''Sequence-based reagent''' - oligonucleotides, primers, morpholinos, etc.; indicate sequence. </li>
 +
<li>'''Peptide, recombinant protein''' - generally, commercially available reagents.</li>
 +
<li>'''Chemical compound, drug''' - generally, commercially available reagents.</li>
 +
<li>'''Commercial assay, kit''' - detection assays; labeling and sample preparation kits.</li>
 +
<li>'''Large-scale dataset''' - newly created or previously existing; include data repository accession number(s) in Identifiers column.</li>
 +
<li>'''Software, algorithm''' - newly created or previously existing.</li>
 +
<li>'''Other''' - miscellaneous other categories, including histological stains.</li>
 +
</ul>
  
 
<h1>Example of Completed Author Reagent Table</h1>
 
<h1>Example of Completed Author Reagent Table</h1>
  
Download [http://flybase.org/journal/reagent_form/Reagents_example.xlsx an xlsx version of the example below].
+
Download [http://flybase.org/journal/reagent_form_v2/Reagent.table.v2.example.xlsx an xlsx version of the example below].
 +
 
 +
[[File:reagent_v2_sample.png]]
 +
 
 +
<h1>List of ID_source abbreviations</h1>
 +
 
 +
Additional entries and improvements solicited. A minimum of 3 letters used to minimize potential conflicts.
 +
 
 +
<li>'''RRID'''</li>
 +
<li>'''DSHB'''</li>
 +
<li>'''ATCC'''</li>
 +
<li>Mouse-specific (strains and clones): '''MGC, JAX, NIG''', many others  (see http://www.findmice.org/)</li>
 +
<li>Zebrafish-specific (strains and clones): '''ZGC, ZIRC, EZRC''', others?</li>
 +
<li>Fly-specific (stocks, clones, cell lines): '''DGRC, BDSC, VDRC, FlyORF, TRIP, HMS, DGGR''' (Kyoto), '''NIG, THFC''', others</li>
 +
<li>Worm-specific (strains): '''CGC''', others?</li>
 +
<li>Yeast-specific (strains and plasmids): '''Euroscarf, YRC''', others?</li>
 +
 
 +
Companies:  Full name should be entered in column C; use first two words as identifier prefix (or one, if single word).  Do not simply indicate "Catalog #" -- this is too error-prone.
 +
 
 +
Databases:
 +
<li>'''NCBI''' (gene)</li>
 +
<li>'''HGNC'''</li>
 +
<li>'''MGI'''</li>
 +
<li>'''RGD'''</li>
 +
<li>'''WORMB'''</li>
 +
<li>'''FLYB'''</li>
 +
<li>'''ZFIN'''</li>
 +
<li>'''SGD'''</li>
 +
<li>'''POMB'''</li>
 +
<li>'''XENB'''</li>
 +
<li>'''TAIR'''</li>
 +
<li>'''IRD'''</li>
 +
 
 +
<li>'''GenBank, ENA, DDBJ'''</li>
 +
<li>'''GEO, ArrayExpress'''</li>
  
[[File:Reagent_table_filled_out.png]]
+
<li>'''dbSNP'''</li>
 +
<li>'''ClinVar'''</li>
 +
<li>'''ClinGen'''</li>

Latest revision as of 20:45, 25 January 2018

Rationale and Purposes

Wider use of identifiers and recognized symbols increases the transparency and reproducibility of biological research, while aiding curation into research databases.

The table is designed to be used regularly during the course of a research project, recording reagents as they are received and/or used. Lab-wide use of a common reagent form would facilitate tracking of reagents within the lab.

A spreadsheet format is convenient and flexible for the researcher and provides commonly used download options for readers of publications. Use of the same format throughout (reagent data collection, submission for publication, post-publication downloads) reduces error-prone copying and pasting steps.

Providing information in a structured format that allows bulk downloads greatly facilitates curation into research databases.

In addition to reagents, unambiguous identification of specific genes studied is particularly helpful for genetic and genome databases, as well as for the larger research community.

Download the ART template

Download template in XLSX format Alt text

Guidelines for creation of the Author Reagent Table

These guidelines are also available in .docx format.

Some of the constraints below are imposed to allow automated parsing of the table.

Columns (general):

  1. Column order and headings must be preserved.
  2. Columns A-E should not be removed, even if not used.
  3. Additional columns can be appended (F, G, etc.) for internal use.

Rows (general):

  1. Row titles (preceding the parentheses) must be preserved.
  2. Row one (column headings) should not be removed.
  3. Row two (headings with instructions) may be removed.
  4. Order of the rows can be changed.
  5. Clustering of multiple reagents of one type recommended, but is not mandatory.
  6. Colors are entirely optional: can be removed or changed.
  7. Data types indicated on template that are not used can be removed.
  8. Data types not represented in the template: use “other”.

Column A: Reagent type (mandatory)

  1. Row title (preceding parentheses) cannot be changed.
  2. For information concerning specific reagent types, see “Descriptions of reagent types” section below.
  3. If appropriate, include species within parentheses. Use full genus and full species for first mention; thereafter, initial for genus may be used.
  4. If appropriate, indicate sex after species (within the parentheses); separate by comma, space.
  5. See additional information in the section “Rows (general)” above.

Column B: Designation used in publication (mandatory)

  1. This is a free-text field; there are no formatting constraints, except for separation of multiple entries by semi-colon, space.
  2. Should indicate exactly how the reagent is referred to in the publication. If several designations are used for one reagent, can include more than one entry, separated by semi-colon, space. If one designation has been used to refer to several different reagents, list each reagent separately and include a unique identifier or description parenthetically.
  3. If there is a semi-colon within the designation used, add double quotes around the entire phrase.
  4. Additional defining information can be included parenthetically (if brief).

Column C: Source or reference (mandatory)

  1. If reagent obtained from a public source, such as a stock center or company, list resource name.
  2. If not obtained from public source, but a published description is available, list the DOI or PMID for the publication.
  3. If reagent newly created in the publication, enter “this paper”.
  4. If none of the above, enter “other” and explain in Additional Information (Column E).
  5. If it is appropriate to indicate both a publication and a lab or researcher that provided the reagent, list the publication in this field and the lab or researcher in Additional Information.

Column D: Identifiers (not mandatory; use if possible)

  1. Use the format “ID_source:identifier” with a colon and no spaces. Separate multiple entries with a semi-colon, space.
  2. PLEASE DO NOT GUESS. If you are not certain, leave column D blank and enter in the ‘Additional Information’ (column E) any pertinent information about the origin of the reagent (e.g. laboratory from which reagent was obtained).
  3. If possible, use the recommended abbreviation for the ID_source; see list in last section, below. These are also included in the downloadable ART Guidelines, .docx format.
  4. Multiple identifiers, even if redundant, are useful for validation. In some case a more general identifier (for a stock, for instance) can be combined with a more precise identifier (for the allele of interest in that stock).
  5. Inclusion of database identifiers is strongly encouraged to facilitate accurate incorporation of published data into appropriate biological databases.

Column E: Additional information

  1. Mandatory if column C entry is “this paper” or “other”. Description of new reagent or laboratory from which reagent obtained. (Free text)
  2. For antibodies, indicate dilution in parentheses (to avoid auto-formatting problems).
  3. Other pertinent information, including pointers to supplementary information or Methods section, if appropriate. (Free text)

Additional columns can be added for internal purposes (and removed prior to submission for publication): tracking acquisition by the lab, lab-specific stock numbers, storage location in the lab, comments about problems or QC, etc.

Descriptions of reagent types

  • Gene (indicate species) - not strictly a reagent, but unambiguous identification critical for genetic research and genetic databases.
  • Strain, strain background (indicate species) - applies to whole organism; includes bacterial and virus strains or isolates. Indicate sex, if applicable.
  • Genetic reagent (indicate species) - applies to mutations and variants in whole organism, including transgenically introduced constructs. For transgenic lines, indicate host species. Indicate sex, if applicable.
  • Cell line (indicate species) - if a primary cell line, describe in Additional Information. Indicate sex, if applicable.
  • Transfected construct (indicate species) - in cell line. Generally, indicate species of cell line; use species of construct component if that is more relevant and explain in Additional Information.
  • Biological sample (indicate species) - any other biological entity, ranging from isolated tissue to defined population; describe in Additional Information. Indicate sex, if applicable.
  • Antibody - include host organism common name and clonality (e.g., “mouse monoclonal”); include dilution used in Additional Information (within parentheses to avoid auto-formatting problems).
  • Recombinant DNA reagent - traditional cultured clones, plasmids, cDNAs, etc., including recombinant DNA libraries.
  • Sequence-based reagent - oligonucleotides, primers, morpholinos, etc.; indicate sequence.
  • Peptide, recombinant protein - generally, commercially available reagents.
  • Chemical compound, drug - generally, commercially available reagents.
  • Commercial assay, kit - detection assays; labeling and sample preparation kits.
  • Large-scale dataset - newly created or previously existing; include data repository accession number(s) in Identifiers column.
  • Software, algorithm - newly created or previously existing.
  • Other - miscellaneous other categories, including histological stains.

Example of Completed Author Reagent Table

Download an xlsx version of the example below.

Reagent v2 sample.png

List of ID_source abbreviations

Additional entries and improvements solicited. A minimum of 3 letters used to minimize potential conflicts.

  • RRID
  • DSHB
  • ATCC
  • Mouse-specific (strains and clones): MGC, JAX, NIG, many others (see http://www.findmice.org/)
  • Zebrafish-specific (strains and clones): ZGC, ZIRC, EZRC, others?
  • Fly-specific (stocks, clones, cell lines): DGRC, BDSC, VDRC, FlyORF, TRIP, HMS, DGGR (Kyoto), NIG, THFC, others
  • Worm-specific (strains): CGC, others?
  • Yeast-specific (strains and plasmids): Euroscarf, YRC, others?
  • Companies: Full name should be entered in column C; use first two words as identifier prefix (or one, if single word). Do not simply indicate "Catalog #" -- this is too error-prone. Databases:

  • NCBI (gene)
  • HGNC
  • MGI
  • RGD
  • WORMB
  • FLYB
  • ZFIN
  • SGD
  • POMB
  • XENB
  • TAIR
  • IRD
  • GenBank, ENA, DDBJ
  • GEO, ArrayExpress
  • dbSNP
  • ClinVar
  • ClinGen