The mega nav needs to contain the following:
1.People
2.Posts
3.Programmes
4.Placements
5.Revalidation
6.Cases
7.System Admin– includes Role Creation, Permissions Management, Password Management
8.Data Admin
The following will be in the top navigation, but not part of the meganav - tbc if they are all in scope:
9.Settings – includes Password Management (own), e.g. Notifications Preferences
10.Notifications
11.Help
Design specifications can be found here - TIS_ Megamenu specs
Field labelling is discussed in the attached:
For Discussion
| # | Question | Comment | Owner |
|---|---|---|---|
| 1 | Can the security model be applied at the 2nd level? i.e. exclude certain functionality from particular user types? | Yes, in fact it is simpler to do so | Former user (Deleted) to discuss w/ Graham |
| 2 | Will the team managing ref tables be central v local? | Local Data Admin - they have access to components + data mgmt | |
| 3 | will the team managing users be central v local? | Central - they have have access to everything includeing all components, user mgmt and data mgmt | |
| 4 | Could there be an overlap of the two roles? So that one or both teams would need access to both areas | Yes, see #3 | |
| 5 | how many groupings should there be (roughly) for reference tables and what are they? (Go through known reference tables and group them up | DRAFT (1) Diversity | Marital Status, Sexual Orientation, Ethnic Origin, Gender, Religious Belief, Title, Role (to be removed?) (2) Professional Bodies | College, GDC Status, GMC Status, Designated Body Code (DBC) (3) Visa | Settled, Immigration (4) Training | Training Number, Training Number Type (5) Grade | Grade (6) Programme & Curricula | Curriculum, Specialty, Specialty Group, Curriculum Sub-Type, Leaving Destination, Programme Membership Type (7) Locations | Site, Local Office, Trust (8) Medical School | Medical School (9) Country | Country (10) Nationality | Nationality (11) Placements | Funding Type, Placement Type, (12) Assessments | Assessment Type (13) General | Status, Inactive Reason |
0 Comments