Skip to main content

Public Popular Chemistry Databases and Licensing


Licensing of data, and copyright is a complex thing, and always gets people hot under the collar! Some time ago, following consultation with our funders, we settled on a CC-BY-SA license for ChEMBL - this does a couple of things, but primarily it places an explicit license on the data so it is clear what you can do with it. There is a lot of hot air and active discussion over how 'public' and 'open' particular licenses are, but the CC-BY-SA 3.0 license made sense to us (for reference, this license is also used by the world's premier open resource wikipedia - here is their license)

This license we apply to each release of the database, it makes the data freely available and usable. It requires attribution, so that users of derivative works know where the data comes from, can identify the funders and producers of the work - which we think is fair and appropriate, and finally it applies 'share-alike', so that if you distribute the ChEMBL data further you shouldn't restrict the rights of your users to further give away, use, remix, etc. the data. To be clear though, it does not preclude commercial use of the data.

The Share Alike clause is the thing that people usually get excited by, but this is meant to ensure that if you distribute the data to others you make sure that you also give those you distribute it to the same right to redistribute. If you have a significant problem with this, then don't redistribute any data you get under a SA license; if you find it difficult to keep track of the provenance of data entering your systems, should you really be building stuff to distribute anyway? ;)

Chemistry is a relatively odd world compared to bioinformatics, in that users are generally worried about inadvertent disclosure of their ideas and queries - the basis of the concern is that running a search over the Internet, over an open network, can amount to disclosure and 'publication', and could in theory void a patent through prior art disclosure. As you are probably aware, it is easy to monitor and record traffic over public networks, recovering passwords, etc. Secondly, there is a general suspicion over what happens to recording usage on the servers - do the providers of the web service mine the queries? sell them on? and other sort of paranoid stuff. Well it is not as paranoid as you may think, maybe, since several large internet sites explicitly state in the Terms and Conditions that your query becomes their intellectual property. Sloppy programming, in particular with advertiser sites, can disclose a whole bunch of query data to advertisers.

One of the ways of dealing with the former issue, is to provide access over the https: protocol, this encrypts the traffic between your client browser and the server, and also prevents impersonation of the server by another machine (to most reasonable intents and purposes this is still true). The same secure http: protocol can be applied to make programmatic web services secure too.

There are a number of large 'free'/Open chemical databases at the moment, and we drew up a little table the other day comparing the license and access. It's not complete, probably contains some errors, so if anything is wrong, please let me know. If there are other Open resources to add, put something in the comments, and I'll add it to the table.

Update - thanks to Richard of the RSC, I've corrected some ambiguities in the original table.

ResourceUrl (http: protocol form)LicenseDownloadhttps:
ChEMBLhttp://www.ebi.ac.uk/chemblCC-BY-SAyesyes

BindingDBhttp://www.bindingdb.org/CC-BY-SAyesno

PubChemhttp://pubchem.ncbi.nlm.nih.gov/No clear license statementyesyes

ZINChttp://zinc.docking.org/No redistribution of significant subsets without permissionyesyes, but certificate expired

ChemSpiderhttp://www.chemspider.com/No download, and limited to a total 5,000 data entries stored locally. API access free to academic users, others by agreement.noyes, but broken

Comments

Popular posts from this blog

UniChem 2.0

UniChem new beta interface and web services We are excited to announce that our UniChem beta site will become the default one on the 11th of May. The new system will allow us to better maintain UniChem and to bring new functionality in a more sustainable way. The current interface and web services will still be reachable for a period of time at https://www.ebi.ac.uk/unichem/legacy . In addition to it, the most popular legacy REST endpoints will also remain implemented in the new web services: https://www.ebi.ac.uk/unichem/api/docs#/Legacy Some downtime is expected during the swap.  What's new? UniChem’s current API and web application is implemented with a framework version that’s not maintained and the cost of updating it surpasses the cost of rebuilding it. In order to improve stability, security, and support the implementation and fast delivery of new features, we have decided to revamp our user-facing systems using the latest version of widely used and maintained frameworks, i

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 30 released

  We are pleased to announce the release of ChEMBL 30. This version of the database, prepared on 22/02/2022 contains: 2,786,911 compound records 2,157,379 compounds (of which 2,136,187 have mol files) 19,286,751 activities 1,458,215 assays 14,855 targets 84,092 documents Data can be downloaded from the ChEMBL FTP site: https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_30/ Please see ChEMBL_30 release notes for full details of all changes in this release:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_30/chembl_30_release_notes.txt New Deposited Datasets EUbOPEN Chemogenomic Library (src_id = 55, ChEMBL Document ID CHEMBL4689842):   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 synthesize at least

LSH-based similarity search in MongoDB is faster than postgres cartridge.

TL;DR: In his excellent blog post , Matt Swain described the implementation of compound similarity searches in MongoDB . Unfortunately, Matt's approach had suboptimal ( polynomial ) time complexity with respect to decreasing similarity thresholds, which renders unsuitable for production environments. In this article, we improve on the method by enhancing it with Locality Sensitive Hashing algorithm, which significantly reduces query time and outperforms RDKit PostgreSQL cartridge . myChEMBL 21 - NoSQL edition    Given that NoSQL technologies applied to computational chemistry and cheminformatics are gaining traction and popularity, we decided to include a taster in future myChEMBL releases. Two especially appealing technologies are Neo4j and MongoDB . The former is a graph database and the latter is a BSON document storage. We would like to provide IPython notebook -based tutorials explaining how to use this software to deal with common cheminformatics p

Multi-task neural network on ChEMBL with PyTorch 1.0 and RDKit

  Update: KNIME protocol with the model available thanks to Greg Landrum. Update: New code to train the model and ONNX exported trained models available in github . The use and application of multi-task neural networks is growing rapidly in cheminformatics and drug discovery. Examples can be found in the following publications: - Deep Learning as an Opportunity in VirtualScreening - Massively Multitask Networks for Drug Discovery - Beyond the hype: deep neural networks outperform established methods using a ChEMBL bioactivity benchmark set But what is a multi-task neural network? In short, it's a kind of neural network architecture that can optimise multiple classification/regression problems at the same time while taking advantage of their shared description. This blogpost gives a great overview of their architecture. All networks in references above implement the hard parameter sharing approach. So, having a set of activities relating targets and molecules we can tra