Skip to main content

Direct submissions of data to ChEMBL and the Open PHACTS project



Don’t we just love the fact that these days so much bioactivity data is freely available at no cost (to the end user)? I think we do. The more, the better. So, what would your answer be if someone asked you if you consider it to be a good idea if they would deposit some of their unpublished bioactivity data in ChEMBL? My guess is that you would be all in favour of this idea. 'Go for it', you might even say. On the other hand, if the same person would ask you what you think of the idea to deposit some of ‘your bioactivity data’ in ChEMBL the situation might be completely different.  

First and foremost you might respond that there is no such bioactivity data that you could share. Well let’s see about that later. What other barriers are there? If we cut to the chase then there is one consideration that (at least in my experience) comes up regularly and this is the question:  'What’s in it for me?' Did you ask yourself the same question? If you did and you were thinking about ‘instant gratification’ I haven’t got a lot to offer. Sorry, to disappoint you. However, since when is science about ‘instant gratification’? If we would all start to share the bioactivity data that we can share (and yes, there is data that we can share but don’t) instead of keeping it locked up in our databases or spreadsheets this would make a huge difference to all of us. So far the main and almost exclusive way of sharing bioactivity data is through publications but this is (at least in my view) far too limited. In order to start to change this (at least a little bit) the concept of ChEMBL supplementary bioactivity data has been introduced (as part of the efforts of the Open PHACTS project, http://www.openphacts.org).

Here is how it works: If you have unpublished bioactivity data that has been generated in an assay that can be found in ChEMBL (since the publication where the assay is described is also in ChEMBL), you can now deposit this data in ChEMBL (see http://dx.doi.org/10.6019/CHEMBL2094195 for an example). The obvious situation would be one where only a subset of the results have been reported in the publication but there are many more results (e.g. inactives). If you work in an industrial setting and might feel that you are not be in a position to release additional chemical structures you could think about depositing bioactivity data for compounds in (older) patents. Or you have reported bioactivity data in a poster. These are only examples and there are many more opportunities. In some cases we might explore new territory and the progress might be slow, but if we don’t try new things we are stuck with what we have. 'Do we really want this?' I hope the answer is no. So, let’s not focus on ‘instant gratification’ but help to grow the body of freely available bioactivity data by contributing to ChEMBL supplementary bioactivity data. If we could just give it a go it might make a difference. The concept might be quite restricted (e.g. the assay needs to be published) but we need to start somewhere. If you want to find out more about ChEMBL supplementary bioactivity data why not drop ChEMBL Help a line (chembl-help@ebi.ac.uk) and put ‘ChEMBL supplementary bioactivity data’ in the subject field. And don’t worry, you are not committing yourself by wanting to know more. 

ChEMBL, and the whole world of drug discoverers, is looking forward to hearing from you.  

Stefan Senger

Comments

Popular posts from this blog

New SureChEMBL announcement

(Generated with DALL-E 3 ∙ 30 October 2023 at 1:48 pm) We have some very exciting news to report: the new SureChEMBL is now available! Hooray! What is SureChEMBL, you may ask. Good question! In our portfolio of chemical biology services, alongside our established database of bioactivity data for drug-like molecules ChEMBL , our dictionary of annotated small molecule entities ChEBI , and our compound cross-referencing system UniChem , we also deliver a database of annotated patents! Almost 10 years ago , EMBL-EBI acquired the SureChem system of chemically annotated patents and made this freely accessible in the public domain as SureChEMBL. Since then, our team has continued to maintain and deliver SureChEMBL. However, this has become increasingly challenging due to the complexities of the underlying codebase. We were awarded a Wellcome Trust grant in 2021 to completely overhaul SureChEMBL, with a new UI, backend infrastructure, and new f

Legacy SureChEMBL retirement

Dear SureChEMBL users, About six months ago, we introduced the new version of SureChEMBL . It brought significant improvements in terms of performance and stability, and it also allows us to implement new functionalities. After the survey at the beginning of the year, we prioritised what should be delivered first. You should see the materialisation of our work in the coming months. As originally announced when the new SureChEMBL was introduced, the plan was to shut down the old system permanently to focus all our resources on the new SureChEMBL. This time has come, so expect www.surechembl-legacy.org to be unreachable in the coming days with no turning back! Consequently, and in parallel, the new SureChEMBL will lose its Beta status, and we will stop referring to it as the new version. This does not mean we are reducing our efforts to improve our system; on the contrary, this removes a distraction! If you have any feedback, you can contact us directly at surechembl-help@ebi.ac.uk . W

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