-
Notifications
You must be signed in to change notification settings - Fork 12
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
Bug?: Obographs parser: metadata not utilized; getting 0 mappings #456
Comments
ConceptMaps Feature Added output for FHIR ConceptMap JSON. Currently having some issues, mapping-commons/sssom-py#456, so have added param include_concept_map to toggle off. - Add: Dependency: sssom - Add: test/ directory, and initialized with inputs and test case - Add: Scripting for this work General - Delete: Support for SemanticSQL intermediary
One terminological thing here: a mapping is not a relationship. Its a correspondence between two terms. The lines between the two are very hazy in practice, but in our minds we should draw them, because otherwise sssom becomes another ontology formalism (basically able to publish all possible triples). This must be avoided. In your case, did you try to use the https://mapping-commons.github.io/sssom-py/cli_usage.html#sssom-parse method with the --F/--filter-mapping-predicates option? |
Great point; this is another case where I missed the forest for the trees. It all makes perfect sense now. Should've been totally obvious to check the docs.
New issues1. Docs about the nature of mappings?I glanced through the SSSOM docs but I didn't see anything about what a mapping is and isn't. Im' guessing it has something to do with the concept of "degree of equivalence / shared properties". Is this in scope for the docs? I'm not sure. Could also include short list of preds SSSOM considers by default (I'm guessing something like skos exact/broad/narrow/close/related & oio hasDbXref). 2. Bug?:
|
ConceptMaps Feature Added output for FHIR ConceptMap JSON. Currently having some issues, mapping-commons/sssom-py#456, so have added param include_concept_map to toggle off. - Add: Dependency: sssom - Add: test/ directory, and initialized with inputs and test case - Add: Scripting for this work General - Delete: Support for SemanticSQL intermediary
ConceptMaps Feature Added output for FHIR ConceptMap JSON. Currently having some issues, mapping-commons/sssom-py#456, so have added param include_concept_map to toggle off. - Add: Dependency: sssom - Add: test/ directory, and initialized with inputs and test case - Add: Scripting for this work General - Delete: Support for SemanticSQL intermediary
ConceptMaps Feature Added output for FHIR ConceptMap JSON. Currently having some issues, mapping-commons/sssom-py#456, so have added param include_concept_map to toggle off. - Add: Dependency: sssom - Add: test/ directory, and initialized with inputs and test case - Add: Scripting for this work General - Delete: Support for SemanticSQL intermediary
You should turn 1) into issue on sssom repo, 2) into issue on sssom-py (both very good requests) and (3) could be made into an "example paragraph of (1) |
Overview
I'm working on a PR to add FHIR ConceptMaps to the TIMS OMOP/OWL to FHIR conversion tooling.
I am stuck on an issue where when I convert OMOP -> OWL -> Obographs -> SSSOM TSV, the TSV does not contain any mappings.
Command & main inputs / outputs of concern
Command:
f'sssom parse {obograph_path} -I obographs-json -o {outpath_sssom} -m {metadata_path}'
(sssom parse /Users/joeflack4/projects/owl-on-fhir/test/output/test_defaults/RxNorm.owl.obographs.json -I obographs-json -o /Users/joeflack4/projects/owl-on-fhir/test/output/test_defaults/RxNorm.sssom.tsv -m /Users/joeflack4/projects/owl-on-fhir/test/output/test_defaults/temp-metadata.sssom.yml
)Inputs:
Output: RxNorm.sssom.tsv
Discussion
RxNorm.owl is a subset of the OMOP content. It's only 472 lines.
Includes namespaces:
Example class snippet (truncated)
I expect / want every object property declaration from the second half of the snippet to be a single row in my SSSOM TSV.
When I convert to Obographs, it looks like this:
Obographs snippet
In that snippet, you can see some of the relationship mappings:
In the top of these 2 mappings, I manually edited the JSON to replace the CURIE with a URI to test if that would work, but it didn't.
These namespaces exist in my metadata YML, so why aren't any mappings being generated?
Additional info
For reference, I looked at how OMIM is being converted to Obographs and SSSOM to double check what I was doing was correct.
The PR has a test case for this, FYI.
The text was updated successfully, but these errors were encountered: