-
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
Update process for using display hints directly from the schema #750
Comments
@turbomam @naglepuff @marySalvi @jeffbaumes This has come up in some of the data portal user research. What is the best practice for which schema slot should be used for a tool tip display in nmdc UIs like the data portal? The screen shot above indicates it should be slot_usage.$SLOT.annotations.display_hit.value. Is that still correct? |
Default to description and have a way of overwriting it. @turbomam will do this for env context terms using annotations (ie brief_description) |
[not directly addressing this issue, but noting here as related] There may be an opportunity to spin out a separate “governance tier” for slot definitions for informal annotations, represented more dynamically e.g. as a database (“slotbase”?) rather than as a set of yaml files in a git repo. prior art / reference: https://metadata.raid.org/en/latest/#core-extended-and-local-metadata-schema-components |
|
Use |
actually |
So slot_usage.$SLOT.annotations.tool_tip.value? |
@turbomam I don't see any examples in berkeley-schema-fy24 or nmdc-schema which illustrate your most recent suggestion. |
Using microbiomedata/nmdc-schema#2120 as an example for how this should be formatted. |
Example of preferred way to model this:
|
Actually, I don't recommend that format (in which the annotation's key is repeated in the Otherwise, this compact form is preferable (in my opionion) annotations:
tooltip: GOLD Ecosystem Classification paths describe the surroundings from which an environmental sample or an organism is collected. |
Look into a process and verification that display hints from the schema are being utilized properly by the web UI. Specifically, we could look into doing this for the study metadata in the submission portal and ensure we are directly using display hints like the following in the UI:
@turbomam @cmungall FYI.
The text was updated successfully, but these errors were encountered: