Difference between revisions of "WormBase-Caltech Weekly Calls"
From WormBaseWiki
Jump to navigationJump to searchm (→2018 Meetings) |
m (→2018 Meetings) |
||
| Line 31: | Line 31: | ||
* We should encourage authors to include strain IDs | * We should encourage authors to include strain IDs | ||
* Diseases are annotated to genes, alleles, and strains within WB | * Diseases are annotated to genes, alleles, and strains within WB | ||
| + | |||
| + | |||
| + | === Curating phenotypes and diseases to strains or genotypes === | ||
| + | * Should we generate a ?Genotype class to capture genotypes without a known strain name? | ||
| + | * We could create un-named strain objects, that use a new unique identifier as a primary identifier, that represent the entire genotype of a strain used | ||
| + | * When curating phenotypes to strains, we will want to specify what is the relevant/relative genotype that is causative/correlted with the disease or phenotype observation | ||
Revision as of 17:34, 4 January 2018
Contents
Previous Years
2018 Meetings
January 4, 2018
WS264 Upload
- Citace upload to Wen, Tuesday January 16th
- Upload to Hinxton on Jan 19th
Strain data import to AGR for disease
- Will begin to consider pulling in strains into AGR
- Will need to think about how genotypes are built and stored at other MODs
- We should encourage authors to include strain IDs
- Diseases are annotated to genes, alleles, and strains within WB
Curating phenotypes and diseases to strains or genotypes
- Should we generate a ?Genotype class to capture genotypes without a known strain name?
- We could create un-named strain objects, that use a new unique identifier as a primary identifier, that represent the entire genotype of a strain used
- When curating phenotypes to strains, we will want to specify what is the relevant/relative genotype that is causative/correlted with the disease or phenotype observation
