Full gene names are lowercase italic, and gene symbols are three or more lowercase letters and are also italicized. The letters should be unique with respect to other named zebrafish mutants and genes. Gene symbols should not be the same as a gene abbreviations in mouse or human except in cases of established orthology where the gene symbol should match that of the orthologue. Zebrafish gene designations should not be preceded by 'Z' or 'Zf'include any reference to species, for example d, dr, z or zf. The use of punctuation such as period and hyphens in gene names or symbols is discouraged, except under specific circumstances described below.
Gene names should be registered at ZFIN.
Tg indicates transgene. Within the parentheses, the most salient features of the transgene should be described. Brevity and clarity in the transgene name are favored, in general, over exhaustive detail. Regulatory sequences should be listed to the left of the colon, and coding sequences to the right of the colon. Not all transgenic constructs will have both regulatory and coding elements, and in this case, the colon will not be used. In cases where a construct utilizes sequences from a named gene, it should contain the standard zebrafish lowercase symbol for that gene. The entire transgene name should be italicized.
For those cases where a specific transcript or transcript promoter of a gene is used, the transcript number or name should be used. It should be noted that the use of hyphens here is distinct from the use of hyphens in regulatory or coding sequence fusions as discussed below. The hyphen in transcript names is an integral part of the transcript name and demarcates the transcript number for a gene.
Examples: original construct: Tg1(uxs1:GFP); subsequent construct: Tg2(uxs1:GFP); additional constructs: Tg#(uxs1:GFP)
When a mutated form of a gene is used in a construct the mutations in the gene are noted using underscore followed by the amino acid substitution. If the mutation is a nucleotide change, it is noted by underscore, then nucleotide number followed by the original nucleotide>mutant nucleotide. It is critical that an accession number be included in the manuscript's description of the mutant because some genes have multiple entries/sequences. This accession number will be noted on the construct page.
Example: Amino acid mutation is in rat Fgf8 at position 245 where S has been replaced by A: Tg(pax2a:Rno.Fgf8a_S245A)
Example: Nucleotide mutation is in Human gene MPZ at position 1026 where T has been replaced by A: Tg(Hsa.MPZ_1026T>A:EGFP)
Sometimes within a single construct, there are multiple cassettes, each containing regulatory and coding sequences. In this case, it is necessary to distinguish between what is coding in the first cassette with what is regulatory in the second. Multiple cassettes may be distinguished using a comma. In the following example, isl3 promoter drives GAL4, and UAS drives GFP.
If 2 independently injected constructs can be experimentally demonstrated to be integrated in the same locus, each construct name will be separated by a semi-colon. The line named with the plasmid contents separated by a ; instead of a , since the , is used to separate cassettes on the same construct. This line of transgenic fish will be assigned one line number. Note: if it is later found that the constructs integrated in different positions an additional line number. will be needed.
When one promoter is used to drive more than one gene, a comma is used to separate the gene names. This includes uni- & bidirectional promoters.
For those situations where a construct utilizes enhancers or promoters from genes that regulate two or more genes, only one of the genes should be represented in the name such that the gene with the lowest number or gene closest to the promoter is listed.