...
- Let COO run its course (pun intended). I have concerns over the delivery date (when each story gets done) and the prioritisation process (with David and Angela) from a WIP perspective in as much as we need to know what COO will give us, so we can either assume it will be there in time, or deliver it in WIP if we really need it.
- Does WIP want to deliver some of the COO stories (earlier, as WIP)?
- WIP has some additional course requirements in the backlog and might yet draft some more (as our understanding grows).
- Will a user want to see all courses:
- Related to a subject? But which subject list is used for this, given that the course attribute "subject" is based on the Banner codes and this is not a great match to our web subject? Further, if we abandon the Banner subjects in favour of marketing/recruitment oriented areas of study and subjects we will no longer be able to express this relationship.
- Related to an area of study (see below for a definition)? ? See definition below. Would be an inheritance approach or a search based on a join, with the results normalised.
- Taught by a certain staff member?
- Taught (by staff) in a certain school?
- Required for a programme? This touches on where is the master of this data, can it be accessed as a feed, is it understandable by a human, etc?
- Related to a specific course (still ? Still need to define related but I think of same subject or area of study, same level plus or minus one level,
- Recommended by others? Still needs defining but I think of a recommendation engine hooked in to either the enrolment data or GSA
Subjects and Area of Study
...
- The proposed term to cover a cluster of related/similar subjects (can also be though of as "topic" or "area of interest/enquiry')
- Would be a starting point for a future student who is exploring what to study
- Would map to subjects, programmes and maybe even courses (issues here listed in course section above and subject and programme sections below)
- All work to identify these (including if they will work) is on the critical path.
- Where the mapping between area of study and subject is:
- One-to-many: Use area of study before they move to subjects,
- One-to-one: Use area of study instead of subjects.
- Could be related to a faculty (or two)
- Could be related to one or more schools
Subjects
- Could be at the same level as areas of study (where there is only one in an area of study) or lower. What will this mean for content plans?
- Might require a related subjects list (currently manually maintained)
- Is related to a school (and through this to a faculty)
- Can be studied through one or more programmes (maybe we show advantages of each, if more than one)
- Could display the "associated staff", based on roles (e.g. teaches this courses related to this subject, researches in this subject area, is librarian with responsibility for this subject area). All this might also apply to area of study.
- Could display research opportunities: Based on research interests of staff (see above bullet point), research projects (especially if funded), institutes/centres/chairs, etc. All this might also apply to area of study.
Programmes
- Assuming we market programmes, is there room to improve the information about them?
- Expressed the mapping to subjects in reverse?
- Do students want to know the courses required by the rules of a programme? (also covered in the courses section above)
- This touches on where is the master of this data, can it be accessed via an API or ingested somehow, is it understandable by a human, etc? An important question, that could take some time to answer.
- Would this also need improved data quality in course outlines, which in turn would mean a design of the Banner form/screen for data entry?
- This could be a lot of information, so careful UI design is a must. Josef, enter stage left.
- Are administered by a faculty