Erica Wood

Per my exchange with Sierra, while the `infores_catalog.yaml` file is still on the short term specifications, we should be using the long term specifications: > For the knowledge_level and agent_type...

It does look like this information is in the DrugBank XML download: ``` Eliglustat is a glucosylceramide synthase inhibitor used for the treatment of type 1 Gaucher disease.[L41404] Gaucher disease...

This is in the `umls-chv.ttl` file: ``` a owl:Class ; skos:prefLabel """fentanyl overdose"""@en ; skos:notation """0000040137"""^^xsd:string ; """-1"""^^xsd:string ; """-1"""^^xsd:string ; """-1"""^^xsd:string ; """-1"""^^xsd:string ; """no"""^^xsd:string ; """-1"""^^xsd:string ; UMLS:has_cui...

It appears that URL is no longer available and this is the correct one now: https://data.bioontology.org/ontologies/ORDO/submissions/27/download?apikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb (Source: https://bioportal.bioontology.org/ontologies/ORDO)

This was actually fixed in the `KG2.8.5pre` build by downloaded `ordo.owl` from kg2erica.rtx.ai onto the build instance.

This result no longer exists at that URL. However, I was able to reproduce the issue here: https://arax.ncats.io/?r=148548. It appears the problematic categorization of acetylcarnitine is coming from LOINC: Identifier...

Per https://bioportal.bioontology.org/ontologies/OMIM?p=classes&conceptid=MTHU000220, `hepatitis` is stored as a subclass of `liver`. We may need to change how we import OMIM if this is important, because this seems to be exactly how...

This ties into #281 (though that is more limited in scope and will occur at a different place in the build process). Overall, it would probably be good to consider...

As of `KG2.8.3`, there are 1554 `subject`-`object` category pairs and 10439 `subject`-`predicate`-`object` pairings. Here are the results of ``` match (n)-[]->(m) return distinct n.category, m.category ``` [edge_category_pairings.csv](https://github.com/RTXteam/RTX-KG2/files/11985387/edge_category_pairings.csv) ``` match (n)-[e]->(m)...

Hi @saramsey, yes, the KG2pre build system currently ignores those domain and range constraints. Our biolink validation is limited in scope overall, but certainly with regards to domain and range.