sujaypatil96
commented
2 weeks ago When I look at the "Slots" table Then I can see columns for the following:
MIxS ID ✅
Full Name
Why do you want to see the full name when the short name is linked out? you can simply click on the page for the slot (with short name) and read what the full name is
Requirement
The cardinality captures the requiredness. See https://linkml.io/linkml/schemas/slots.html#cardinality page to learn how the cardinality syntax on the web documentation pages can be read/interpreted
Short Name ✅
Definition
Similar to full name, why would you want to see this when you can simply click on the documentation page for the slot and view the description. We should try to avoid cramming in information in tables because it has limited space on a web page and cramming in a lot of columns introduces horizontal scroll and that it is ideally undesired behavior
Value syntax
I'm forgetting what this means?
Expected value
I'm forgetting what this means?
Example ✅ -- "Examples" section
Preferred unit ✅ -- shown in "Range"
Occurrence ✅ -- shown in "Applicable checklists and extensions" section
only1chunts
User story
Acceptance criteria
Additional information
NB the above wording is how these are shown in the old excel formatted versions of the tables, below I try to map those to the names used in the LinkML version: Short Name = slot name MIxS ID = slot_uri Full Name = title definition = description Value Syntax = range Occurence = multivalued Example = examples Expected value = annotations: expected_value: text Requirement = ? I cant see this information stored in the terms.yaml file ? Preferred unit = I'm not sure, but I think this is stored in the packages yamls somewhere under slot_usage maybe?