Sequence Submission and Accession Assignment

  • Sequence submission and accession assignment are essential processes in bioinformatics that enable researchers to deposit nucleotide and protein sequence information in public biological databases and make these data accessible to the scientific community. Sequence submission involves providing biological sequence data, associated annotations, and supporting metadata to an appropriate repository. Accession assignment is the process through which a database assigns an identifier to an accepted record, allowing the record to be retrieved, cited, tracked, and linked to other biological information. These processes support data sharing, scientific transparency, reproducibility, genome annotation, comparative genomics, and the long-term preservation of biological research results.
  • Researchers submit sequences generated through genome sequencing, transcriptome analysis, polymerase chain reaction (PCR), molecular cloning, metagenomics, microbial identification, and other experimental approaches. Submissions may represent a single gene, a messenger RNA transcript, a coding sequence, a plasmid, a viral genome, a complete microbial genome, or a large collection of raw sequencing reads. The submission requirements depend on the type of data, the repository, the experimental design, and whether the sequence represents an individual record or part of a large-scale sequencing project. Correctly identifying the data type is an important first step because different databases and submission systems are designed for different kinds of biological information.
  • Several major repositories accept sequence submissions. GenBank, maintained by the National Center for Biotechnology Information (NCBI), accepts nucleotide sequence records and associated annotations. The European Nucleotide Archive (ENA), maintained by EMBL-EBI, and the DNA Data Bank of Japan (DDBJ), maintained by the National Institute of Genetics, provide corresponding submission and archival services. These three repositories participate in the International Nucleotide Sequence Database Collaboration (INSDC), through which eligible nucleotide sequence records are exchanged internationally. As a result, a sequence submitted to one participating archive can become accessible through the other archives. However, submission interfaces, validation procedures, and supplementary services may differ between repositories.
  • The appropriate repository depends on the type of data being submitted. Individual nucleotide sequences and assembled genomic records can be deposited in GenBank, ENA, or DDBJ. Large-scale sequencing reads are generally submitted to dedicated read archives, such as the Sequence Read Archive (SRA) and corresponding ENA and DDBJ resources. Genome projects may also require associated BioProject and BioSample records, which describe the overall research project and the biological material studied. Protein sequence records may be submitted through specialized or linked systems, depending on their origin and relationship to nucleotide records. Researchers should consult the current instructions of the selected repository before preparing a submission.
  • A sequence submission normally begins with the preparation of the sequence data and associated metadata. The nucleotide sequence must be represented in a supported format, such as FASTA, or another format accepted by the submission system. For annotated records, researchers may need to provide gene features, coding sequences, exon boundaries, transcript information, functional descriptions, and other biological annotations. Metadata can include the organism name, strain or isolate, specimen source, collection location when appropriate, sequencing method, sample characteristics, and references to publications or associated projects. Large sequencing submissions may additionally require information about libraries, experiments, sequencing platforms, and individual sequencing runs.
  • Sequence quality control is an important part of preparing a submission. Researchers should check for ambiguous bases, unexpected sequence lengths, contamination, vector sequences, sequencing errors, and possible sample mix-ups. For assembled genomes, relevant checks may include assembly completeness, contiguity, contamination, expected genome size, and consistency with the organism’s known biology. For raw sequencing reads, checks may include base quality, adapter contamination, read length, and library characteristics. The required checks depend on the type of submission, and not every repository imposes identical acceptance criteria. Depositing a sequence in a public database does not necessarily mean that the sequence has been independently confirmed to be biologically correct.
  • Metadata validation is equally important. An incorrect organism name, missing sample identifier, inconsistent strain designation, or incomplete experimental description can reduce the usefulness of a sequence record. Researchers should ensure that sample identifiers are consistent across sequence files, annotation files, and project records. Where appropriate, standardized taxonomic identifiers, controlled vocabularies, and accepted biological terminology should be used. For genome projects, the assembly metadata should accurately describe the source material, assembly method, sequencing technologies, and relevant quality information. Reliable metadata help users interpret records correctly and enable automated systems to connect related datasets.
  • Once the data are prepared, the researcher submits them through the repository’s online submission interface, command-line tools, or supported programmatic submission system. The submission system may request the sequence files, annotations, metadata, contact information, publication details, and information about data release. Depending on the submission type, multiple records may be grouped into a project, study, sample, experiment, or sequencing run. For example, a genome sequencing project may include a BioProject record describing the research, BioSample records describing the source organisms, raw sequencing reads, and an assembled genome record. These records have related but distinct identifiers because each describes a different level of the research data.
  • Following submission, automated validation checks are commonly performed. These checks may identify invalid sequence characters, formatting errors, missing required fields, inconsistent feature coordinates, unsupported feature annotations, or discrepancies between the submitted sequence and its metadata. Some checks assess biological plausibility, such as whether a coding sequence has a valid reading frame or whether the reported organism and sequence characteristics are consistent. Validation systems may generate warnings as well as errors. An error generally requires correction before the submission can proceed, whereas a warning may indicate an issue that needs review or explanation. The exact validation steps depend on the database and submission category.
  • Some submissions undergo additional review or communication with database staff. Submitters may be asked to clarify annotations, correct metadata, provide missing information, or resolve inconsistencies. Large genome submissions may involve additional assembly and annotation checks. Researchers should retain the original submitted files and review any modifications made during the submission process. It is also important to distinguish database validation from independent experimental verification: validation can identify many technical and metadata problems, but it cannot guarantee that every nucleotide or biological interpretation is correct.
  • After a record has been accepted, the database assigns an accession number. An accession number is a stable identifier used to retrieve and cite the record. For example, a GenBank nucleotide record may have an accession such as AB123456, while a RefSeq nucleotide record may use prefixes such as NM_ or NC_, depending on the record type. Genome assembly records at NCBI commonly use accessions beginning with GCA_ for GenBank assemblies or GCF_ for RefSeq assemblies. Raw sequencing datasets use other accession namespaces, such as SRA accessions beginning with SRR, SRX, SRP, or SRS, depending on whether the identifier refers to a run, experiment, study, or sample. These are examples of identifier types; actual assignments depend on the repository and submitted data.
  • Accession assignment is not simply a numbering step. The accession links a record to its sequence, annotations, metadata, and related database information. It provides a stable reference that researchers can use in publications, supplementary materials, analysis scripts, and scientific databases. A researcher who cites a sequence accession allows readers to retrieve the corresponding record and examine its contents. Accession numbers also facilitate cross-referencing between nucleotide archives, protein databases, genome browsers, literature records, and specialized biological resources. However, different accessions may refer to the same biological entity at different levels, such as a sample, sequencing run, assembled genome, transcript, or protein.
  • Accession numbers must be distinguished from version identifiers. A sequence record may retain its base accession while a version suffix changes when the underlying sequence is revised. For example, a nucleotide record may be represented as AB123456.1, with the suffix .1 identifying its first sequence version. If the sequence is subsequently revised, the version may become .2. The accession identifies the record, while the version suffix identifies a particular sequence version. Annotation or metadata changes do not necessarily increment the sequence version, depending on the database’s versioning rules. Researchers should therefore preserve the full accession and version when exact sequence identity is important for reproducibility.
  • Genome assembly accessions have their own versioning conventions. An assembly accession such as GCA_000001405.15 identifies a specific version of a GenBank assembly record, whereas a corresponding RefSeq assembly can have a separate GCF_ accession and version. Assembly versions are distinct from the accessions and versions of the individual chromosome or contig sequences that make up the assembly. They are also distinct from the version of the gene annotation applied to the assembly. These distinctions are important because sequence content, assembly structure, and annotation models can change independently. Reproducible genome analysis therefore requires the relevant assembly identifier, sequence versions when necessary, and annotation release.
  • Public release is another important aspect of sequence submission. Researchers may choose or be required to make records publicly available immediately or coordinate release with publication, subject to the repository’s policies. Some submissions can remain confidential until a specified release date. Data associated with manuscripts, collaborative projects, or patent applications may have particular timing requirements. Researchers should confirm the selected release conditions and applicable repository policies before submitting. After public release, records can generally be discovered and retrieved by other researchers, supporting data reuse, independent verification, and scientific collaboration.
  • Correcting or updating an existing submission is also part of database management. Researchers may need to revise a sequence, correct annotations, update organism information, add publication references, or provide additional metadata. Many databases allow submitters to update records through established procedures. Sequence changes may result in a new sequence version, while changes to descriptive information may be handled without changing the sequence version. In other cases, records may be suppressed, withdrawn, or replaced when necessary. Researchers should use the repository’s update process rather than submitting duplicate records without explanation, and they should preserve a record of important changes.
  • Sequence submission and accession assignment support a wide range of bioinformatics applications. Public nucleotide records provide reference data for sequence alignment, gene identification, genome annotation, phylogenetic analysis, comparative genomics, metagenomics, and variant interpretation. Raw sequencing archives allow researchers to repeat analyses using new methods or alternative reference genomes. Accession-linked metadata help connect sequence observations with biological samples and experimental conditions. In clinical and public-health research, reliable identifiers support traceability and comparison of genetic data, although privacy, consent, controlled access, and applicable regulations must be considered for sensitive human data.
  • Several challenges can affect sequence submission and accession management. Incomplete metadata can make records difficult to interpret, while inaccurate annotations can lead to incorrect biological conclusions. Duplicate submissions may create redundancy, and differences between database versions can complicate comparisons. Large sequencing projects can generate complex relationships among projects, samples, experiments, runs, assemblies, and annotations. Researchers should use the correct identifier type for each data object, verify that the accession resolves to the intended record, and distinguish archival nucleotide accessions from curated reference accessions. They should also recognize that a public accession does not by itself establish sequence quality, biological validity, or clinical significance.
  • For reproducible research, accession numbers should be included in publications and supporting datasets wherever possible. Researchers should record the database, complete accession and version, retrieval date when relevant, reference genome assembly, annotation release, and any transformations applied to the downloaded data. Raw files and processed outputs should be linked to the correct sample and project identifiers. When records are updated, researchers should determine whether the change affects sequence content, genomic coordinates, annotations, or only descriptive metadata. These practices make it easier to reproduce analyses, identify the exact data used, and evaluate whether later database updates affect published results.
  • Sequence submission and accession assignment provide the foundation for reliable sharing and retrieval of biological sequence information. Through repositories such as GenBank, ENA, DDBJ, and specialized sequencing archives, researchers can preserve nucleotide data and make them accessible to the international scientific community. Accession numbers establish traceable links between sequence records and their associated biological information, while versioning and metadata support precise identification and reproducibility. Understanding the submission workflow, validation requirements, identifier types, release policies, and record-update procedures is essential for responsible data management and effective bioinformatics research.
Author:

Leave a Reply

Your email address will not be published. Required fields are marked *