GenBank

What is table2asn?

table2asn is a command-line program that creates sequence records for submission to GenBank.

In general, table2asn will recognize files with the same basename as the input sequence file, and will output an ASN.1 (Abstract Syntax Notation 1) text file with the same basename and a .sqn suffix. Various optional output files can be generated, depending on the arguments used. For example: validation files (.val suffix) and a summary of the .val files (.stats suffix), a discrepancy report (.dr suffix), or a GenBank flatfile (.gbf suffix).

table2asn is the replacement of the older now-obsolete tool tbl2asn, with very similar operation. There are a few different argument values (discussed below) and several additional functions in table2asn compared to tbl2asn.

table2asn is available by anonymous FTP. Copy the version for your platform, uncompress the file, rename it to "table2asn" and set the permissions, as necessary for the platform. This page provides a brief description of the more common uses for table2asn, but more detail is provided in the table2asn_readme.txt file.

6 types of input data files

1. Template file containing a text ASN.1 Submit-block object (suffix .sbt). [Required]
2. Nucleotide sequence data in FASTA format (suffix .fsa). [Required]
3. 5-column Feature Table (suffix .tbl). [Required only if including annotation in this format]
4. Protein sequence (suffix .pep). [Optional; these are rarely needed.]
5. Quality Scores (suffix .qvl.) [Optional]
6. Source Table (suffix .src.) [Optional]

Generating the .sqn file for submission

• The minimum requirements to generate an ASN .sqn file using table2asn are one .sbt file and one or more .fsa files.
• The files are placed in a source directory and a series of command line arguments are used to generate the .sqn files.
• table2asn will generate a .sqn for every .fsa file in the directory, plus any of the corresponding optional files that may be present. The other files must have the same file name prefix as their corresponding .fsa. (for example helicase.fsa and helicase.tbl).

Command Line Arguments

To get a summary of the command line arguments that table2asn has at its disposal, run: table2asn -help

Please be aware that the argument values of a few functions were changed in table2asn, compared to the older tbl2asn. You can see all the arguments by typing "table2asn -help", but this table shows the ones that might have the most impact:

table2asn command line argument changes from tbl2asn

Here is a partial list of commonly used table2asn arguments:

Example Command Lines

• Single non-genome submission: a particular .fsa file, and only 1 sequence in the .fsa file and the source information is in the definition line of the .fsa file:
  • table2asn -t template.sbt -i x.fsa -V v
• Batch non-genome submission: a directory that contains .fsa files, and multiple sequences per file, and the source information is in the definition line of the .fsa files:
  • table2asn -t template.sbt -indir path_to_files -a s -V v
• Genome submission: a directory that contains multiple .fsa files of a single genome, and one or more sequences per file and the source information is in the definition line of the .fsa files:
  • table2asn -t template.sbt -indir path_to_files -M n -Z
• Genome submission for the most common gapped situation (= runs of 10 or more Ns represent a gap, and there are no gaps of completely unknown size, and the evidence for linkage across the gaps is "paired-ends"), and the source information is in the definition line of the .fsa files:
  • table2asn -t template -indir path_to_files -M n -Z -gaps-min 10 -l paired-ends

Before submitting your .sqn files to GenBank,

• Review the .stats file for the summary of validator problems, and correct any error-level or reject-level errors. Details of the errors are in the .val files. Taxonomy-related errors about missing lineages can generally be ignored. However, if there is annotation and the genetic code is not the standard code, then include the correct code in the .fsa definition line as shown in the .fsa definition line , or with the "-j" in the command line, to avoid errors. For more information see Validation or Discrepancy Report Error Explanations and Validation Error Explanations for Genomes.
• For genomes and TSA submissions review the discrepancy report results in the .dr files, especially checking for FATAL tests.

Creating the template file (.sbt)

• Go to the Create Submission Template page
• Fill in the boxes
• Click on "Create Template"
• SAVE the file as template.sbt

Nucleotide sequence and FASTA defline formats (.fsa)

• No size limit on nucleotide sequence, generally.
  • There is a technical length limit of 2,147,483,647bp (= 2^31)
