✨New Feature: Treatment Filter

[SAHU-01]

Fixing #625

Describe changes proposed in this pull request:

• [x] Design treatment dropdown
• [x] Implement treatment dropdown
• [x] Normalize Filter Options

Screenshot:

Notify reviewers: @onursumer

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
htan-portal-nextjs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 5, 2024 10:52pm

[SAHU-01]

@onursumer I tried modifying the processSynapseJson.ts to include more treatment data but I'm not sure if this approach would work?

[onursumer]

@SAHU-01 I think a treatment list like this would work, but we may want to change the way we process the Therapy data in processSynapseJSON.ts. I'll add another comment/suggestion for that.

@onursumer I tried modifying the processSynapseJson.ts to include more treatment data but I'm not sure if this approach would work?

[inodb]

@SAHU-01 great work! Would it be possible to move the Treatment column to the cases tab? We can still keep it as a file attribute, but maybe better not to show by default

[SAHU-01]

@onursumer we can display Treatment column in case tab, I've set it up, by default it won't be visible in case tab, from the columns dropdown if treatment type is selected, the treatment type column will be visible. Like this:

Should I remove the treatment type column from file tab?

[onursumer]

@SAHU-01 I think we can make the new Treatment column visible by default for the Cases tab, and also keep it in the file tab but hide it there by default.

[inodb]

@SAHU-01 two minor tweaks that could be nice:

• [x] Move treatment filter to between Demographics and Assays (as it is a patient-level filter it feels a bit better there)
• [x] Data Access button can be less wide. The number of filter buttons are starting to reach the width of my laptop, this might help

[SAHU-01]

@inodb would this work?

[inodb]

@SAHU-01 perfect - thank you!