elixir-luxembourg / daisy

Data Information System (DAISY) is a data bookkeeping application designed to help Biomedical Research institutions with their GDPR compliance.
GNU Affero General Public License v3.0
13 stars 10 forks source link

Change user dashboard #150

Closed pinarpink closed 3 years ago

pinarpink commented 4 years ago

Is your feature request related to a problem? Please describe. Currently the user dashboard includes boxes that list things like:

Based on our DAISY use experience with LCSB users, we can say current items in dashboard do not make sense to the regular user.

Describe the solution requested

We propose that the dash board includes, instead the following lists:

Describe possible alternatives

This issue should be discussed among team before starting with implementation.

Other info context

vildead commented 4 years ago

Great! After discussion with @evescat, there is more to discuss:

daisy_web_home1

jLebioda commented 4 years ago

I like the ideas very much!

Regarding the search box - @neoflex, is running the query over different models feasible in solr?

jLebioda commented 4 years ago

The shortcuts "add new project" and "add new dataset" could be included in the boxes on the left, e.g:

Screenshot 2020-04-21 at 17 54 12
pinarpink commented 4 years ago

@vildead @jLebioda both scrshots look great!! I vote for add buttons to be located in respective boxes (as in Jacek's scrshot). I propose to rename " Upcoming events" to either "Notifications" or "Expiry Alerts"

pinarpink commented 4 years ago

@jLebioda @vildead is there already a branch for this? I am wondering if it is doable (without the quick search.) before the 19 May workshop?

jLebioda commented 4 years ago

I will push the branch in a few minutes

Sure, I will do my best

jLebioda commented 4 years ago

The feature will be developed on 150-new-dashboard branch (https://github.com/elixir-luxembourg/daisy/tree/150-new-dashboard)

jLebioda commented 4 years ago

Currently it looks like that:

Screenshot 2020-05-08 at 13 27 34

Collecting all the expiration events for the user might be costly - we might want to avoid having heavy code on index page; possible it could be calculated once per day as a celery task or cron job. BTW, would it be a brand new feature? I tried to find some code related to getting the events but I couldn't find any

pinarpink commented 4 years ago

@jLebioda hey! that was quick.

pinarpink commented 4 years ago

@jLebioda I had a closer look, there's quite a bit stale code wrt notifications, mail send etc, which has not been tested. My vote is to leave out notifications from the dashboard for now.

jLebioda commented 4 years ago

OK, so I'll just hide the right-hand side.

In effect, we'd have:

pinarpink commented 4 years ago

@jLebioda agreed!

jLebioda commented 4 years ago
Screenshot 2020-05-08 at 16 37 05

added a small help block to maintain the alignment

pinarpink commented 4 years ago

@jLebioda You were ahead of me with the user guide link. Looks very good!

vildead commented 3 years ago

already done