• Each sequence in a FASTA file must have a definition line (defline) beginning with a '>'.
• Minimum requirements for the FASTA defline are:
  • SeqID (sequence identifier) which is the text between the '>' and the first space. The SeqIDs limits are:
    • Must be <50 characters
    • Can only include letters, digits, hyphens (-), underscores (_), periods (.), colons (:), asterisks (*), and number signs (#).
  • Organism and related information (unless organism information is included with -j at the command line or in a .src file )
  • Optional defline information is in this list of source modifiers and includes:

Biological

• strain [strain=S288C]
• isolate [isolate=CWS1]
• chromosome [chromosome=XVI]
• plasmid [plasmid-name=pBR322]

Other elements

• topology [topology=circular]
• location [location=mitochondrion]
• molecule [moltype=mRNA] (DNA is the default)
• technique [tech=wgs]
• genetic code [gcode=4]

Here is the list of source modifiers. See the Taxonomy pages for the genetic code values.

Example FASTA

>Sc_16 [organism=Saccharomyces cerevisiae]
tataggcgaatcgagtatattattttttctcaacatatgtat
atgaacatgagaatatatttataggaatgtataaaattgtga
cctctcctgctattttagttactgattttatgtatgtagggg
gaataggggctgcctttcttaatgcagttttaattttttctt
ttaattttttcttagtaaaattatttaaagtaaagattaatg
gaataaccattgcgcttttttttacagtttttggtttttcat
tttttggaaaaaatattttaaatattttacctttttatttag
ggggtattttatatagtatctatacttcaacagatttttctg
aacatatagttcctattgctttttcaagtgcattagcccctt
ttgtaagcagtgttgctttttatggagaaatatcctatgaaa
catcatatataaatgcaattttaattggtattttaattggtt
ttatagtggttcctttgtctaaaagtctttatgactttcatg
agggatatgatttatataatttaggttttacagcaggtt

Example batch FASTA

>Sc_16_1 [organism=Saccharomyces cerevisiae]
tataggcgaatcgagtatattattttttctcaacatatgtat
atgaacatgagaatatatttataggaatgtataaaattgtga
cctctcctgctattttagttactgattttatgtatgtagggg
gaataggggctgcctttcttaatgcagttttaattttttctt
ttaattttttcttagtaaaattatttaaagtaaagattaatg
aacatatagttcctattgctttttcaagtgcattagcccctt
ttgtaagcagtgttgctttttatggagaaatatcctatgaaa
>Sc_16_2 [organism=Saccharomyces cerevisiae]
catcatatataaatgcaattttaattggtattttaattggtt
ttatagtggttcctttgtctaaaagtctttatgactttcatg
agggatatgatttatataatttaggttttacagcaggtt
gaataaccattgcgcttttttttacagtttttggtttttcat
tttttggaaaaaatattttaaatattttacctttttatttag
ggggtattttatatagtatctatacttcaacagatttttctg

Feature table format (.tbl)

table2asn reads features from a five-column tab-delimited table called a Feature table. The feature table specifies the location and type of each feature. table2asn will process the feature intervals and translate CDSs into proteins. The first line of the table should contain the following information:

>Features SeqID

The SeqID must match the nucleotide sequence SeqID in the corresponding .fsa file.

Example Feature Table

>Feature Sc_16 
69 543 gene
 gene sde3p
69 543 CDS
 product SDE3P
 protein_id WS1030

Note that GenBank prokaryotic or eukaryotic genomes can use GFF3 files in a GenBank-specific format as annotation input, as described at Annotating Genomes with GFF3 or GTF files. In general, the qualifiers that can be included in a 5-column feature table (.tbl) file can be included in column 9 of the appropriate feature's row in a GFF3 file.

Protein sequence format (.pep)

• This file is not usually needed because GenBank generally presents on the conceptual translation of the nucleotide sequence, which will be automatically generated by table2asn.
• This file will substitute the automatically translated products of the CDS features with the provided protein sequences, so is only needed in unusual cases.
• It is FASTA file of the protein sequence, where the SeqID must match protein_id in the .tbl file

Example FASTA

>WS1030 [gene=sde3p] [protein=SDE3P]
MYKIVTSPAILVTDFMYVGGIGAAFLNAVLIFSFNFFL
VKLFKVKINGITIAAFFTVFGFSFFGKNILNILPFYLG
GILYSIYTSTDFSEHIVPIAFSSALAPFVSSVAFYGEI
SYETSYINAILIGILIGFIVVPLSKSLYDFHEGYDLYN
LGFTAG

Quality scores table format (.qvl)

• Provides Phrap/Consed quality scores.
• Has a defline with the corresponding SeqID from the .fsa file.
• Generates Seq-graph data that will be included with the nucleotide sequence of the .fsa file in the final .sqn file.

  >Sc_16
  51 63 70 82 82 82 90 90 90 90 86 86
  86 86 86 86 90 90 90 90 90 86 86 78...
  

Source table format (.src)

For sets of sequences, especially those with different sources, a tab-delimited source modifier table file can be created, with a name that has a .src extension. The first column in the file must be the SeqIDs of the sequences. The first row gives the names of the source qualifiers being added, separated by tabs. Any additional rows list the SeqID and source qualifiers for each sequence in the corresponding .fsa file.

SeqID organism strain isolate
Sc_16 Zea mays A69Y J平成90年6月2日x12