Skip to main content

Should CAS numbers be in ChEMBL and/or UniChem?


A very quick survey to add excitement to either your holiday or work-day! None of these sucker links, where there appears a 0.24% complete progress bar on the second page, it's just a simple yes/no question on whether it's a good idea to add CAS registry numbers to ChEMBL and/or UniChem. No promises that we could deliver this, but depending on what you vote for, we will consider our options.

Update: Given the multiple channels out there, there are also comments on this on LinkedIn (in the ChUG - "ChEMBL User Group" group - why not join, if you're not already) and a couple on Google+.

Update 2: I'll let the poll run till the end of the week (Friday 8th 2014) - and then write something up on the results.

Comments

I would argue against this. The CAS registry number is proprietary and not easy to use. Particularly, you are not allowed to collect them, though they have an informal limit at 10k registry numbers. This causes serious licensing issues with ChEMBL: you will have to make it a separate database and release it separate files. CC-BY-SA does not allow further restrictions such as those imposed for the CAS registry number.
jpo said…
I would disagree with the statement that I'm not allowed to collect them. How can anyone stop me from public sources of course. For example, is there a license carve out on the wikipedia CAS numbers? wikipedia content is CC-BY-SA, so perfect alignment with the current ChEMBL license. There are lots of other sources of large sets of CAS RNs - NCI resolver, ChemSpider, PubChem, UNII). There are also many on public, non-copyrighted documents, patents, INN/USAN documents, etc. To say that i'm not allowed to do anything with them, is just bonkers.

There is a formal limit of 10K, if you sign (or your organisation, with relevant scope of the license).

I'm of mixed view myself as to whether it is worth doing something with ChEMBL - hence to poll - see what the community thinks. For some of the stuff I'm currently working on (clinical candidate disclosures) they are required, and I have never seen a statement to say I can't reuse them in any document I've come across). The whole idea is that they (CAS RNs) are useful to cross reference chemical (and biological) objects with systems that choose to use them.

Sorry for briefish reply, holiday, and just back from the beach with wet trunks!
jpo said…
I would disagree with the statement that I'm not allowed to collect them. How can anyone stop me from public sources of course. For example, is there a license carve out on the wikipedia CAS numbers? wikipedia content is CC-BY-SA, so perfect alignment with the current ChEMBL license. There are lots of other sources of large sets of CAS RNs - NCI resolver, ChemSpider, PubChem, UNII). There are also many on public, non-copyrighted documents, patents, INN/USAN documents, etc. To say that i'm not allowed to do anything with them, is just bonkers.

There is a formal limit of 10K, if you sign (or your organisation, with relevant scope of the license).

I'm of mixed view myself as to whether it is worth doing something with ChEMBL - hence to poll - see what the community thinks. For some of the stuff I'm currently working on (clinical candidate disclosures) they are required, and I have never seen a statement to say I can't reuse them in any document I've come across). The whole idea is that they (CAS RNs) are useful to cross reference chemical (and biological) objects with systems that choose to use them.

Sorry for briefish reply, holiday, and just back from the beach with wet trunks!

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