Skip to main content

The AIDX






ChEMBL has recently begun to display the ‘AIDX’ field as part of our assay data. In this Blog post you can find out more about the AIDX as well as how to best populate this field when depositing data to ChEMBL.


What is the AIDX?


ChEMBL extracts bioactivity data from the core medicinal literature but also accepts deposited data from the scientific community. In fact, deposited data now provides more than half of the bioactivity data within ChEMBL. During the preparation of data for submission to ChEMBL, depositors format and assign identifiers to their data to allow integration into ChEMBL and the AIDX is the depositor-defined identifier for assays. Each AIDX corresponds to a distinct assay with a defined experimental set-up (aim, target and method). Concise and meaningful AIDXs are ideal since these are not easily replicated by different depositors.


 


Suggested AIDX format: Smith_KinaseXYZ_Assay36 (abbreviation of the group leader, target, assay number).


Poor AIDX format: ‘1’, ‘2’, ‘3’


Reuse of AIDXs - depositing additional bioactivity data to an existing assay


Depositors occasionally submit additional bioactivity data for assays that already exist within ChEMBL. For example when a single institute is performing the same set of assays for newly synthesised compounds, or a contract research organisation is characterising compounds using a defined set of assays. Here, depositors can reuse an existing AIDX for new bioactivity data, but the AIDX must match the previous identifier exactly and the assay set up should be identical. Depositors are responsible for ensuring that the assay set up is consistent between datasets and that a standard protocol and appropriate positive and negative controls are included to ensure variation is within expected limits.


Can I reuse an existing depositor AIDX if my assay uses the same commercial screening kit?


Commercial kits may have a standard assay set up but we consider assays run by different institutions, using the same commercial kit, as distinct. The depositor AIDXs for these screening assays should be distinct if performed at different institutes. However, to allow comparison between similar assays, kit identifiers/catalogue numbers should ideally be included within the assay description.


e.g. Inhibition of XYZ target at 10uM tested using the Eurofins SafetyScreen44 (BI) (P270) - P270 is the catalogue number.


Summary


Overall, the AIDX is an identifier that depositors use when submitting experimental data to ChEMBL. Occasionally, this identifier can be re-used for data from a single institute or from CROs. Assays from different institutes are considered distinct but we suggest that users include a catalogue number for commercial kits to facilitate comparisons across similar assays.


Questions? Get in touch in the Helpdesk with any further questions or browse our assays.


Comments

Popular posts from this blog

SureChEMBL Available Now

Followers of the ChEMBL group's activities and this blog will be aware of our involvement in the migration of the previously commercially available SureChem chemistry patent system, to a new, free-for-all system, known as SureChEMBL. Today we are very pleased to announce that the migration process is complete and the SureChEMBL website is now online. SureChEMBL provides the research community with the ability to search the patent literature using Lucene-based keyword queries and, much more importantly, chemistry-based queries. If you are not familiar with SureChEMBL, we recommend you review the content of these earlier blogposts here and here . SureChEMBL is a live system, which is continuously extracting chemical entities from the patent literature. The time it takes for a new chemical in the patent literature to become searchable in the SureChEMBL system is 1-2 days (WO patents can sometimes take a bit longer due to an additional reprocessing step). At time of writi

New SureChEMBL announcement

(Generated with DALL-E 3 ∙ 30 October 2023 at 1:48 pm) We have some very exciting news to report: the new SureChEMBL is now available! Hooray! What is SureChEMBL, you may ask. Good question! In our portfolio of chemical biology services, alongside our established database of bioactivity data for drug-like molecules ChEMBL , our dictionary of annotated small molecule entities ChEBI , and our compound cross-referencing system UniChem , we also deliver a database of annotated patents! Almost 10 years ago , EMBL-EBI acquired the SureChem system of chemically annotated patents and made this freely accessible in the public domain as SureChEMBL. Since then, our team has continued to maintain and deliver SureChEMBL. However, this has become increasingly challenging due to the complexities of the underlying codebase. We were awarded a Wellcome Trust grant in 2021 to completely overhaul SureChEMBL, with a new UI, backend infrastructure, and new f

ChEMBL & SureChEMBL anniversary symposium

  In 2024 we celebrate the 15th anniversary of the first public release of the ChEMBL database as well as the 10th anniversary of SureChEMBL. To recognise this important landmark we are organising a two-day symposium to celebrate the work achieved by ChEMBL and SureChEMBL, and look forward to its future.   Save the date for the ChEMBL 15 Year Symposium October 1-2, 2024     Day one will consist of four workshops, a basic ChEMBL drug design workshop; an advanced ChEMBL workshop (EUbOPEN community workshop); a ChEMBL data deposition workshop; and a SureChEMBL workshop. Day two will consist of a series of talks from invited speakers, a few poster flash talks, a local nature walk, as well as celebratory cake. During the breaks, the poster session will be a great opportunity to catch up with other users and collaborators of the ChEMBL resources and chat to colleagues, co-workers and others to find out more about how the database is being used. Lunch and refreshments will be pro

ChEMBL 34 is out!

We are delighted to announce the release of ChEMBL 34, which includes a full update to drug and clinical candidate drug data. This version of the database, prepared on 28/03/2024 contains:         2,431,025 compounds (of which 2,409,270 have mol files)         3,106,257 compound records (non-unique compounds)         20,772,701 activities         1,644,390 assays         15,598 targets         89,892 documents Data can be downloaded from the ChEMBL FTP site:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_34/ Please see ChEMBL_34 release notes for full details of all changes in this release:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_34/chembl_34_release_notes.txt New Data Sources European Medicines Agency (src_id = 66): European Medicines Agency's data correspond to EMA drugs prior to 20 January 2023 (excluding vaccines). 71 out of the 882 newly added EMA drugs are only authorised by EMA, rather than from other regulatory bodies e.g.

RDKit, C++ and Jupyter Notebook

Fancy playing with RDKit C++ API without needing to set up a C++ project and compile it? But wait... isn't C++ a compiled programming language? How this can be even possible? Thanks to Cling (CERN's C++ interpreter) and xeus-cling jupyter kernel is possible to use C++ as an intepreted language inside a jupyter notebook! We prepared a simple notebook showing few examples of RDKit functionalities and a docker image in case you want to run it. With the single requirement of docker being installed in your computer you'll be able to easily run the examples following the three steps below: docker pull eloyfelix/rdkit_jupyter_cling docker run -d -p 9999:9999 eloyfelix/rdkit_jupyter_cling open  http://localhost:9999/notebooks/rdkit_cling.ipynb  in a browser