Reference Report
| Reference | |||
|---|---|---|---|
| Citation | Bellen, H. (2005.1.25). spdo/tmod split. (Export to RIS) | ||
| FlyBase ID | FBrf0182569 | ||
| Publication Type | Personal communication to FlyBase | ||
| PubMed ID | |||
| PubMed Abstract | |||
| Text of Personal Communication |
Date: Fri, 21 Jan 2005 09:44:23 \-0600
To: David Sutherland <djs93XXXXXXXXXXXXXXX>, jskeathXXXXXXXXXXXXXXX From: Hugo Bellen <hbellen@XXXXXXXXXXXXXXX> Subject: Re: spdo/tmod split Hi, At 02:26 PM 1/21/2005 \+0000, you wrote: >Dear Hugo and James, >>I'm currently engaged in the tricky task of trying to split FlyBase's current >record for spdo into 2 (tmod/CG1539 & spdo/CG31020), based on the data in >'O'Connor-Giles and Skeath, 2003, Dev. Cell 5(2): 231--243'. >>I'd like to check with you that my proposed partitioning of the alleles fits >with your understanding of their behaviour. Any additional >complementation or >molecular data that could help with this partitioning would be most >welcome. I >can curate such data as a personal communication to FlyBase. >>The tough question is what to do with 'spdoH7'(*) and its associated data. >> On the basis of the mapped insertion 'P{lacW}spdoH7' (now to be renamed >P{lacW}tmod)H7) it needs to be an allele of tmod. On the basis of >failure to >complement spdoC55 (see below), it needs to be an allele of spdo. The most >obvious explanation is that the 'H7' chromosome has mutations in both genes \- >suggesting I should make both alleles. This still leaves the problem of >where >to put the phenotypic data. It most likely hits two or more genes. As far as I can establish, we do not know what the phenotype is of tmod, but Jim can prove me wrong. >Any suggestions? >>Here is how I plan to split the rest of the alleles between the two genes: >>Alleles remaining spdo/CG31020: >>1. leisions mapped by O'Conner-Giles & Skeath: >>spdoC55>spdoG104>spdoK433>>spdoZZ27 (a deficiency removing spdo/CG31020 : data from FBrf0162056 == >O'Connor-Giles and Skeath, 2003, Dev. Cell) > Strictly we only make alleles from Dfs when one of their breakpoints is > in the >gene in question \- Is this the case? spdoZZ27 is a deletion that removes both tmod and spdo, and other genes. It is a null for tmod (no transcript) >2. On the basis of complementation: >>spdoS097002b>Separable from: P{lacW}S097002a >data from: FBrf0099763 Salzberg et al., 1997: >Fails to complement: spdoC55>Southern analysis reveals a chromosomal rearrangement. >Lethality not revertible by Δ2-3-induced mobilization >>Fails to complement: spdoC55>Isolation of spdoH7 by failure to complement spdoC55 is described in >'Dye et al., '98 FBrf0102830'>>Alleles to split out as tmod: >1. constructs: >spdohs.PDL is the only one of these >'rescue' data for 'spdoH7' \- should this now be recorded as partial >suppression of a spdoH7 phenotype by hs-tmod? That is the best explanation as the partial rescue in the PNS was repeated blind. >2. Insertions mapped to CG1539: >>spdo02288>spdo00848>>3. lesions mapped to CG1539 >>spdoS130910>A portion of the CG1539 gene is deleted. (data Dye et al., '98 FBrf0102830) Correct>spdoZZ27 (a deficiency removing tmod/CG1539: data from FBrf0162056 == >O'Connor-Giles and Skeath, 2003, Dev. Cell) > Strictly we only make alleles from Dfs when one of their breakpoints is > in the >gene in question \- Is this the case? Jim may know the precise breakpoint..>>4. On basis of complementation only: >>spdorG347>Fails to complement: spdo00848>(data from BDGP) >>Thanks in advance Sorry for the confusion, but double hits with P-elements, the deletion associated with zz27, and the partial rescue, are at the base of much of the problems. Please confer with Jim, but I think you got most of it... Hugo |
||
| DOI | |||
| Related Publication(s) | |||
Recent Updates
|
|||
| Description |
What does this section display?
This section contains items that were added to this record for each release.
It currently only tracks new links between this FlyBase report and other
FlyBase data classes (e.g. genes, references, stocks) or controlled
vocabulary terms (e.g. GO, anatomy terms).
What does this section not display?
This section does not currently display links that were removed or gene model changes.
|
||
| Update Feed |
Click the icon below to subscribe to this FlyBase record and receive updates automatically through your
feed reader.
|
||
| FB2013_03 | |||
| FB2013_02 | |||
| All updates | Click here to see a list of all updates to this record from FB2010_08 and on. | ||
Associated Information
|
|||
| Comments | |||
| Associated Files | |||
Other Information
|
|||
| Secondary IDs | |||
| Language of Publication | English | ||
| Additional Languages of Abstract | |||
| Also Published As | |||
Parent Publication
|
|||
| Publication Type | |||
| Abbreviation | |||
| Title | |||
| ISBN/ISSN | |||
Data from Reference
|
|||
Aberrations (1)
|
|||
Alleles (11)
|
|||
Genes (2)
|
|||
Recent Updates