Erica Wood

In its current state, is it worth keeping the TTD information in KG2? Since the identifiers are incorrect, is it helpful?

@saramsey If you look at the TTD identifiers currently in `KG2.6.0`, you'll notice that the identifiers are just the names of the nodes. The TTD nodes are created in `dgidb_tsv_to_kg_json.py`:...

> Thank you @ericawood, that helps. OK, so my previous comment was based on a misunderstanding on my part. It sounds like the DGIdb ETL process is only creating TTD...

> @ericawood The identifiers you listed above, while they may have the CURIE prefix "ttd.target", look to be drugs to me. I'm pretty sure they are not drug targets in...

Will other sources link to TTD properly with the identifiers in this form?

I contacted the identifiers.org help desk a while back about their TTD identifiers not resolving. This was their response: > Dear Erica Wood, > > thank you for pointing out...

In KG2.8.3, running ``` match (n) where n.id contains " " return distinct n.provided_by, count(*) ``` returns no results, but the TTD identifiers are still do not resolve: ``` match...

From KG2.6.7: ``` match (n) where (split(n.provided_by, ':')[0]='umls_source'or n.provided_by="identifiers_org_registry:umls") and not (n.description contains "UMLS_STY") return count(n) ``` count(n) --| 186647 ``` match (n) where (split(n.provided_by, ':')[0]='umls_source'or n.provided_by="identifiers_org_registry:umls") and not (n.description...

This is important for implementing #86.

This is definitely still an issue, as of `KG2.8.3`: ``` match (n) where (n.provided_by in ["['infores:atc-codes-umls']", "['infores:cpt-codes-umls']", "['infores:drugbank']", "['infores:fma-umls']", "['infores:go']", "['infores:hcp-codes-umls']", "['infores:hcpcs-cpt-umls']", "['infores:hgnc']", "['infores:hl7-umls']", "['infores:hpo']", "['infores:icd10-umls']", "['infores:icd10ae-umls']", "['infores:icd10cm-umls']", "['infores:icd10pcs-umls']", "['infores:icd9cm-umls']",...