Erica Wood

Based on this: ``` ubuntu@ip-172-31-59-112:~/kg2-build$ grep "CHEMBL.COMPOUND:CHEMBL254219" kg2-simplified-edges.jsonl | jq . { "domain_range_exclusion": false, "id": "CHEMBL.COMPOUND:CHEMBL254219---owl:sameAs---None---None---None---CHEBI:28544---UNICHEM_source:", "negated": false, "object": "CHEBI:28544", "predicate": "biolink:same_as", "predicate_label": "same_as", "primary_knowledge_source": "infores:unichem", "publications": [], "publications_info": {},...

This appears to have been part of a larger problem, where qualifiers was being mapped into a list rather than a dictionary: ``` "DrugCentral:antisense_inhibitor": { "operation": "keep", "core_predicate": "biolink:affects", "qualified_predicate":...

With e1548d3, this is fixed: ``` { "domain_range_exclusion": false, "id": "CHEMBL.COMPOUND:CHEMBL254219---DGIdb:inhibitor---biolink:causes---activity---decreased---NCBIGene:477---DGIdb:", "negated": false, "object": "NCBIGene:477", "predicate": "biolink:affects", "predicate_label": "inhibitor", "primary_knowledge_source": "infores:dgidb", "publications": [], "publications_info": {}, "qualified_object_aspect": "activity", "qualified_object_direction": "decreased", "qualified_predicate":...

Yes, it will be. It is also in the `KG2.8.5pre` build that isn't getting deployed.

See #339 for the cause. I'm going to leave the `verify this fix in next kg2 build` tag on, but that isn't for `KG2.8.4pre`.

This isn't in the KG2.8.4pre build, so it needs to stay open till we can verify in KG2.8.5pre.

``` Source predicate curie is missing from the YAML config file: ORPHANET:C057 Source predicate curie is missing from the YAML config file: RO:0002428 Source predicate curie is missing from the...

I once tried to set up something to email me when the Snakefile finished. It didn't work great, since anytime you are emailing from AWS, it goes to spam (and...

I think I found the offending line in dgidb's `interactions.tsv`: `MSLN Mesothelin 10232 TTD CAR-T cells targeting mesothelin CAR-T cells targeting mesothelin ` Based on it's entry on TTD's website...

> Looking at https://registry.identifiers.org/registry/ttd.target, we would need a different format of TTD identifiers that are NOT included in the interactions TSV to make them resolvable. > Though the example (https://identifiers.org/ttd.target:TTDS00056)...