Closed turbomam closed 2 years ago
@cmungall is suggesting that I do as much of the template building by parsing the LinkML model of the various MIxS yaml files at https://github.com/GenomicsStandardsConsortium/mixs-source
So GAZ content isn't important to us and SPARQL against OntoBee isn't a solution we would probably use.
This issue is just a worked example on "how would you do automated template generation?"
As a first step a LinkML version of DataHarmonizer would at least allow select field sources to identify the ontology vocabulary branch(es) to fetch terms from - but there would likely need to be features for placing constraints around that, like fetch terms to a certain depth. A past project offered a dynamic lookup service so that the project config files didn't need to have the whole vocabulary loaded. But this becomes a bit of a load when validation is required on such fields.
P.s. our previous GAZ and DO dynamic lookup system went straight to OLS API. You can see it in action in example form https://genepio.org/geem/form.html#GENEPIO:0001777 - any of the "lookup choice" fields will provide a popup if you provide an initial choice to start from. (Its a prototype we would redo the code for btw). If OntoBee isn't a solution would OLS be for dynamic lookup?
Thanks @ddooley
I think I was too eager to create an issue here. I'm well on my way to creating templates by parsing LinkML files. I think that should be self sufficient and not require any external lookups. I'll share my code soon.
direct answer to your question: yes, I use OLS a lot and using it for this poorly worded issue would make sense, if external lookups were required.
Here's my work in progress for creating a DataHarmonizer template from a LinkML schema
I've shared the converted website as a github page
None of this is guaranteed to stay in the same location or to be up 100% of the time
There is a
geo_loc_name
section in the CanCOGeN template. I assume somebody entered the content below mostly by hand?I would be interested in a tool that could populate the following into the template just by specifying the parent term GAZ:00002561 'Province (Canada)'. Then the user could add, delete or modify any of that.
Or instead of a tool, it could just be some documentation/hints... see further down
Sample documentation
"Run the following query at" http://sparql.hegroup.org/sparql/