Chimera UI
This page documents the ongoing work on milestone 1.6 which is going to implement the epic #4 "better UI for Chimera". Further information on the redesign effort is to be found in issue #74 "SPIKE: how should UI look like?
We identified the following views that together form the new UI.
This view contains the visual elements that should be always visible, i.e. the header and footer. The part between header and footer is filled by one of the content views.
The header contains the following elements:
- Chimera logo
- Navigation breadcrumb
- Avatar box
The navigation breadcrumb component has the following parts, which are clickable links:
- organization Should this really be included? It would duplicate the current organization in the avatar component. However, we need a way to get to the case model overview.
- case model
- case model version
- case
- activity / data object
The avatar component displays the avatar of a user who is logged in. Next to the avatar the username is displayed with the current organization displayed below. This component allows users to log-out and switch their current organization, as well as to access their profile page.
If no user is logged in, this component is replaced by the login component. It contains text fields for username and password, as well as a login button. It also displays a link to register as user on this Chimera instance.
The footer component contains the following elements:
- Chimera version and build date
- Link to Chimera user guide
- Link to Chimera wiki
- Link to BPT and HPI
This view shows a list of the organizations available on this Chimera instance. The entries in the organization list link to the organization view of the respective organization. Furthermore, this view offers a button to create a new organization.
This view contains the organization name (which can be edited by authorized users) and a description.
Underneath, it has 3 tabs for managing case models (default tab), members, and roles of the organization.
This view lists all the case models belonging to this organization in a table with the columns case model name, date of creation, and number of cases. The table is sortable by this three columns in ascending and descending order. The case model name links to the respective case model, creation date and number of cases are not clickable. Each row of the table also contains buttons to edit and delete the case model.
This view lists the members of this organization. Each list entry links to the respective user profile page and contains icon buttons to manage the user's roles and remove them from the organization. Above the list is a button to add new users as members to the organization. A new member can either be a registered user on the Chimera instance, or someone who is not registered. In the later case their email address needs to be entered and an invitation mail is sent.
This view displays a list of available roles. Each list entry contains icon buttons to edit the role name and delete the role. Above the list is a button to create new roles. Todo: Do we need a separate role view? A role is just a name and an optional description. On the other hand, a role view would allow to display a list of members who hold this role.
This view displays information about a single case model. Part of this view is the cases sub-view, which is a list of all running cases for the current case model.
The case list is a sortable and filterable table with the columns "start date", participants, state.
This view shows information about a single case. It is separated into the parts case history, current activities, and case future.
This view displays information about an activity and offers buttons to terminate or cancel it.