Skip to main content

Mapping lists of IDs in ChEMBL



In order to facilitate the mapping of identifiers in ChEMBL, we have developed a new type of search in the ChEMBL Interface. Now, it is possible to enter a list of ChEMBL IDs and see a list of the corresponding entities. Here is an example:

1. Open the ChEMBL Interface, on the main search bar, click on 'Advanced Search':


2. Click on the 'Search by IDs' tab:



3. Select the source entity of the IDs and the destination entity that you want to map to:

4. Enter the identifiers, you can either paste them, or select a file to upload. When you paste IDs, by default it tries to detect the separator. You can also select from a list of separators to force a specific one:

Alternatively, you can upload a file, the file can be compressed in GZIP and ZIP formats, this makes the transfer of the file to the ChEMBL servers faster. Examples of the files that can be uploaded to the search by IDs can be found here.

5. Click on the search button:

6. You will be redirected to a search results page, you can see the status of the process while the ids are being mapped:
]

7. When the process is finished, the 'Summary' tab will be enabled, you can see details such as how many terms where recognised, how many matched in ChEMBL and how many IDs were found to be downgraded, among other details:

8. Below the description of the steps, you will see the results of your search:


Currently, users can do the following mappings:
  • From Molecule ChEMBL IDs to ChEMBL Molecules.
  • From Target ChEMBL IDs to ChEMBL Targets.
However, we plan to implement more kinds of mappings, such as:
  • From Assay ChEMBL IDs to ChEMBL Assays.
  • From Document ChEMBL IDs to ChEMBL Document.
  • From Cell Line ChEMBL IDs to ChEMBL Cell Lines.
  • From Molecule ChEMBL IDs to ChEMBL Drugs.
  • From Tissue ChEMBL IDs to ChEMBL Tissues.
  • From UniProt IDs to ChEMBL Compounds.
  • From Smiles to ChEMBL Compounds.
Currently, you can enter up to 200k IDs. We are working on improving this restriction.
Remember that if you have any questions, you can contact us at chembl-help@ebi.ac.uk.

Comments

Popular posts from this blog

ChEMBL & SureChEMBL anniversary symposium

  In 2024 we celebrate the 15th anniversary of the first public release of the ChEMBL database as well as the 10th anniversary of SureChEMBL. To recognise this important landmark we are organising a two-day symposium to celebrate the work achieved by ChEMBL and SureChEMBL, and look forward to its future.   Save the date for the ChEMBL 15 Year Symposium October 1-2, 2024     Day one will consist of four workshops, a basic ChEMBL drug design workshop; an advanced ChEMBL workshop (EUbOPEN community workshop); a ChEMBL data deposition workshop; and a SureChEMBL workshop. Day two will consist of a series of talks from invited speakers, a few poster flash talks, a local nature walk, as well as celebratory cake. During the breaks, the poster session will be a great opportunity to catch up with other users and collaborators of the ChEMBL resources and chat to colleagues, co-workers and others to find out more about how the database is being used. Lunch and refreshments will be pro

ChEMBL 34 is out!

We are delighted to announce the release of ChEMBL 34, which includes a full update to drug and clinical candidate drug data. This version of the database, prepared on 28/03/2024 contains:         2,431,025 compounds (of which 2,409,270 have mol files)         3,106,257 compound records (non-unique compounds)         20,772,701 activities         1,644,390 assays         15,598 targets         89,892 documents Data can be downloaded from the ChEMBL FTP site:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_34/ Please see ChEMBL_34 release notes for full details of all changes in this release:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_34/chembl_34_release_notes.txt New Data Sources European Medicines Agency (src_id = 66): European Medicines Agency's data correspond to EMA drugs prior to 20 January 2023 (excluding vaccines). 71 out of the 882 newly added EMA drugs are only authorised by EMA, rather than from other regulatory bodies e.g.

A python client for accessing ChEMBL web services

Motivation The CheMBL Web Services provide simple reliable programmatic access to the data stored in ChEMBL database. RESTful API approaches are quite easy to master in most languages but still require writing a few lines of code. Additionally, it can be a challenging task to write a nontrivial application using REST without any examples. These factors were the motivation for us to write a small client library for accessing web services from Python. Why Python? We choose this language because Python has become extremely popular (and still growing in use) in scientific applications; there are several Open Source chemical toolkits available in this language, and so the wealth of ChEMBL resources and functionality of those toolkits can be easily combined. Moreover, Python is a very web-friendly language and we wanted to show how easy complex resource acquisition can be expressed in Python. Reinventing the wheel? There are already some libraries providing access to ChEMBL d

Accessing SureChEMBL data in bulk

It is the peak of the summer (at least in this hemisphere) and many of our readers/users will be on holiday, perhaps on an island enjoying the sea. Luckily, for the rest of us there is still the 'sea' of SureChEMBL data that awaits to be enjoyed and explored for hidden 'treasures' (let me know if I pushed this analogy too far). See here and  here for a reminder of SureChEMBL is and what it does.  This wealth of (big) data can be accessed via the SureChEMBL interface , where users can submit quite sophisticated and granular queries by combining: i) Lucene fields against full-text and bibliographic metadata and ii) advanced structure query features against the annotated compound corpus. Examples of such queries will be the topic of a future post. Once the search results are back, users can browse through and export the chemistry from the patent(s) of interest. In addition to this functionality, we've been receiving user requests for  local (behind the