metaspace2020 / metaspace

Cloud engine and platform for metabolite annotation for imaging mass spectrometry
https://metaspace2020.eu/
Apache License 2.0
46 stars 10 forks source link

Dataset viewer redesign #553

Open LachlanStuart opened 4 years ago

LachlanStuart commented 4 years ago

Figure out how the Annotations page should look to support other use-cases & upcoming features

LachlanStuart commented 4 years ago

Ideas:

Overall design:

"Overview"

"Details"

"Ion image viewer"

LachlanStuart commented 4 years ago

Notes from Måns' demo of MSiReader

Comparing DSs:

Overlaying ion images

Diagnostic plots:

Intensity normalization

General UX

richardgoater commented 4 years ago

@aeisenbarth and I had a brief discussion about general UX at the weekend. We echoed Måns' point about the inline filter buttons, and also mentioned some unexpected pop-ups in certain places. @aeisenbarth would you like to comment?

LachlanStuart commented 4 years ago

@richardgoater Were the unexpected pop-ups from the candidate molecules popover?

image

We've reduced the vertical size substantially by limiting the number of items it shows, but it still takes up a significant amount of horizontal space, especially with the isobars warning or long molecule names. Here's a particularly bad example:

image

aeisenbarth commented 4 years ago
richardgoater commented 4 years ago

Collected Slack Comments

LachlanStuart commented 4 years ago

Notes from the meeting

“Views” of the data

Filters:

CR: “I would never not have the Molecules section open”

Structure:

Further discussion: These as separate pages:

Or somehow combine it into one page, or make the UMAP/etc a selectable right-side-of-the-screen fixture?

LachlanStuart commented 4 years ago

From today's strategic meeting - @LachlanStuart responsible for breaking this into tasks, analyzing what needs further analysis, triage, back-end dev, front-end dev.

LachlanStuart commented 4 years ago

I'm going to move this off the METASPACE v1.7/1.8 board on to the Roadmap board. This task doesn't warrant closing as it's not really complete and still has a lot of good info in the comments that may be used for reference later, but work is continuing in other, smaller tasks (currently #575 and #561), so something must be done with this task to stop it cluttering the main board.

LachlanStuart commented 2 years ago

I'm assigning @theodev to triage this (close, or break into concrete tasks for implementation) as he has the most context for it.