Subject: 	Re: GSDB-Message FlyBase query: GS2163A, GS2163B, GS2048A, GS2048B
> My specific questions:
> 1. Can you confirm that the 'official name' for GS2163A is now GS2163?
Yes,
GS2163 used to have two insertions, A and B, but our recent re- 
mapping data showed only one insertion which correspond to A.
> 2. Likewsie, can you confirm that the 'official name' for GS2048A  
> is now
> GS2048?
Yes,
Same as above
> 3. What has happened to GS2163B - has it been renamed or did the  
> mapping
> prove incorrect?
We determined the sequences of GAL4-dependent misexpressed  
transcripts, rather than the genome sequence, which was not available  
at that time.
Our recent re-mapping was done based on the vector-flanking genome  
sequence as usual. We do not know why only one insertions came up  
with this method. We haven't confirmed whether you still find a  
misexpressed transcripts derived from GS2163B.
> 4. Likewise, what has happened to GS2048B - has it been renamed or did
> the mapping prove incorrect?
Same situation as above.
Thank you curating the data.
Toshiro
On 2007/05/11, at  23:16 , Steven Marygold wrote:
> Dear GSDB,
>
>
> FlyBase is currently reviewing its curation of P{GS} insertions,
> basically replacing the P{GS} symbol (that we used originally) with  
> the
> more informative P{GSV$} symbol (where $ = 1, 2, 3, 6, 7 as
> appropriate).
>
> In reviewing Table 2 of the Toba et al. 1999 Genetics paper, I have  
> come
> across 4 GS lines that appear to have been changed/removed in the
> current GSDB website, namely:
> GS2163A - inserted near LD04971 (= Ent2) in Toba et al.; now called
> GS2163 in GSDB
> GS2163B - inserted near guf (= Oda) in Toba et al.; now not found in
> GSDB
> GS2048A - inserted near LD03829 (= homer) in Toba et al.; now  
> called in
> GS2048 in GSDB
> GS2048B - inserted near LD07122 (= CG9418 ) in Toba et al.; now not
> found in GSDB
>
> My specific questions:
> 1. Can you confirm that the 'official name' for GS2163A is now GS2163?
> 2. Likewsie, can you confirm that the 'official name' for GS2048A  
> is now
> GS2048?
> 3. What has happened to GS2163B - has it been renamed or did the  
> mapping
> prove incorrect?
> 4. Likewise, what has happened to GS2048B - has it been renamed or did
> the mapping prove incorrect?
>
>
> Thanks for your help.
>
> Steven (for FlyBase)