Purpose of BioSample
The BioSample database is descriptive information about the biological source materials, or samples, used to generate experimental data in any of primary data archives.
Following figure depicts how BioSample records are organized and linked with other objects. This example is composed of one umbrella project that encompasses three subprojects, each of which generated data derived from two BioSample records. Users can query either the BioProject or the BioSample database to retrieve the relevant records, and then navigate through links to the corresponding experimental data which continue to be stored in DDBJ’s primary data archives, DDBJ, DRA and GEA.
Given the huge diversity of sample types handled by archival databases, and the fact that appropriate sample descriptions are often dependent on the context of the study, the definition of what a BioSample represents is deliberately flexible. Typical examples of a BioSample include a cell line, a primary tissue biopsy, an individual organism or an environmental isolate.
Biological replicates are represented by separate BioSamples with distinct ‘replicate’ attribute, e.g., ‘biological replicate 1’ and ‘biological replicate 2’. FAQ: How many samples do I need for my DRA submission?
Information about the sample will include:
- The material sampled, e.g., organs, tissues, cell type
- Phenotypic information including disease states and clinical information about the individual
The information about human subjects and access to it will be compliant with all relevant ethical requirements. The DDBJ BioSample database does not support controlled access mechanisms and thus cannot host human clinical samples that may have associated privacy concerns. Submit such human samples to JGA which have access-control mechanism.
In general, create BioSample records for biological source materials and represent extracted molecules, nucleic acids and metabolites, by DRA, GEA and MetaboBank metadata.
- Biological replicates are represented by separate BioSamples with distinct ‘biological_replicate’ attributes. DRA objects organization For example, ‘biological_replicate = 1’ and ‘biological_replicate = 2’.
- Technical replicates are represented by DRA Experiments and GEA SDRF. Use a BioSample for technical replicates.
- RNA and metabolites samples extracted from a plant leaf, create one BioSample and represent extracts by GEA and MetaboBank metadata.
- If a paired-end library from single sample is sequenced, do not create separate sample for forward and reverse reads but register both reads in a DRA Run. DRA objects organization
- If a sample is sequenced by different sequencing instruments, link DRA Experiments with distinct Instrument model to a BioSample.
- Register a separate BioSample for each unique source, e.g., RNA from the wings is a separate BioSample than RNA from legs if those two sources were sequenced independently.
- Genome Assembly Sample requires genome-specific attributes such as locus tag prefix, so it needs to be separated from other RNA and metabolites samples.
- 23,000 unique 16S amplicons from a single seawater collection point - 1 BioSample (1 sample was collected and then analyzed to deduce 16S diversity)
- 3 “identical” transgenic mice treated with the same drug as part of an experiment - 3 BioSamples (biological replicates are represented by separate BioSamples)
- To examine gene expression profiles, CHO cells infected with a virus and sampled at 0, 2, 4, and 8 hours post infection - 4 BioSamples (4 time points)
- To analyze differences in gene expression levels, RNA-seq data from a single male anteater taken from the brain, heart, lungs, testes, and liver - 5 BioSamples (5 different tissues isolated)
A major component of a BioSample record is the sample attributes section. Attributes define the material under investigation and can include sample characteristics such as cell type, collection site and phenotypic information like disease state.
BioSample attributes are captured as structured name: value pairs, for example, tissue:liver
The database supports and encourages use of dictionaries of attribute names by providing packages with pre-defined attributes.
BioSample promotes richer sample description and standardization of attribute name by providing sample packages designed for each type of sample and sequences.
- See “Sample Information” regarding how to select a package.
- See “Sample attributes” regarding sample attributes.
The package itself is a mechanism to promote adequate sample description and attributes are more important for sample interpretation. Therefore, if samples are described by appropriate attributes, you do not change the package even though submitted samples use not-recommended package.
For an organism name of the BioSample organism attribute, see the “Organism name” page. Previously, a strain name or some other lower taxon was required for the organism name of whole genomic sequence, mainly microorganisms. However, currently, the value of organism qualifier should be just a scientific name, in principle, even though for microbial genomes. Please describe a strain name in the strain attribute of BioSample.
Related news: Changes in organism strain information management
Genome assembly sample
A DDBJ genome sequence should be linked to one BioProject and one BioSample. This constraint is set by INSDC to manage genome sequences.
Submit sample(s) used for genome assembly in following packages. When it is not appropriate to use MIxS, use standard packages according to organisms.
- In the case of isolated, cultured prokaryotes: Cultured Bacterial/Archaeal Genomic Sequences (MIGS.ba) or Microbe
- In the case of eukaryotes: Eukaryotic Genomic Sequences (MIGS.eu) or one of the standard packages for organism, Model organism or animal, Invertebrate or Plant
Register a locus tag prefix necessary for an annotated genome submission by entering a prefix in the BioSample locus_tag_prefix attribute.
Genome assembled from multiple samples
When submitting a genome sequence assembled from DNA reads extracted from different samples to DDBJ, we recommend to register a BioSample even though samples are different (an assembled genome needs to be linked to single BioSample).
- genome sequences of different samples were treated as the “same” molecule.
- Apart from a genome sequence, quantitative data such as gene expression are not linked.
- Genome DNAs extracted from a same sample on a different day. You may not describe the extracted dates in BioSample attributes. Instead, you may describe the dates in DRA Experiment or BioSample description.
- Genome DNAs prepared for Illumina and PacBio sequencing. Differentiate at the DRA Experiment level and not at the BioSample level.
When you want to register more than one BioSample, register a derived BioSample because a genome sequence cannot be linked to multiple BioSamples. For example, sequencing reads of male and female samples are submitted to DRA, and submit a genome sequence assembled from both samples, register a derived BioSample citing both BioSample accessions.
Enter the originating BioSample accessions in derived_from attribute of the derived BioSample in the format of “This sample group is the combination of the [number of samples] individual BioSamples: [BioSample accessions]”. For example, “This sample group is the combination of the 2 individual BioSamples: SAMN12623203 and SAMN12623206”
- A Genome sequence JAGDQO010000000 and a derived sample SAMN17974349.
There are four tiers of metagenome assembly (Metagenome-Assembled Genome, MAG) submission depending on the degree of assembly.
Submit a MAG from a particular organism to the ENV division of DDBJ.
Create a virtual BioSample for MAG submission.
Use the MIMAG package and use an organism name without uncultured (e.g., Methanosarcina thermophila).
Indicate deriving source sample as “derived_from: SAMD00000001”. Examples
A MAG also needs to be linked to a BioSample, create a derived BioSample for MAG.
Submission of research data from human subjects
Submit data derived from human subjects (human data) to the databases of Bioinformation and DDBJ Center in compliant with “Submission of Research Data from Human Subjects”.
WARNING: Only use for human samples or cell lines that have no privacy concerns. For all studies involving human subjects, it is the submitter’s responsibility to ensure that the information supplied protects participant privacy in accordance with all applicable laws, regulations and institutional policies. Make sure to remove any direct personal identifiers from your submission. If there are patient privacy concerns regarding making data fully public, please submit samples and data to Japanese Genotype-phenotype Archive (JGA) database. JGA has controlled access mechanisms and is an appropriate resource for hosting sensitive patient data.
Describe following attributes for Human (Homo sapiens) sample by using Human package. Please see this page for attribute explanation.
Sample derived from human subjects
Fill in anonymized subject id in isolate.
Indicate primary cell in sample_type.
sample_type: primary cell
In most cases, iPS cells are used in differentiated state, so information regarding before and after the differentiation are important.
In addition to the above, provide attributes indicated below. It is also applied to ES cells used after differentiation.
Complex samples such as differentiated a few times, provide description in free-text.
Samples from human subjects
Describe information regarding differentiation in cell_type.
For example, cell_type： iPS cell derived megarocyte cell.
Describe information regarding differentiation in cell_type.
For example, cell_type： iPS cell (cell_line:253G1) derived megarocyte cell.
In addition, describe provider information in biomaterial_provider.
For example, biomaterial_provider： ATCC.
An antibiogram table can be included in a BioSample record (Example: SAMN07958491). To submit the table, please contact BioSample team.
For the antibiogram submission guidelines, please see the NCBI BioSample pages.