We, the Connect for Life team, are working on moving Report pages to the new 3.x front end and we would like to make in a way that will benefit the community too.
The first step we planned is to move these pages from Reporting UI 2.x:
Reports Overview - where you see lists of available reports split into sections (configurable)
Report Page - where you can see, for specific report, queued or running report executions, results ready for download, and configure and start a report execution.
The report overview page has configurable tabs where implementer can arrange reports according to type/theme/anything.
Each record of an overview page can be expanded to show a list of report results ready for download.
An action on each record opens side panel where user can check if specific report is being executed and, regardless if it is running or not, configure and start a new report execution.
I’m just seeing these mock-ups for the first time now and have a few pointers and questions, that I hope will be helpful. Hope that’s ok
I wonder what the description field would actually show? Would the user write their own custom description of what the report is there? I wonder if it’s worth exploring displaying reports in formats other than tables like with a preview of page 1 instead of in a table? How should the reports be organised / sorted? By date? By type? By department?
It’s hard to know where exactly I am when looking at those screens. Am I in a detail page called ‘Reporting overview’? Where would I land if I hit the back button? Take a look at this section of the design documentation about the page headers
It looks like there’s 48px tables being used here, these are normally only used on tablet, otherwise, we use the 32px tables on desktop
I think the table-within-a-table thing is a bit odd, I wonder if there’s a better way to lay out this information, specifically the ‘available for download’ table within the reports table
On desktop, it can be nice to help declutter the UI to just have the action icons on each row appearing on-hover. I wonder also if there’s a way to avoid having an unlabelled, non-standard icon, as it’s not obvious what that icon button does…
I want to also say that the point of OpenMRS-3 is not to directly translate everything from 2.x UI into 3.x UI. Instead we should be starting with figuring out what reporting tools and features are needed by various user types and building them from the ground up with 3.x design patterns.
Of course, we’ll see many of the 2.x features there, but I want to encourage us to start with understanding what users need in terms of reporting, rather than starting with all the features that existed in 2.x!
By non-standard icon, I mean the kind of icon you can show to a user without a label and people will understand it, of which I’d say there’s at the most 3 or 4 in the world: overflow menu (3 dots), trashcan (delete), pencil (edit), and that’s about it! This calendar with a play icon is not clear what it does…
I was thinking we would meet together in an OpenMRS 3.0: Product & Design Sessions all together so we can discuss how to move forward + get feedback from the other members of the community. I was thinking the one of 5 December ? Does that work for everybody?