Concern that users might see an all-grey screen and be confused.
Chantelle and other scientists want to explain what the features are and what they are calculated on.
Q: is that actually a concern?
Globally, many of our datasets do need more information/context
Lyndsay doesn't want us to rush into a decision -> we should build something that is generalizable across our apps.
Minimal thought is an indication of full track feature vs. subset track feature?
Suggestions:
Tooltip on feature dropdowns -> include a full description string in the tooltip, opened as #371.
Dataset Info, feature glossary area, etc. -> extension of #198
Should this be in a tab? In the header?
"View glossary" -> link to external page?
Sidebar or panel that slides in?
Change play button
Chat w/ Chantelle:
Markdown dataset info would be OK
String feature description would be OK
On quilt, the "collection" level is what has descriptions attached. But probably OK to have the "dataset"-level have its own description. (For NucMorph they will all be the same.)
UX Questions
Where would dataset info go in the app?
How do we make it share placement with our other viewers?
Developer Questions
Does this make sense as Markdown? iframe?
Collections? Datasets? Who provides these?
Below to be filled out by UX during kickoff Q&A to the best of current understanding
Size
Effort level (xs, sm, m, lg, xl)
Scope
What will we do? What will we NOT do?
User needs statement(s)
As a [type of user], I need/want to [action(s)], so that I can [goal].
Discussion Notes
Suggestions:
Chat w/ Chantelle:
UX Questions
Developer Questions
Below to be filled out by UX during kickoff Q&A to the best of current understanding
Size
Effort level (xs, sm, m, lg, xl)
Scope
What will we do? What will we NOT do?
User needs statement(s)
As a [type of user], I need/want to [action(s)], so that I can [goal].
Additional notes
Knowns/unknowns, stakeholders, time/dependency considerations, deliverables