 What is the difference
between TSA and dbEST/SRA/trace archive? |
 |
Sequences in dbEST/SRA/trace archive are single-pass reads are determined by different sequencing techniques. TSA sequences are computationally assembled sequences
from these single-pass reads.
| Can I submit single-pass
reads to TSA? |
|
Single-pass reads may be submitted as part of a TSA project providing they are in the minority and add additional information to the transcriptome project.
| What is the difference
between TSA records from dbEST assemblies and TSA records from SRA/trace archive assemblies? |
|
Both flatfiles will display TSA as the division code, 'TSA:' in the beginning of the DEFINITION line, and the same KEYWORDS. In addition, each type must be registered as a project. However,
for dbEST derived TSA records there will be an assembly block displayed on the flatfile which lists the ESTs that were used to create the assembly.
See EZ000001 for an example. TSA records derived from SRA/trace archive sequences will not have a assembly block but instead a DBLINK number that
will link to the assembly archive sequence data that is the basis for the assembly. See EZ007475 for an example.
| Is annotation required? |
|
Annotation is not required.
| Can I submit an assembly of EST/SRA/trace archive data
generated by another group?
|
|
No. All submitted assemblies must be derived from primary data generated by the same group.
| Where should clonally
derived sequences be submitted? |
|
These sequences should be submitted to GenBank . Only computationally assembled sequences by a program such as CAP3 should be submitted to TSA.
| 
