Meeting with Faculty, School and Student Recruitment reps who work with students
22/07
Terminology and requirements
...
Terminology – suggested glossary as a solution “Get people used to the terminology that we use” – said this is ‘absolutely vital’. (Anne unsure about glossary as a solution)
General – Some kind of fast introduction to our navigation (location and purpose of main sections) or basic terminology could be useful.
Richard – terminology: they talk about ‘degrees’ when in schools.
...
Melissa – the units within a school are called 'programmes' within FHSS (maybe other faculties?). Were previously called 'departments'
...
Students moving between homesite and the older F&S sites – confused. Duplicated content, different templates.
Nicole – Sees the students who know how to get help, begging the question of what is happening to the rest. Website: students go down ‘rabbit holes’ to pages, often on F&S sites. Can’t find where they were when they want to find it again.
...
Melissa – reason why we refer to courses by codes not names is because it is currently v labour intensive to change the site when course names change (quite regularly). Paul said we have access to Course Catalogue to get accurate names from the code.
Degree planning
Melissa – BA course options – too diverse to show.
...
Craig - Engineering try to give all students an exist exit plan if they fail the courses required to proceed with a BE (and most have to convert to a BSc or information systems in a BCom)
...
General – degree examples: students are likely to just choose from the provided examples.
General – If the 'configuration' starts to be too complex (lot of options, exceptions, rules, variations etc.), 'contact a support/advisor' CTA could be shown.
Craig – need to tell school leavers that they need NCEA M or E for certain courses – A isn't enough. Exit options from degree – alternative pathways.
Limit to first year.