Skip to main content

Chembl_02 - Press Release

This morning, there was a press release released, marking the official release of chembl_02. More details are in the press release, but for the blog audience, the data is available in the interface, and the databases available for download on the ftp site. Work is already underway on chembl_03, with some associated minor changes to parts of the schema and additional curation of data. There is also something exciting and special in chembl_03, but more of that later.

There is approximately 20% more data in chembl_02 than chembl_01 and new content highlights include a significant expansion of Natural Product records, and unification of all compound identifiers across all EMBL-EBI records (we use ChEBI ids) all chembldb compounds should now seemlessly and quickly make their way into PubChem.

Many, many thanks to those who have told us of the errors and ambiguities you have found. We will incorporate all of these back into the database for the entire community.
For newer readers a pointer, and for older readers with poor memory, a reminder, of the chembl FAQ, and keep an eye open of the chembl-og (or even better the RSS feed) for schema walkthroughs, support and so forth.

Two pieces of staffing news for the group. Firstly, congratulations to Patricia for her success in getting selected for an EIPOD - this is for a joint collaborative project in peptide SAR between the Koehn and Overington groups. Secondly, we welcome our first PhD student - Felix Krueger, who is immersing himself in programming, databases, British life, and data.

Complementary to the required formality of the press release - some thanks! The entire Chembl team would like to take this opportunity to thank our many friends and colleagues who have helped to date, and will do so in the future. In particular, the Wellcome Trust (especially Alan and Rebecca) for their vision and funding (and Janet, Chris, Henning and Bissan for their essential roles in the grant), the senior management of EMBL, especially Iain and Janet, for their wisdom and continuous support. We'd like to acknowledge the assistance our growing network of external curators (Malcolm, Sam, Lora, and Karen), previous interns (good luck Jigisha!), and outsourcing partners (especially Jignesh and the team). Bissan and Mark at the ICR were essential in the early days of the group, and achieved so much while we were recruiting, and they remain an important part of our work and plans. We also thank and recognise the management and staff of Inpharmatica and their investors, for much of the initial development of the databases was done at that time - you know who you are!. Prof. Hopkins, as ever, you are a star ;) Most essential though has been the friendship, focus and shared purpose of our new colleagues at the EMBL-EBI - especially our new friends in the ChEBI team, as well as the INTACT, Systems, Outreach, PANDA, HSF, EBI Industry programme partners, and many other new friends and colleagues, both at Hinxton and Heidelberg. Finally, finally; we have also been doubly blessed with 1) being able to continue working with several long-term collaborators, and 2) finding new important ones since starting at the EMBL-EBI. The future looks bright, so thank you all!


Popular posts from this blog

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

ChEMBL 29 Released

  We are pleased to announce the release of ChEMBL 29. This version of the database, prepared on 01/07/2021 contains: 2,703,543 compound records 2,105,464 compounds (of which 2,084,724 have mol files) 18,635,916 activities 1,383,553 assays 14,554 targets 81,544 documents Data can be downloaded from the ChEMBL FTP site: .  Please see ChEMBL_29 release notes for full details of all changes in this release: New Deposited Datasets EUbOPEN Chemogenomic Library (src_id = 55, ChEMBL Document IDs CHEMBL4649982-CHEMBL4649998): The EUbOPEN consortium is an Innovative Medicines Initiative (IMI) funded project to enable and unlock biology in the open. The aims of the project are to assemble an open access chemogenomic library comprising about 5,000 well annotated compounds covering roughly 1,000 different proteins, to synthesiz

Identifying relevant compounds in patents

  As you may know, patents can be inherently noisy documents which can make it challenging to extract drug discovery information from them, such as the key targets or compounds being claimed. There are many reasons for this, ranging from deliberate obfuscation through to the long and detailed nature of the documents. For example, a typical small molecule patent may contain extensive background information relating to the target biology and disease area, chemical synthesis information, biological assay protocols and pharmacological measurements (which may refer to endogenous substances, existing therapies, reaction intermediates, reagents and reference compounds), in addition to description of the claimed compounds themselves.  The SureChEMBL system extracts this chemical information from patent documents through recognition of chemical names, conversion of images and extraction of attached files, and allows patents to be searched for chemical structures of interest. However, the curren

Julia meets RDKit

Julia is a young programming language that is getting some traction in the scientific community. It is a dynamically typed, memory safe and high performance JIT compiled language that was designed to replace languages such as Matlab, R and Python. We've been keeping an an eye on it for a while but we were missing something... yes, RDKit! Fortunately, Greg very recently added the MinimalLib CFFI interface to the RDKit repertoire. This is nothing else than a C API that makes it very easy to call RDKit from almost any programming language. More information about the MinimalLib is available directly from the source . The existence of this MinimalLib CFFI interface meant that we no longer had an excuse to not give it a go! First, we added a BinaryBuilder recipe for building RDKit's MinimalLib into Julia's Yggdrasil repository (thanks Mosè for reviewing!). The recipe builds and automatically uploads the library to Julia's general package registry. The build currently targe

New Drug Warnings Browser

As mentioned in the announcement post of  ChEMBL 29 , a new Drug Warnings Browser has been created. This is an updated version of the entity browsers in ChEMBL ( Compounds , Targets , Activities , etc). It contains new features that will be tried out with the Drug Warnings and will be applied to the other entities gradually. The new features of the Drug Warnings Browser are described below. More visible buttons to link to other entities This functionality is already available in the old entity browsers, but the button to use it is not easily recognised. In the new version, the buttons are more visible. By using those buttons, users can see the related activities, compounds, drugs, mechanisms of action and drug indications to the drug warnings selected. The page will take users to the corresponding entity browser with the items related to the ones selected, or to all the items in the dataset if the user didn’t select any. Additionally, the process of creating the join query is no