-
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
Indicate MIxS terms #555
Comments
Brandon, please add T-Shirt size and any questions. Team is trying to get an idea of the time/effort to do this. |
Please provide information/documentation about how to know if a term comes from MIxS. Is this consumable from code, or will we need to maintain own mappings? Where should we be looking for this info? Thanks. |
@ssarrafan this should be reassigned to Mark M. and Bill. Mark is currently working with Montana to identify sources of each term (where they came from) for display on the metadata submission interface. Once that information is available, hopefully Bill can include that information in the schema so that Brandon can also display it via the portal. |
@pvangay ok I've assigned this to Bill and Mark. Is the expectation that this will be done this month or can I move this to the January sprint? |
good question for @turbomam |
there are a variety of ways to programmatically extract this from the schema I can advise but need more information about the overall dataflow. I am assuming for UI purposes you will want a ready-made json blob containing all metadata about a field including source, description, hyperlinks for more info etc. Our libs for doing this are python but we can easily precompile json for you. |
I'm already consuming |
@subdavis The You can load the yaml directly yourself and convert to json or I can add a util to do this. What do you prefer? |
@wdduncan can this issue be closed? |
@ssarrafan I do not know. What do you think @subdavis ? |
Sorry, I'm late to the game. Where should it be indicated that a term comes from MIxS? If a term is to be used in the NMDC DataHarmonizer, it will be marked with a Slots/columns that are modification of a MIxS slot appear in mixs_modified_slots I will be proposing a new structure for this Google Sheet soon, so some of that may become moot. In terms of how the terms appear in DataHarmonizer, that will be determined by the |
Should be a small amount of effort. Also, I won't be able to directly map |
@subdavis I can create a json file on the github repo, or you can convert it yourself. Just let me know which prefer. |
I am really late to this game! But saw the message in slack & checked this out. |
See work discussed in this ticket microbiomedata/nmdc-schema#252 |
There are roughly 100 elements in what are the consequences of assigning more than one subset? Syntactically, in_subset is multivalued |
Removed @wdduncan per his note. HI Set. Here is an update: |
I think (but haven't proven yet) that all MIxS slots in https://github.com/microbiomedata/nmdc-schema/blob/issue-291-mixs-submod/src/schema/mixs_6_for_nmdc.yaml are annotated as follows: from_schema: http://w3id.org/mixs/terms Having said that,
I'm pretty sure that those annotations appear in @sujaypatil96's new-ish |
But the Yes, switch to |
Solution in microbiomedata/nmdc-schema#292 closing this issue in anticipation of a merge in May 2022 |
Indicate when a term is from MIxS
Related to #448
The text was updated successfully, but these errors were encountered: