You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue that concerns KGX is that instead of having a physical merge.yaml file, we dynamically create the file through the following steps:
Create a LinkML schema that replaces the merge.yaml file.
Create classes using gen-python from linkml
Create an object [MergeKG ] using the above classes based on the transforms that need to be merged.
This gives the flexibility of choosing which individual transforms need to be merged. Falls perfectly into the KG modularization discussion we've been having.
Use yaml_dumper to dump the MergeKG into a yaml file which is then passes to the load_and_merge() in KGX.
This step could be avoided if KGX could accept the MergeKG object directly in the function above rather than exporting it as a file.
The old merge_yaml had the structure (displaying only parts that need to be updated):
This is w.r.t a conversation with @sierra-moxon .
The project (or rather PR) that triggered this issue: Knowledge-Graph-Hub/kg-microbe-merge#1
The issue that concerns KGX is that instead of having a physical
merge.yaml
file, we dynamically create the file through the following steps:LinkML
schema that replaces themerge.yaml
file.gen-python
from linkmlMergeKG
] using the above classes based on the transforms that need to be merged.yaml_dumper
to dump theMergeKG
into a yaml file which is then passes to theload_and_merge()
in KGX.MergeKG
object directly in the function above rather than exporting it as a file.The old
merge_yaml
had the structure (displaying only parts that need to be updated):The new format equivalent will look like this:
Just
source
anddestination
are the ones whose design is updated.So the 2 features that can come out of this issue are:
cli_utils.py
to handle the updated merge.yamlload_and_merge()
to acceptMergeKG
object which is a linkml product.The text was updated successfully, but these errors were encountered: