Comments
- Add Free Text Comment
- MIMS Comment
- MIGS Comment
- MIMARKS Comment
- MIENS Comment
- GenomeAnnotation Comment
- GenomeDataAssembly Comment
Add Free Text Comment
WORK IN PROGRESS
MIMS Comment
WORK IN PROGRESS
Add
WORK IN PROGRESS
Remove
WORK IN PROGRESS
MIGS Comment
WORK IN PROGRESS
Add
WORK IN PROGRESS
Remove
WORK IN PROGRESS
MIMARKS Comment
WORK IN PROGRESS
Add
WORK IN PROGRESS
Remove
WORK IN PROGRESS
MIENS Comment
WORK IN PROGRESS
Add
WORK IN PROGRESS
Remove
WORK IN PROGRESS
GenomeAnnotation Comment
WORK IN PROGRESS
Add
WORK IN PROGRESS
Remove
WORK IN PROGRESS
GenomeDataAssembly Comment
Add
GenomeDataAssembly Comment -> Add opens a dialog that adds a Structured Comment describing the sequencing and assembly work done for the current sequence.
What is a Structured Comment? Some sequence submitters have organism and other metadata that does not fit into the controlled list of GenBank qualifiers but that is significant for the complete description of a sequence.
To collect and display such additional metadata in sequence records, GenBank uses a Structured Comment, which consists of tag (field)-value pairs that are contained within START and END tags. The START and END tags function as delimiters for parsing.
The Genome Data Assembly comment appears in the COMMENT section of sequence record and is framed by the default tags ##Genome-Assembly-Data-START## and ##Genome-Assembly-Data-END##.
Genome submissions require assembly information to be included within the Genome Assembly-Data structured comment. This structured comment includes the following metadata:
- Assembly Name: a short name suitable for display (for example, LoxAfr_3.0 for a Loxodonta africana assembly, version 3.0)
- Assembly Method: includes version or date the program was run (for example, Newbler v. 2.3 or Celera Assembly v. May 2010)
- Genome Coverage (for example, 12x)
- Sequencing Technology (for example, ABI 3730; 454 GS-FLX Titanium; Illumina GAIIx)
The Assembly Name is optional. Assembly Method requires 'v. ' between the algorithm name and its version (or the month and year it was run). If more than one sequencing technology was used, separate them with a semi-colon (for example, Sanger; Illumina GAIIx).
Remove
GenomeDataAssembly Comment -> Remove deletes the Structured Comment describing the sequencing and assembly work applied the current sequence.
What is a Structured Comment? Some sequence submitters have organism and other metadata that does not fit into the controlled list of GenBank qualifiers but that is significant for the complete description of a sequence.
To collect and display such additional metadata in sequence records, GenBank uses a Structured Comment, which consists of tag (field)-value pairs that are contained within START and END tags. The START and END tags function as delimiters for parsing.
The Genome Data Assembly comment appears in the COMMENT section of sequence record and is framed by the default tags ##Genome-Assembly-Data-START## and ##Genome-Assembly-Data-END##.
Genome submissions require assembly information to be included within the Genome Assembly-Data structured comment. This structured comment includes the following metadata:
- Assembly Name: a short name suitable for display (for example, LoxAfr_3.0 for a Loxodonta africana assembly, version 3.0)
- Assembly Method: includes version or date the program was run (for example, Newbler v. 2.3 or Celera Assembly v. May 2010)
- Genome Coverage (for example, 12x)
- Sequencing Technology (for example, ABI 3730; 454 GS-FLX Titanium; Illumina GAIIx)
The Assembly Name is optional. Assembly Method requires 'v. ' between the algorithm name and its version (or the month and year it was run). If more than one sequencing technology was used, separate them with a semi-colon (for example, Sanger; Illumina GAIIx).
For more information please see the full documentation for NCBI Genome Workbench Editing Package.
Current Version is 3.8.2 (released December 12, 2022)
General
Help
Tutorials
- Basic Operation
- Using Active Objects Inspector
- Configure tracks and track display settings
- Working with Non-Public Data
- Viewing Multiple Alignments and Trees
- Broadcasting
- Genes and Variation
- Generating and Viewing Sequence Overlap Alignment
- Working with BAM Files
- Loading Tabular Data
- Working with VCF Files
- Sequence View Markers
- Opening Projects in Genome Workbench
- Publication quality graphics (PDF/SVG image export)
- Editing in Genome Workbench
- Create Protein Alignments using ProSplign
- GFF-CIGAR export for alignments
- Exporting Tree Nodes to CSV
- Generic Table View
- Running BLAST search against custom BLAST databases
- Using Phylogenetic Tree
- Coloring methods in Multiple Alignment View
- Displaying translation discrepancies
- Searching in Genome Workbench
- Graphical View Navigation and Manipulation
- Using the Text View to Review and Edit a Submission
- BAM haplotype filtering
- Displaying new non-NCBI molecules with annotations
- Creating phylogenetic tree from precalculated multiple alignment
- Creating phylogenetic tree starting from search
- Video Tutorials
General use Manuals
- Tree Viewer Formatting
- Tree Viewer Broadcasting
- Genome Workbench Macro
- Query Syntax in Genome Workbench and Tree Viewer
- Multiple Sequence Aligners
- Running Genome Workbench over X Window System
NCBI GenBank Submissions Manuals
- Table of Contents
- Introduction
- Genome Submission Wizard
- Save Submission File
- Reports
- Import
- Sequences
- Add Features
- Add Publication
- Comments
- Editing Tools