Skip to main content

Where should you/can you publish your ChEMBL research?

Well, we've got to about 125 citations(1) for the main ChEMBL database paper so far, which for a year is a pretty good haul we think. Given this reasonably big number, we thought it would be appropriate to analyse where the use of ChEMBL makes it's way into the published literature - or what is our 'research user community'(2). A simple way to analyse this is to look at papers that cite ChEMBL, grouped by journal. The graph is below - it's a classic log-normal/power law style frequency-class distribution.

So J Chemical Information & Modelling (JCIM) is about 20% of all citations, and could indicate that the biggest early impact of ChEMBL is in the development of novel methods for compound design - which was one of our hopes for what our work and the ChEMBL data could achieve - better, safer drugs, quicker! Then there's the database community in Nucleic Acids Research (this is quite an unusual journal for comp chemists and modellers, but it is the de facto (and highest profile) place to publish "resource" papers in the life sciences, and it's a completely Open journal (3)) - so the data is being used and integrated elsewhere; then J Med Chem - the premier medicinal chemistry journal, and so on. It is also notable that ChEMBL has contributed centrally to two Nature full Articles this year (covered in earlier posts) - and given how infrequently chemistry makes the pages of the might Nature and Science this is great news for us, and probably good for the entire community with respect to profile and awareness of the field!!

It's interesting to see the strong trend to JCIM - this probably means that they have a receptive set of reviewers and know how to route stuff to the right people (of course if they then reject 95% of all ChEMBL citing papers that's not such good news).

So what next - it got us thinking about how we would expect ChEMBL to impact the field/literature long term - it's really really unlikely that papers that use methods and further integrated data and discover drugs will ever cite the ChEMBL NAR paper. But we will try and track the ripples that ChEMBL makes over time......

A few notes.
1) Citation data is from Google Scholar. But c'mon google - give us an API.
2) We know that many people who use ChEMBL are not really interested in publishing, that they are not free to publish their work, or that they don't have the time to publish, alongside all the other junk they have to deal with.
3) Open, Closed, Gold, Green, Good, Evil, Cow, Horse..... The ChEMBL NAR paper itself (the one that has the 125 citations analysed above) is Open Access, and the entire ChEMBL database team is solely funded by The Wellcome Trust (including my position), so we are under the obligations of their requirements for Open Access publishing. We cannot of course influence where researchers publish use of ChEMBL (and there are many publications that use the ChEMBL data that do not cite our papers :( ), but they will be under their own funders requirements - and remember that not all research is tax-payer (or similar) funded, so not all funders are as motivated to worry about Open Access, especially if it is yet an additional cost. So unfortunately, not all the papers that use ChEMBL are Open Access. But if you can, publish all your research and reviews Open Access - go on, it will make you smile and dogs in the street will like you!

Update - I've (jpo) done a bit of editing on this post overnight - I rushed it yesterday to catch a train, and thought that some additional context and comment was required.

jpo and francis

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

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