ChEMBL Resources

Resources:
ChEMBL
|
SureChEMBL
|
ChEMBL-NTD
|
ChEMBL-Malaria
|
The SARfaris: GPCR, Kinase, ADME
|
UniChem
|
DrugEBIlity
|
ECBD

Friday, 2 August 2013

Compound Sets and Availability



Chemical databases come in many different types and flavours, and given that we now have UniChem up and running, and it is being actively used by at least some of you, our minds have turned a little to describing these ‘flavours’ and ‘resolutions’. One of the key things a user is interested in is how easy is it to get hold of a compound, since this is usually a key filter applied to actually doing anything with the results of a database search. The cost implications of needing to commission synthesis, or potentially try and develop new synthetic methodology to a compound are substantial, and there is a substantial literature on the computational assessment of synthetic accessibility (q.v.).

So, here is a simple five state classification that reflects the typical availability of a compounds in a chemical collection.
  1. A compound has been previously been synthesized and is readily available from chemical vendors.
  2. A compound has been previously synthesized but would require resynthesis.
  3. A compound has not been previously synthesized, but close analogues have and the compound is likely to be readily synthesizable. This class of molecule is often associated with the phrase ‘virtual library’.
  4. A compound has not been previously synthesized, and effort would be required to think about synthetic access to the compound.
  5. A compound is theoretically possible with respect to valence rules, but is so unstable that it is unlikely that it ever can be isolated in pure form and then experiments in a biofluid carried out.
Of course, all these classifications are interesting, but you can do a lot more, a lot quicker and cheaper if a compound is in set 1.

As an estimate of the likely difference in cost between these different classes, I personally, would rate the cost differences, relative to set 1, as twenty fold for set 2, forty fold for set 3, and two hundred fold for set 4 - but these are just my estimates, and there will be a big variance in these costs dependent of the exact compound, its class, etc. Others will have better or different estimates of the average cost differences between the sets (comments welcome!).

Because of the way that people have assembled chemical databases, entire primary databases tend to cluster in a similar way - for example ChEMBL is mostly 2), DrugBank is mostly 1) and GDB-17 is mostly 4). Directly from the above definition, every compound with a known bioactivity has to have been synthesized, and so ChEMBL will always be a 2) in this classification. Of course, some compounds in ChEMBL are readily available, but it is a clear minority.

When people build federated chemical databases (those with little unique primary content, but primarily add value by bringing lots of feeder databases together; for example PubChem and ChemSpider) the picture gets a little more complicated at a database level, since they are often blends of synthesized and ‘virtual’ compound sets. But the same need to indicate the availability/provenance of a structure is useful, and federated databases need to store the original primary database (which may or may not itself be available outside of the federated database). 

So, a couple of thoughts:

  • Is this classification useful to apply to the contents of UniChem? 
  • Is the following classification of the UniChem component databases useful and valid?
  1. DrugBank, PDBe, IUPHAR, KEGG, ChEBI, Array_Express, NIH_NCC
  2. ChEMBL, ZINC, eMolecules
  3. IBM, Patents, SureChem (we don’t currently have GDB in UniChem, but if it was it would be in this set.

See UniChem itself for more details of what is behind these set names.

1 comment:

Dave said...

Hi John,
I just want to add a comment of clarification that ChemSpider does not accept virtual compound sets and we do ask where we think that a dataset may be virtual. However, there may be cases where chemical vendors provide a set of files that includes a mixture of synthesised and virtual data and we are not able to identify the virtual data (they often look very similar to combinatorial libraries).

A guiding principle of the ChemSpider database is that it should contain only chemical species that have been made/isolated/analysed/detected - 'real' compounds (for want of a better term).