Answers.Body: <p>Those IDs are elderly! Ensembl 54 was 2009!</p>
  
  <p>I would recommend using BioMart combined with the <a href="http://www.ensembl.org/Homo_sapiens/Tools/IDMapper" rel="nofollow noreferrer">ID history converter</a>. The ID history converter will convert old IDs to new, and BioMart will convert ENSPs to ENSGs. You can either use the ID history converter with the ENSPs first, then the <a href="http://www.ensembl.org/biomart/martview" rel="nofollow noreferrer">current BioMart</a> to get the ENSGs. Or you can use <a href="http://may2009.archive.ensembl.org/biomart/martview" rel="nofollow noreferrer">Ensembl 54 BioMart</a> to convert the old ENSPs to old ENSGs, then update the ENSGs with the ID history converter. I would probably do both and compare results.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-04T15:59:13.347Z
Answers.Text: Totally agree! They are extremely old but I have to deal with them unfortunately. Thanks a lot for pointing me to the ID history converter, I wasn't aware about this tool. However, I think I didn't ask the question properly. Simplifying, could it be possible that a protein is ENSP00000387261 in v54 and then is ENSP00000387262 in v99? (Note that the example is hypothetical). I am not referring to the ENSPXXX.Y version of a protein but about if the identifier before the point could change between versions.
Answers.UserDisplayName: jxx_fa
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-04T16:14:26.030Z
Answers.Text: Yes, they could have new identifier numbers, which is why you need to combine the ID converter tool with BioMart. Most will stay the same, some will be dead and some will be different.
Answers.UserDisplayName: Emily_Ensembl
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-06T14:01:31.413Z
Answers.Text: Perfect. I am trying with the tool. However, I am having troubles with some proteins. For instance, ENSP00000259791. Apparently it is retired since the release 75, according to its ENSEMBL entry. However, if you introduce it in the ID history converter and look at the table it is still matched to the same ID in the 99 release. If you download the results file, this is not happening anymore. Why this contradiction?. Am I confusing something or is it a bug? Thanks a lot for your help @Emily_Ensembl
Answers.UserDisplayName: jxx_fa
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-06T14:09:08.647Z
Answers.Text: That's weird. The tool should also give you three other IDs for that one, so you can go ahead with them. I will look into it.
Answers.UserDisplayName: Emily_Ensembl
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-06T14:17:13.540Z
Answers.Text: Great. I am trying to parse the table for my 20,000 IDs in R so please let me know if you find what is the issue so I could take it into account systematically. Thanks!
Answers.UserDisplayName: jxx_fa
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-04T14:43:08.397Z
Answers.LastActivityDate: 2020-02-04T15:27:04.863Z
Answers.LastEditDate: 2020-02-04T15:27:04.863Z
Answers.UserDisplayName: Emily_Ensembl
Body: <p>In order to obtain orthologs for human genes, I am working with <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2808972/" rel="nofollow noreferrer">InParanoid version 7.0</a>. This version of the database uses Ensembl Protein Identifiers (<strong>ENSP</strong>) from ENSEMBL version v54, which is based on <strong>NCBI 36</strong> assembly of the human genome.</p>
  
  <p>For my project, I need to have the Ensembl Gene Identifiers (<strong>ENSG</strong>) of these proteins, but in the last version of ENSEMBL, which is based on <strong>GRCh38</strong> assembly. I need to use this version of InParanoid for consistency with previous analyzes.</p>
  
  <p>Thus, my question is, <strong>could I just use biomaRt to map ENSP (from NCBI36) to ENSG (actual version)</strong> or this approach is inherently wrong?</p>
  
  <p>Is it possible to "convert" ENSP identifiers from NCBI36 to GRCh38 and then do the map to ENSG?. I am aware of <a href="https://genome.ucsc.edu/cgi-bin/hgLiftOver" rel="nofollow noreferrer">liftOver</a> but I am not sure it would work here.</p>
  
Tags: <sequence-annotation><ensembl><liftover>
Title: Ensembl protein identifiers from different assemblies
ThreadText: # Ensembl protein identifiers from different assemblies
  
  (Asked by: username_0 on 2020-02-04)
  
  In order to obtain orthologs for human genes, I am working with [InParanoid version 7.0](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2808972/). This version of the database uses Ensembl Protein Identifiers (**ENSP**) from ENSEMBL version v54, which is based on **NCBI 36** assembly of the human genome.
  
  For my project, I need to have the Ensembl Gene Identifiers (**ENSG**) of these proteins, but in the last version of ENSEMBL, which is based on **GRCh38** assembly. I need to use this version of InParanoid for consistency with previous analyzes.
  
  Thus, my question is, **could I just use biomaRt to map ENSP (from NCBI36) to ENSG (actual version)** or this approach is inherently wrong?
  
  Is it possible to "convert" ENSP identifiers from NCBI36 to GRCh38 and then do the map to ENSG?. I am aware of [liftOver](https://genome.ucsc.edu/cgi-bin/hgLiftOver) but I am not sure it would work here.
  
  **Tags:** sequence-annotation, ensembl, liftover
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-02-04. Score: 4
  
  Those IDs are elderly! Ensembl 54 was 2009!
  
  I would recommend using BioMart combined with the [ID history converter](http://www.ensembl.org/Homo_sapiens/Tools/IDMapper). The ID history converter will convert old IDs to new, and BioMart will convert ENSPs to ENSGs. You can either use the ID history converter with the ENSPs first, then the [current BioMart](http://www.ensembl.org/biomart/martview) to get the ENSGs. Or you can use [Ensembl 54 BioMart](http://may2009.archive.ensembl.org/biomart/martview) to convert the old ENSPs to old ENSGs, then update the ENSGs with the ID history converter. I would probably do both and compare results.
  
  > **Comments:**
  > **username_0**: Totally agree! They are extremely old but I have to deal with them unfortunately. Thanks a lot for pointing me to the ID history converter, I wasn't aware about this tool. However, I think I didn't ask the question properly. Simplifying, could it be possible that a protein is ENSP00000387261 in v54 and then is ENSP00000387262 in v99? (Note that the example is hypothetical). I am not referring to the ENSPXXX.Y version of a protein but about if the identifier before the point could change between versions.  
  > **username_1**: Yes, they could have new identifier numbers, which is why you need to combine the ID converter tool with BioMart. Most will stay the same, some will be dead and some will be different.  
  > **username_0**: Perfect. I am trying with the tool. However, I am having troubles with some proteins. For instance, ENSP00000259791. Apparently it is retired since the release 75, according to its ENSEMBL entry. However, if you introduce it in the ID history converter and look at the table it is still matched to the same ID in the 99 release. If you download the results file, this is not happening anymore. Why this contradiction?. Am I confusing something or is it a bug? Thanks a lot for your help @username_1  
  > **username_1**: That's weird. The tool should also give you three other IDs for that one, so you can go ahead with them. I will look into it.  
  > **username_0**: Great. I am trying to parse the table for my 20,000 IDs in R so please let me know if you find what is the issue so I could take it into account systematically. Thanks!  
  
  ---
  
  