-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhance visualisation of data #425
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Target
The MDE and SDE shall be updated with dashboards, tables and graphical representations of data to give users a clear view of all data they are allowed to access and the relationships between those different data items.
Approach
Work with OUH to define the exact data representations that are required and implement those data representations.
The following two areas of enhancement have already been identified:
Technical
Kanban Board
This is a free Kanban board implementation, but it is quite old: https://github.com/DlhSoftTeam/Angular-Kanban
This is source code for creating your own Kanban board: https://www.genuitec.com/create-kanban-board-angular-4/
Investigate the options and assess which would provide the fastest solution and would be the easiest to maintain and adapt moving forwards.
Description
Request status timeline
Design a simple timeline that simply and clearly shows the requests progress through the request status workflow.
This timeline will appear in:
In both cases the timeline will appear within the request popup: inside the popup, on the top, just below the title
Kanban Board
Design a simple (open-source) Angular Kanban component to be integrated into the SDE administration. The kanban will be used as
better visualisation tool for the admins giving them immediate view of all available requests and what status they are.
Drag-and-Drop functionality is not required at this stage (probably won't in the future either as well established that Admins must open the request and review any changes before moving forward)
Planning and Requirements
Initial tasks set to start discussions and planning:
List of Tasks/Requirements
Timeline status representation
These are placeholder that need to be turned into proper tasks once everything is defined from corresponding Plannings:
Kanban representation
Display:
Sde-Admin-UI: Create a page to display the visual display, including styling and navigation links from the requests page
Kanban display should not replace the existing list but it will be a second option.
==> there will be something letting admins to select which view they would like to use
Sde-Admin-UI: Create a board component that consumes the state flow representation produced by the service and shows a grid with column headers being the available states
Sde-Admin-UI: Add the ability for the above board component to call a list of all requests.
Sde-Admin-UI: Create a card type component that receives a request from the parent component. That card will display information on the request including: type, current state and other info (todo: what other info?)
Sde-Admin-UI: modify the board component to display the card component in the right column according to its state. This card should link to the request page for a component when clicked
Sde-Admin-UI: Consider hooks to refresh the board when a request changes state externally
Sde-Admin-UI: Explore visual tools such as grouping, filtering and managing of visible cards and states.
Sde-Admin-UI: Explore what actions could be taken on the board for not allowing Drag-and-Drop actions.
The text was updated successfully, but these errors were encountered: