-
Notifications
You must be signed in to change notification settings - Fork 0
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
Create LinkML files for all Toy data #55
Comments
Based on the documentation, there are two possible commands:
and
|
Trish, I haven't looked deeply into this so you likely know more than I do but I was able to build it all into one schema using this:
Now, I don't know if that is a good schema or if there are reasons we would want this to be a separate schema for each file but my sense is that having it all as one single schema is probably more flexible for different data sets so we don't have to rely on manually specifying schema names. |
We do probably want to name the schema when we make it... like this.
|
Yes, I imagine that Having one model file is fine with me and a question I wanted to run by you. |
What I try to keep in mind is that ideally we'll have essentially no human interaction in this. So we want to be able to put the data somewhere, target that location and have it do everything, perhaps with a variable to say what dataset we're working on. |
for the conversion, yes, no human interaction, but then a human will need to review the file(s) that are generated |
Given the toy data in
toy_data/initial
of:Create LinkML using SchemaAutomator for each file. It is ok to have each of these as separate model files.
The documentation for SchemaAutomator should be updated with any new information needed.
The text was updated successfully, but these errors were encountered: