Skip to main content

Data checks

 


ChEMBL contains a broad range of binding, functional and ADMET type assays in formats ranging from in vitro single protein assays to anti proliferative cell-based assays. Some variation is expected, even for very similar assays, since these are often performed by different groups and institutes. ChEMBL includes references for all bioactivity values so that full assay details can be reviewed if needed, however there are a number of other data checks that can be used to identify potentially problematic results.

1) Data validity comments:

The data validity column was first included in ChEMBL v15 and flags activities with potential validity issues such as a non-standard unit for type or activities outside of the expected range. Users can review flagged activities and decide how these should be handled. The data validity column can be viewed on the interface (click 'Show/Hide columns' and select 'data validity comments') and can be found in the activities table in the full database.

* Acceptable ranges/units for standard_types are provided in the ACTIVITY_STDS_LOOKUP table. An exception is made for certain fragment-based activities (MW <= 350) where the data validity comment is not applied.

2) Confidence scores:

The confidence scores reflect both the target type and the confidence that the mapped target is correct (e.g. score 0 = no target assigned, score 9 = direct single protein target assigned). In cases where target protein accessions were unavailable during initial mapping, homologues from different species/strains have sometimes been assigned with lower confidence scores. Curation is ongoing and confidence scores may change between releases as additional assays are mapped (or re-mapped) to targets. The confidence scores can be viewed on the interface and are found in the assays table in the database.


3) Activity comments:

Activity comments capture the author or depositor’s overall activity conclusions and may take into account counter screens, curve fitting etc. It may be worth reviewing the activity comments to identify cases where apparently potent compounds have been deemed inactive by depositors. For further details on activity comments, see our previous Blog post. The activity comments can be viewed on the interface and are available in the activities table of the database.

4) Potential duplicates:

Bioactivity data is extracted from seven core journals and this may include secondary citations. Potential duplicates are flagged when identical compound, target, activity, type and unit values are reported. The potential duplicates field is available on the interface and is found in the activities table of the database.

5) Variants:

Protein variation can change the affinity of drugs for targets. On the interface, variant proteins are recorded in the assay descriptions which can be used to check whether activities correspond to variant or 'wild-type' targets. The variant sequences table was added to the database in version 22 and is linked to the assays table through the variant ID. The variant ID can be used to include or exclude variants from assay results. Curation is underway to annotate additional variants from historical assays (more on this to follow).

Hopefully this provides an idea of some of the available data checks. Questions? Please get in touch on the Helpdesk or have a look through our training materials and FAQs.

Data checks using Imatinib as an example:










Comments

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:   https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_29 .  Please see ChEMBL_29 release notes for full details of all changes in this release: https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_29/chembl_29_release_notes.txt 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

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

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

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