UX design improvements (dashboard UI)
To confirm the UX design improvements we walked through last week with your team. We'll go ahead with these changes in conjunction with the frontend dev for Colletion manager UI
Dashboard view as system admin
- In current design sys admins see all books and collection on their dash. This is now shown on a tab 'Books and collections'.
- The tabs 'Organizations', 'Users' and 'Error management' move from the Admin UI to the dash.
- From the 'Organizations' tab, systems click on an individual org which takes them to that organization's dash (next screen)
Dashboard view as member of one org
- The majority use case is for a user to belong to one org.
- In this new design, everthing related to a specific org is now in one UI: Books ans collections tabs shows only those belonging the org; the tabs 'Setting', 'Metadata template', and 'Users' move from Admin UI the orgnization's dash.
- This revised design allows users to create a book or collection from within the organization which simplifies the 'New book' and 'New collection' modals since we know what type of org it is (publisher or funder) and which workflows it supports (Word/PDF/XML). This means users make less decisions at book or collection creation step.
- The tabs visible depend on the user's role.
Dashboard view as member of more than one org
- If users are members of more than one org, they first see this page. Clicking on an individual org takes them to the view above.