-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Examples of non-ideal merging of records #162
Comments
I had a quick look at this particular case, in most of these drugcentral documents, 4097 out of 5399, drugcentral does include a field for
In this case, the merging step will be based on the |
The merging of multiple records in source databases into a single record in mychem.info is a challenging process, and one where I doubt we'll ever get it perfectly "right". Having said that, I noticed an example where the current merging is not ideal, and so I'm creating this issue to document this example and others like it.
This is the API call that illustrates this example: https://mychem.info/v1/chem/GVJHHUAWPYXKBD-IEOSBIPESA-N?fields=chembl.molecule_chembl_id,chembl.max_phase,chembl.pref_name,drugcentral.xrefs.chembl_id
mychem only maps this record to a single ChEMBL ID -- CHEMBL47, but DrugCentral maps to two additional IDs: CHEMBL3989727 and CHEMBL2108106. All of these IDs are some variant of Vitamin E. One reason this is confusing because
CHEMBL47
reports"max_phase": 0
, whereas the other two are"max_phase": 4
(what one would expect for Vitamin E).The text was updated successfully, but these errors were encountered: