-
Notifications
You must be signed in to change notification settings - Fork 8
Richer dataset metadata UI feedback #706
Copy link
Copy link
Open
Labels
EpicA collection of issues that are related by topic and can be addressed together.A collection of issues that are related by topic and can be addressed together.usabilityIssue affecting user or developer experience.Issue affecting user or developer experience.
Description
-
"Raw Data Available" icon on dataset card
- "available" icon color hard to distinguish from "unavailable" icon color -> the available state should ideally stand out more
- slightly misleading hover text, since this icon corresponds to
RepositoryURLwhich conveys that the raw data is readily available for download - maybe "Raw data available for direct download" or "Raw data is directly downloadable" would be a better fit?
-
Node mode icons:
- To avoid semantic confusion with the access type icons, I'd propose switching to icons that better convey "counts" and "records" specifically, rather than reusing access permissions icons
-
Show/hide details:
- Fix position of button in card so it doesn't disappear out of view when card is expanded
- For less text, I think simply "Details" would still work here
More minor
- inconsistent capitalization on hover text, e.g. "No Raw Data Available" vs. "No Homepage available" vs. "No derivative data available"
- home icons (icon set below the authors) is not left-aligned to the start of the author list
- some space between the buttons and text in the "Access" section of the details expanded section would help it feel more balanced
General
- Dataset card not super responsive
Questions
- Is having the “Access Data” (access link) button only in the expanded details intuitive?
- If someone included all authors as a single string item inside "Authors", would the UI break - i.e. would this super long string just show up untruncated?
Other
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
EpicA collection of issues that are related by topic and can be addressed together.A collection of issues that are related by topic and can be addressed together.usabilityIssue affecting user or developer experience.Issue affecting user or developer experience.
Type
Projects
Status
No status