-
Notifications
You must be signed in to change notification settings - Fork 4
Missing edge categories? #88
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
Comments
KG-Phenio has edge properties, they're just quite minimal. This is the header:
Not much going on there! For comparison, here's the Monarch graph heading:
Not all properties will be necessary for PHENIO, but the knowledge sources can certainly be expanded. |
The merged Upheno mapping table also needs a knowledge_source added, but that can just be added at transform time as a KGX argument. |
Also want:
|
- Address some of #88 - Add primary_knowledge_source and aggregate_knowledge_source to edges as appropriate - Add knowledge source to provided_by for nodes
I was just poking at some kgx validation output and I noticed I had complaints about ZFA being an invalid prefix in ZP->ZFA associations, and it might have something to do with the blank categories. Here's a summary of edges with blank categories
|
I am not sure we have an implemented strategy for populating edge categories when going from owl->kgx This could be done in kgx by inference, gene to phenotypic feature association:
is_a: association
exact_mappings:
- WBVocab:Gene-Phenotype-Association
defining_slots:
- subject
- object
mixins:
- entity to phenotypic feature association mixin
- gene to entity association mixin
slot_usage:
subject:
range: gene or gene product
description: "gene in which variation is correlated with the phenotypic feature"
examples:
- value: HGNC:2197
description: "COL1A1 (Human)"
object:
range: phenotypic feature however I would do this with linkml:classification_rules now this will probably not be straightforward to add to kgx - @kevinschaper how much does our validation strategy depend on this being present |
It looks like we're hitting some kgx validation issues within translator infrastructure that might be coming in from blank category fields on edges. Would it work to just fill in with (I think I might do that in my phenio kgx massaging, and of course it won't do anything once they're set) |
@kevinschaper reports that kg-phenio may be missing edge categories.
The text was updated successfully, but these errors were encountered: