chembl_webservices_2
chembl_webservices_2 copied to clipboard
Target <-> Protein Class many2many relation is implemented in a wrong way
While working on the interactive web services diagram I spot this problem. The link between Target
and Target Component
is on the Target
side:
So
Target
contains a list of Target Components
data. Now, while there is nothing wrong in having this list as this might be helpful for people exploring this endpoint, this is wrong from the many 2 many relationship point of view. The link should be on the Target Components
side so each Target Component
should have a target_chembl_id
field, the same way many2many relation is implemented between Molecule
and Target
(via Mechanism
):
Another problem is that protein_classification_id
field is nested inside the Target Component
endpoint, giving a false impression that there can be more than one Protein Classification
object for a given Target Component
. This should be flattened.