-
Notifications
You must be signed in to change notification settings - Fork 7
Tableinfo: subject_phenotype.tsv
mano-at-sdsc edited this page Oct 11, 2024
·
4 revisions
Association between a subject and a Human Phenotype Ontology term
For subjects with phenotype metadata, this table will have one row for each phenotype associated with each such subject, along with an association_type
field distinguishing "phenotype present" from "phenotype specifically ruled out."
All fields are required: this table can be empty (header-row only), but any non-header rows must leave no fields blank.
Some examples:
- If you don't have any subjects associated with phenotypes, this table should be left empty.
- If you have exactly one phenotype associated with each subject, this table will have as many rows as subject.tsv.
- If you have five phenotypes associated with each subject, this table will have five times as many rows as subject.tsv.
- If some but not all of your subjects are associated with one or more phenotypes, this table will contain one row for each phenotype assigned to each such subject (and the resulting row count will not have any obvious relationship to the number of rows in subject.tsv, which is both expected and fine in such a case).
Field | Field Description | Required? | Field Value Type | Extra Info |
---|---|---|---|---|
subject_id_namespace | Identifier namespace for this subject [part 1 of 4-component composite primary key] | Required | string | This will be the value of id_namespace in the row in subject.tsv corresponding to the subject referenced in this row. If your program has not registered multiple CFDE identifier namespaces, this will be exactly the same value for all rows. |
subject_local_id | The ID of this subject [part 2 of 4-component composite primary key] | Required | string | This will be the value of local_id in the row in subject.tsv corresponding to the subject referenced in this row. |
association_type | An indicator distinguishing "phenotype present" from "phenotype ruled out" [part 3 of 4-component composite primary key] | Required | one of cfde_phenotype_association_type:0 (meaning "phenotype ruled out") or cfde_phenotype_association_type:1 (meaning "phenotype observed") |
|
phenotype | A valid Human Phenotype Ontology term [part 4 of 4-component composite primary key] | Required | string |
Human Phenotype Ontology lookup Examples: HP:0000349 , HP:0012425
|
-
Tutorials
-
C2M2 Table Guide
-
Table Summary
- analysis_type.tsv
- anatomy.tsv
- assay_type.tsv
- biofluid.tsv
- biosample.tsv
- biosample_disease.tsv
- biosample_from_subject.tsv
- biosample_gene.tsv
- biosample_in_collection.tsv
- biosample_substance.tsv
- collection.tsv
- collection_anatomy.tsv
- collection_biofluid.tsv
- collection_compound.tsv
- collection_defined_by_project.tsv
- collection_disease.tsv
- collection_gene.tsv
- collection_in_collection.tsv
- collection_phenotype.tsv
- collection_protein.tsv
- collection_substance.tsv
- collection_taxonomy.tsv
- compound.tsv
- data_type.tsv
- dcc.tsv (formerly
primary_dcc_contact.tsv
- disease.tsv
- file.tsv
- file_describes_biosample.tsv
- file_describes_collection.tsv
- file_describes_subject.tsv
- file_format.tsv
- file_in_collection.tsv
- gene.tsv
- id_namespace.tsv
- ncbi_taxonomy.tsv
- phenotype.tsv
- phenotype_disease.tsv
- phenotype_gene.tsv
- project.tsv
- project_in_project.tsv
- protein.tsv
- protein_gene.tsv
- subject.tsv
- subject_disease.tsv
- subject_in_collection.tsv
- subject_phenotype.tsv
- subject_race.tsv
- subject_role_taxonomy.tsv
- subject_substance.tsv
- substance.tsv
- Reference Tables
-
Table Summary