Closed mslarae13 closed 3 months ago
Here is a branch for the issue https://github.com/microbiomedata/berkeley-schema-fy24/tree/Fix-compound-range
Update: The enums are being enforced which I confirmed by adding an invalid data file and testing the valid ones with different values. The issue seems to be with the generated documentation saying the range is a string (which is technically true) but it doesn't show the enums being used to enforce the values.
@sujaypatil96 can you help sort out why the generated documentation is wrong? https://microbiomedata.github.io/berkeley-schema-fy24/SolutionComponent/
@sujaypatil96 can you help sort out why the generated documentation is wrong? https://microbiomedata.github.io/berkeley-schema-fy24/SolutionComponent/
Should this issue be re-assigned to @sujaypatil96? @mslarae13
I'm going to remove this issue from the sprint and add the backlog label to it. If it should be active in the next sprint let me know. If it should be re-assigned to @Sujay Patil let me know.
@mslarae13 @JamesTessmer this appears to be a schema issue?
The definition for SolutionComponent
has the slot compound
asserted on it, but it’s range needs to be modified to ProteolyticEnzymeEnum
in a _slotusage statement underneath slots.
I would like for us to review the overall modeling of solutions and reagents. The range
slot_usage
s for compound
sound relatively safe to me.
see also (eventually!):
The documentation generation will be resolved with the release of LinkML version 1.7.6, until then the issue will remain open
@anastasiyaprymolenna does this have relevance for the re-working of ChemicalConversionProcess?
I'm working on a refactoring of everything solution related for Wednesday
compound
has been replaced by substances_used
Discovered while writing ADR
Refer to
https://microbiomedata.github.io/berkeley-schema-fy24/SolutionComponent/
Class:Solution
hasslot:has_solution_components
withRange:Class:SolutionComponent
whereslot:compound
hasRange:Class:ProteolyticEnzymeEnum
.