Skip to main content

ChEMBL Data Deposition Webinar

By

 

 

 The Basics of ChEMBL Data Deposition


Shortly, we are starting work on ChEMBL 37. Thus, we are running a 1 hour data depositor webinar, for anyone who is planning to deposit data to ChEMBL 37.

If you are subscribed to the ChEMBL-depositors mailing list you will have heard about this already. If not, and you have an interest in depositing data to ChEMBL in future, we strongly reccommend you sign up to this depositor mailing list. This will give you updates on the submission process and deadlines.
 

Webinar Info

We are running on Friday 3 Oct, at 10:00 am, on Zoom.
We will post the meeting link to the ChEMBL-depositors mailing list the day before. 

Learning Objectives of the Webinar

This webinar is designed to:
  • Familiarise new depositors with the basic requirements for ChEMBL input data.
  • Re-familiarise former depositors with the deposition process, and explain any new requirements.  
 


A Reminder About ChEMBL 37 deadlines 

For ChEMBL 37, the deadline for an expression of interest has passed.
The deadline for submission of a complete dataset is end of day on October 31, 2025. 

If you are planning to deposit data for ChEMBL 37, but nobody from your team can make the webinar, don't worry - we will have a recording available for anyone interested and will distribute it via the depositor mailing list afterwards! 

Please also get in touch with us at chembl-deposition@ebi.ac.uk, to arrange a quick call to discuss your data, if you have not deposited to ChEMBL before or simply want to discuss your data set ready for submission.

Data Requirements Changes

We have made some schema and data requirement changes during the release of ChEMBL 36. 
We will cover the full requirements during the deposition, but the more notable changes are listed below.

REFERENCE files 

  • These need to have a DATA_LICENCE field, which declares the license for data sharing. This should preferably be CC0 to avoid complications with usage of ChEMBL data.
  • We strongly recommend you to include a CONTACT field, which should include a stable identifier (ideally ORCID) for one to three primary contact person(s) for this data set; this could be the individual carrying out the experiment, the head of a laboratory or a line manager.

ACTIVITY 

  • ACTION_TYPE should only be populated when a compound has confirmed activity. Otherwise, this field should be left as null.
  • We have more clearly defined rules for what goes into the VALUE and TEXT_VALUE fields and what distinguishes them. See this new page.

Comments

Post a Comment