-
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
Fix example validation issues before merging nmdc-schema/main
into berkeley-schema-fy24/main
#73
Conversation
Updating slots to required for class FunctionalAnnotationAggMember, adding new class and slots for the metap aggregation collection.
Add is_best_protein slot
Update slots for MetaPFunctionAggMember
Updated to use new is_best_protein slot
Update range for is_best_protein to Boolean from BooleanValue.
Updating to Boolean instead of BooleanValue.
Make slots for KEGG aggregation tables required.
Updating to failed data can have no has_output.
Also, fix underscore-ness of other pseudo-"private" variables.
That way, we don't have to instantiate the class in order to invoke them.
…nation schema version
Removing rule to have has_output be optional if quality_control_report.status=fail
Testing removing invalid data of quality_control_report.status=pass mixed with failure_categorization.
snakecasing permissible values for FailureWhatEnum
Updating failure_what values to snakecase permissible values
Updating failure_where value to snakecase permissible value.
nmdc-schema/main
-> berkeley-schema-fy24/main
)nmdc-schema/main
into berkeley-schema-fy24/main
Resolving merge conflicts, updating format of qc information to what is in the nmdc-schema.
src/schema/basic_slots.yaml
Outdated
Slot to store additional comments about laboratory or workflow output. For workflow output | ||
it may describe the particular workflow stage that failed. (ie Failed at call-stage due to a malformed fastq file). | ||
|
||
instrument_name: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to get removed, re-adding this is why Database-data-generation-instrument_name-invalid.yaml is now passing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@turbomam not sure if you want to use the new deprecation way we talked about or if this should just be deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @mslarae13
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My vote is just deleted since it's the fork & we just deleted everything else.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you mean remove it from nmdc-schema production (main), then deprecation protocol we decided on. I think it would be a good spot for Sierra to help (if so)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops I already deleted it! but we can reconstruct a deprecation if you want @aclum
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deleting is fine with me.
@turbomam Database-img_mg_annotation_objects.yaml is failing b/c for most documents everything but type slot is commented out, edits in nmdc-schema for this file are from about a month ago. Recall what you were testing or can things be uncommented or deleted to resolve this? |
This reverts commit a69ad73.
@turbomam i need help with Extraction-NEON.yaml, if I strip this down to just id, type, has_input, has_output and conver to a extraction-set record I can get data to validate properly but not as an Extraction record itself.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Things that need to be addressed:
- Database-Extraction-invalid-sample_mass.yaml is failing but for unexpected reasons
- slot instrument_name needs to be removed to make Database-data-generation-instrument_name-invalid.yaml
- I have fixed a number of the valid example data files in the problem folder, those fixes are in branch https://github.com/microbiomedata/berkeley-schema-fy24/tree/berkeley-schema-replica-feedback/src/data/valid as discussed over slack. I'll leave it to @turbomam to decide how to get these back in
- I would like to change the permissible value names for FailureWhereEnum to match the berkeley-schema-fy24 class names, dropping 'Activity'. I'm willing to do this and update the example data but we might want to wait until after we've worked through the other issues.
I fixed all of the tests except
I still have to work on the permissible value names for FailureWhereEnum |
I'm really not motivated to hand-fix |
@turbomam can you point to this file? I'm not sure what you are referring to |
|
Thanks @turbomam that sounds good to me. |
Somebody said that Database-img_mg_annotation_objects.yaml was all commented out in nmdc-schema, so we shouldn't worry about making it fully valid in berkeley-schema-fy24. But it isn't commented out at all in nmdc-schema. If it has unique patterns in it that aren't validated anywhere else, then I would like to fix this file eventually, even if we do leave it in src/data/problem. @aclum Database-biosamples-infiltrations.yaml has become invalid since the last time I tried to validate this branch. I still think we should merge now. The build and test work. |
@aclum @brynnz22 Database-biosamples-infiltrations.yaml is failing the new pattern for relating a poetry run linkml-validate
--schema src/schema/nmdc.yaml \
--target-class Database src/data/problem/valid/Database-biosamples-infiltrations.yaml
|
@turbomam I think we just need to change |
merged a local copy of the
nmdc-schema
into a local duplicate ofberkeley-schema-fy24
now comparing against
berkeley-schema-fy24
'smain
will need to review the example data files that have been moved into the
problem
sub-directory@eecavanna who else should we invite as reviewers?