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? | Former user (Deleted) to discuss w/ Graham | |
| 2 | will the team managing ref tables be central v local? | ||
| 3 | will the team managing users be central v local? | ||
| 4 | could there be an overlap of the two roles? So that one or both teams would need access to both areas | ||
| 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) Marital Status, Sexual Orientation, Ethnic Origin, Gender, Religious Belief, Title (2) College, GDC Status, GMC Status, Designated Body Code (DBC) (3) Settled, Immigration (4) Grade, Training Number, Training Number Type (5) Programme Membership Type (6) Curriculum, Specialty, Specialty Group, Curriculum Sub-Type (7) Site, Local Office, Trust (8) Medical School (9) Country (10) Nationality (11) Funding Type, Placement Type, Assessment Type, Leaving Destination (12) Status, Inactive Reason, Role? |
Add Comment