Ensembl ID converter not working?
1
0
Entering edit mode
6.6 years ago

Hi, I have some outdated Ensembl Gene IDs. I tried using Ensembl's ID converter tool to get the new versions of the IDs but it just spits back the same ID to me that wasn't working in the first place. For example, with "ENSGALG00000015646", the tool says that the ID is still in the current release, Release 90 (see below). But if I type the ID into the search bar on the website, it gives 0 results. Any idea what's going on?

90: ENSGALG00000015646.3

53: ENSGALG00000015646.3

51: ENSGALG00000015646.3

45: ENSGALG00000015646.3

42: ENSGALG00000015646.3

36: ENSGALG00000015646.2

ensembl ID conversion • 2.3k views
ADD COMMENT
1
Entering edit mode

Hi,

This is strange behaviour- and I think you may have found a bug in the ID history convertor. I think the problem arises from where we updated form the Galgal4 assembly to the Gallus_gallus-5.0 assembly.

For example, searching in the Ensembl archives (in a version that used the Galgal4 assembly) provides an entry for your stable ID: http://dec2015.archive.ensembl.org/Gallus_gallus/Gene/Summary?db=core;g=ENSGALG00000015646;r=2:117721181-117734940;t=ENSGALT00000025230

You can then use the gene name (TCEB1) to find the gene in the current version of Ensembl: http://www.ensembl.org/Gallus_gallus/Gene/Summary?db=core;g=ENSGALG00000035417;r=2:118445078-118458839;t=ENSGALT00000065415

Obviously, this is a long-way round to get the result you are looking for with the ID history convertor, so we are looking into fixing this issue as quickly as possible. I will keep you updated with the progress of our work.

Best wishes

Ben Ensembl Helpdesk

ADD REPLY
0
Entering edit mode

This gene is indeed not in e90 but present in older versions. What ID conversion tool are you using ?

ADD REPLY
0
Entering edit mode

The ID History Converter tool on Ensembl's webite: http://www.ensembl.org/Homo_sapiens/Tools/IDMapper?db=core Do you have a different one you'd recommend?

ADD REPLY
1
Entering edit mode

I did not check myself, but Jean-Karim is confirming .... so maybe tell them that their converter is not working, there might be a bug!

ADD REPLY
0
Entering edit mode

This looks like a bug to me. You should report to the helpdesk.

ADD REPLY
4
Entering edit mode
6.6 years ago
Ben_Ensembl ★ 2.4k

Having looked into this problem- it's caused by the way that retired Ensembl stale IDs are labelled in our database. This means that the ID history convertor does not recognise retired stable IDs and simply lists the retired stable ID for the current Ensembl release.

This is only a problem where an old stable ID is not linked to a new stable ID. Where an old stable ID is linked to a stable ID in the current version of Ensembl, the ID history convertor will be able to provide an accurate history.

With ENSGALG00000015646, you have found an example where the ID is retired and not mapped to a gene in the current version of Ensembl. This happens in the instances where the mapping pipeline does not detect a sufficiently similar gene.

To fix this, we will change the way stable IDs are retired in our database, so that the results the ID history convertor provides for retired stable IDs is not ambiguous. However, we are unable to change the pipeline that maps the stable IDs, and so from Ensembl 91 onwards you will see ENSGALG00000015646 simply listed as 'retired'.

I hope this helps clarify the data you retrieved form the ID history convertor, but please do get back in touch if anything is still unclear.

Best wishes

Ben Ensembl Helpdesk

ADD COMMENT
0
Entering edit mode

Thanks for the info! :)

ADD REPLY

Login before adding your answer.

Traffic: 2592 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6