chado.stock Tables
Table / View | Referenced | Foreign Keys | Columns | Type | Comments |
---|---|---|---|---|---|
stock | 13 | 3 | 8 | Table | Any stock can be globally identified by the combination of organism, uniquename and stock type. A stock is the physical entities, either living or preserved, held by collections. Stocks belong to a collection; they have IDs, type, organism, description and may have a genotype. |
stock_cvterm | 1 | 3 | 6 | Table | stock_cvterm links a stock to cvterms. This is for secondary cvterms; primary cvterms should use stock.type_id. |
stock_cvtermprop | 0 | 2 | 5 | Table | Extensible properties for stock to cvterm associations. Examples: GO evidence codes; qualifiers; metadata such as the date on which the entry was curated and the source of the association. See the stockprop table for meanings of type_id, value and rank. |
stock_dbxref | 1 | 2 | 4 | Table | stock_dbxref links a stock to dbxrefs. This is for secondary identifiers; primary identifiers should use stock.dbxref_id. |
stock_dbxrefprop | 0 | 2 | 5 | Table | A stock_dbxref can have any number of slot-value property tags attached to it. This is useful for storing properties related to dbxref annotations of stocks, such as evidence codes, and references, and metadata, such as create/modify dates. This is an alternative to hardcoding a list of columns in the relational schema, and is completely extensible. There is a unique constraint, stock_dbxrefprop_c1, for the combination of stock_dbxref_id, rank, and type_id. Multivalued property-value pairs must be differentiated by rank. |
stock_feature | 0 | 3 | 5 | Table | Links a stock to a feature. |
stock_featuremap | 0 | 3 | 4 | Table | Links a featuremap to a stock. |
stock_genotype | 0 | 2 | 3 | Table | Simple table linking a stock to a genotype. Features with genotypes can be linked to stocks thru feature_genotype -> genotype -> stock_genotype -> stock. |
stock_library | 0 | 2 | 3 | Table | Links a stock with a library. |
stock_pub | 0 | 2 | 3 | Table | Provenance. Linking table between stocks and, for example, a stocklist computer file. |
stock_relationship | 2 | 3 | 6 | Table | |
stock_relationship_cvterm | 0 | 3 | 4 | Table | For germplasm maintenance and pedigree data, stock_relationship. type_id will record cvterms such as "is a female parent of", "a parent for mutation", "is a group_id of", "is a source_id of", etc The cvterms for higher categories such as "generative", "derivative" or "maintenance" can be stored in table stock_relationship_cvterm |
stock_relationship_pub | 0 | 2 | 3 | Table | Provenance. Attach optional evidence to a stock_relationship in the form of a publication. |
stockcollection | 3 | 2 | 5 | Table | The lab or stock center distributing the stocks in their collection. |
stockcollection_db | 0 | 2 | 3 | Table | Stock collections may be respresented by an external online database. This table associates a stock collection with a database where its member stocks can be found. Individual stock that are part of this collction should have entries in the stock_dbxref table with the same db_id record |
stockcollection_stock | 0 | 2 | 3 | Table | stockcollection_stock links a stock collection to the stocks which are contained in the collection. |
stockcollectionprop | 0 | 2 | 5 | Table | The table stockcollectionprop contains the value of the stock collection such as website/email URLs; the value of the stock collection order URLs. |
stockprop | 1 | 2 | 5 | Table | A stock can have any number of slot-value property tags attached to it. This is an alternative to hardcoding a list of columns in the relational schema, and is completely extensible. There is a unique constraint, stockprop_c1, for the combination of stock_id, rank, and type_id. Multivalued property-value pairs must be differentiated by rank. |
stockprop_pub | 0 | 2 | 3 | Table | Provenance. Any stockprop assignment can optionally be supported by a publication. |