Closed pcm32 closed 8 months ago
Hi Pablo,
Thank you for your feedback, this has been fixed, along with the way it gets the reference from the ChEMBL data, you can see it here:
https://www.ebi.ac.uk/chembl/target_report_card/CHEMBL3774298/
Thanks!
On 11 May 2022, at 09:51, David Mendez @.***> wrote:
Hi Pablo,
Thank you for your feedback, this has been fixed, along with the way it gets the reference from the ChEMBL data, you can see it here:
https://www.ebi.ac.uk/chembl/target_report_card/CHEMBL3774298/ https://www.ebi.ac.uk/chembl/target_report_card/CHEMBL3774298/ — Reply to this email directly, view it on GitHub https://github.com/chembl/GLaDOS/issues/1301#issuecomment-1123382431, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACZ6XQBSSW6NQVAAJQ5DADVJNYHXANCNFSM5VOVHFDA. You are receiving this because you authored the thread.
@nclopezo
Although the cross reference Iink works fine and the resource name is correct, I noticed that we now use the UniProt accession in the gene cross references rather than the ENSEMBL_ID. We previously used the ENSEMBL_ID. Is this correct?
Those references don't seem to have any further processing, they are shown as they come from elasticsearch:
Is this what you are asking about?
Thanks. The above screenshot shows an Ensembl_ID but I agree that the XREFs haven't changed in the database and are working.
Hi there,
On your cross references, you are linking to the expression of genes at our resource (Expression Atlas), which we really appreciate! But currently it says there "ArrayExpress" in the label of the link, where it should read "Expression Atlas" instead:
Could you please amend this? The link works fine, it is just the name of the resource.
Thanks!