Page MenuHomePhabricator

User interface changes for Current Events Dashboard
Open, Needs TriagePublic

Description

Main components:

Problem:

  • On devices with low resolution, most of the screen is filled with information that is not immediately actionable without scrolling.

old.png (720×960 px, 128 KB)

Mock-up:

Wikidata Current Events Dashboard Mockup (2).png (720×960 px, 117 KB)

Wikidata Current Events Dashboard Mockup (3).png (720×960 px, 105 KB)

But this simpler footer works as well for now:

Wikidata Current Events Dashboard Mockup (1).png (720×960 px, 97 KB)

You can use https://mismatch-finder.toolforge.org/ and https://item-quality-evaluator.toolforge.org/ for inspiration about implementation.

Links for the footer:

Acceptance criteria:

  • The browser title reads “Current Events Dashboard” (it currently shows "Qurator...")
  • Remove Constraint Violation Checker for now.
  • Create a short Current Events README
  • Show 25 entries should move to the bottom (if possible within the scope of the tools used) (NOT DONE)
  • No "Frequently revised items in the previous 72 hours" shown
  • include “user feedback” for empty tables
  • Footer in the simple ("Made by the Wikimedia development team" etc) or ideally the new and advanced layout
  • No "Updated every minute. Previous 72 hours: As the data on recent changes accumulate we provide summary statistics on edits made in the previous seventy-two (72) hours (or three days) and update the table below every ten minutes. You can instantly update the dashboard by reloading it." should be shown
  • "Latest update" should move to the bottom
  • change the order of the tables from 6h-72h to 72h-6h (so that the first table shown will always be filled)
  • As we are sorting for Editors first and Revisions second, they should also appear in that order (as seen in the mockup).
  • Heading should read “Wikidata Current Events Dashboard” (text not picture if at all possible; if only text *or* a picture work for the heading let's go for just text then
  • Remove Google news column (e.g. not available everywhere)
  • Remove timestamp column (mostly redundant)
  • Align numbers right
  • Remove search box

Event Timeline

Manuel renamed this task from UI changes for Current Events Dashboard to User interface changes for Current Events Dashboard.Nov 3 2021, 10:41 PM
Manuel updated the task description. (Show Details)

Change 739359 had a related patch set uploaded (by GoranSMilovanovic; author: GoranSMilovanovic):

[analytics/wmde/WD/WikidataAnalytics@master] T294983

https://gerrit.wikimedia.org/r/739359

Change 739359 merged by GoranSMilovanovic:

[analytics/wmde/WD/WikidataAnalytics@master] T294983

https://gerrit.wikimedia.org/r/739359

@GoranSMilovanovic Can you please make it look structurally exactly like the mock-up? (e.g. order of columns, position & content of elements)

Can you please check whether the tabs are named correctly? It is ok to name them "6h" etc without "latest" as discussed. But there seems to be a mix-up of some sort in terms of what tables are shown.

Name and title read “Wikidata Current Events Dashboard” (text not picture, if at all possible)

Not possible. @Manuel: I am not a web designer. In serving dashboards, I work with limited possibilities offered by the RStudio Shiny framework, which is essentially an abstraction over Bootstrap. If you think that in the future we will need more design, UX/UI related tweaks and similar, we need to consider hiring a web-designer/developer or introducing someone who is in web-design/development already in WMDE.

It is ok to name them "6h" etc without "latest" as discussed.

It is not possible to enforce tab names in two rows in Shiny. I tried to find a way to do it and failed; if I eventually find out that something like that is possible I will implement the solution exactly as desired.

Can you please check whether the tabs are named correctly? There seems to be a mix-up of some sort.

Hm. You might be right - I need to check this carefully.

@Manuel @GoranSMilovanovic

Can you please check whether the tabs are named correctly? There seems to be a mix-up of some sort.

The dashboard is currently sorting out its findings by number of revisions - bug fix!

@Manuel Re: T294983#7509866

The dashboard is currently sorting out its findings by number of revisions - bug fix!

Actually, it is not sorting by number of revisions, I have just checked everything in that respect. It might be the case that one of us accidentally sorted some dashboard table by number of revisions in our 1:1.

@GoranSMilovanovic: Logic dictates that all 6h should be included in 24h, all 24h should be included in 48h, and all 48h should be included in 72h. This is still not the case, so something *must* be wrong here. As this is not a design problem I now moved it to a separate ticket: T296387: Some tables show wrong or incomplete information on Current Events dashboard

Design reasons why I cannot close this ticket yet:

  • As we are sorting for Editors first and Revisions second, they should also appear in that order (as seen in the mockup).
  • If only text *or* a picture work for the heading let's go for just text then.
  • The browser title still shows "Qurator..."
  • Show 25 entries should move to the bottom
  • "Latest update" should move to the bottom
  • no "Updated every minute. Previous 72 hours: As the data on recent changes accumulate we provide summary statistics on edits made in the previous seventy-two (72) hours (or three days) and update the table below every ten minutes. You can instantly update the dashboard by reloading it." should be shown
  • There is no "Made by the Wikimedia development team" etc footer In the meantime we have a new format for footers that we should try to adopt if we can.

@Manuel

Please let's follow the changes in the test environment first:

As we are sorting for Editors first and Revisions second, they should also appear in that order (as seen in the mockup).

Fixed.

"Latest update" should move to the bottom

Fixed.

If only text *or* a picture work for the heading let's go for just text then.

Done.

no "Updated every minute. Previous 72 hours: As the data on recent changes accumulate we provide summary statistics on edits made in the previous seventy-two (72) hours (or three days) and update the table below every ten minutes. You can instantly update the dashboard by reloading it." should be shown

Fixed.

Show 25 entries should move to the bottom

I still need to see if this is possible at all in datatable (R datatable docs | datatable docs)

The browser title still shows "Qurator..."

This needs to happen only when we decide to deploy in production.

There is no "Made by the Wikimedia development team" etc footer In the meantime we have a new format for footers that we should try to adopt if we can.

To Do. Please let me know if there is a selection of links that we want to include in the footer of this Dashboard. Thanks.

NEW from our 1:1 today

including “user feedback” for empty tables

To do.

Manuel: 1st prio is the bug about incorrect information

You mean the Some tables show wrong or incomplete information on Current Events dashboard ticket: of course. ASAP, I am monitoring the situation in the (restarted) test environment, and I will fix that as soon as I figure exactly what is causing the problem. From what I see now is that I know the problem to be related to the Dashboard's update engine - not the Dashboard components themselves.

Thx for the update @GoranSMilovanovic! Also from our 1:1 we discussed changing the order of the tables from 6h-72h to 72-6h so that the first table shown will always be filled. I added it to the description.

Manuel updated the task description. (Show Details)

Please let me know if there is a selection of links that we want to include in the footer of this Dashboard.

I added them to the description!

@Manuel

T294983#7529722

change the order of the tables from 6h-72h to 72h-6h (so that the first table shown will always be filled)

Fixed in the test environment (I can also see you have already check marked it).

No "Frequently revised items in the previous 72 hours" shown

Fixed in the test environment.

@Manuel

Footer in the simple ("Made by the Wikimedia development team" etc) or ideally the new and advanced layout

This is implemented in the test environment now, with the following constraints:

  • I could not change the background colour of the footer to match the one used in the mock-up and examples (note: of course, only pure Shiny tech was used to build the footer);
  • I could not find the Constraint Violation Checker served via any UI online, so I have linked the command tool's GitHub repo instead;
  • finally, all Wikidata Analytics products built since 2017 use GPLv2, so I have used that license in place of BSD 3-Clause License.

I need to fix the Current Events README too (a generic README from the {golem} pipeline for Shiny production is still in the repo).

@Manuel

Reminder on ToDos here:

The browser title reads “Current Events Dashboard” (it currently shows "Qurator...")

This will be fixed with the deployment in production; ShinyProxy server settings determine the title of the app and the URL from where it is served.

Show 25 entries should move to the bottom (if possible within the scope of the tools used)

I will do my best but thus far I cannot find the way to move it to the bottom of the table.

include “user feedback” for empty tables

To be implemented very soon.

@Manuel

include “user feedback” for empty tables

Done.

The footer is very nice! \o/

I could not change the background colour

That's fine!

I could not find the Constraint Violation Checker

Let's remove it for now.

GPLv2, so I have used that license in place of BSD 3-Clause License.

I'll ask the team about this.

I need to fix the Current Events README too

What would you suggest? A quick overview should do in this case, right?

I will do my best but thus far I cannot find the way to move it to the bottom of the table.

Then let's leave it where it is. We saved a lot of prime space already!

I need to fix the Current Events README too
What would you suggest? A quick overview should do in this case, right?

Exactly. I will take care of it don't worry; I've just mentioned that as a sort of reminder.

Remove Constraint Violation Checker for now.

Done: please check in the test environment.

@Manuel @Tobi_WMDE_SW

Create a short Current Events README

Done. N.B. I think we would need to include the description of the filtering criteria used on the dashboard in the README file once you decide upon T296387: see my T296387#7544835.

As I have mentioned previously,

The browser title reads “Current Events Dashboard” (it currently shows "Qurator...")

can be solved only in the deployment phase, since the App title is controlled by the Shiny Proxy config; so this last opened request will be resolved then.

When I wrote this ticket, I did not know we had limited time together. Under the new circumstances, the Readme is not a high priority. So let's not invest more time in this for now.

-> I will resolve this ticket as soon as we have this deployed with the new title.

@Manuel We already have a concise README file created yesterday.

I am building the image now and deploying the Current Events in production immediately.
I will ping back here when the system is online.

@Manuel Building the Docker image for Current Events is taking some time on macOS (this is due to my inexperience - I should have used my Debian server instead). I will ping back here as soon as the image is rendered and deployed to CloudVPS. Everything is ready it will just take some time until the system goes live.