Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • High level IA and site structure: Changing this is always easier before a major project rather than during or after. As such we urgently need direction or answers in this area. I think it sits with Nathan (and 'Tash for a few more days) to advance but I can not see a delivery date for a new IA. I am encouraged by the feedback of workshop participants with the direction of "audiences and their needs first", a pillar of how we think about the website and how we approach our work (but the devil might yet be in the detail). This is now on the critical path and maybe even a blocker, in that the following bullets are all reliant an a decision at this higher level. 
  • Lower level site structure and content plans: Well advanced by Anne, but potentially requiring rework depending on the high level IA work. Needs socialising with stakeholders, as it is currently a straw man or proposal. Workshops to date indicate an acceptance from half the faculties and a willingness to discuss from the others (but please do not mistake this for an agreement or willingness to implement). I suggest we have follow-up conversations with any faculty that does not seem onside with the "folding of school sites into the faculty site", meaning VBS and Science so far.
  • Navigation: From simple (page sections, hyper-links, etc) to more complex (contextual search widgets). Can we identify some more complex ones early, with sufficient knowledge of their importance that work can start on them now?
  • Functionality: I feel strongly that this area has to push ahead faster, partly because it is mostly new to the website (so therefore has a higher risk until we understand it better) and also because I am (or soon will be) half way through my contract and we have not yet built any new functionality, and this is an agile environment). I am thinking about this category (as tagged by Sam in Reframer for workshop observations) in terms of:
    • Engagement: The more simple, one-way functionality that allows the user to do stuff he/she wants with our content. Client-side, not restricted (much) by Squiz, generic/modular (in that it could be placed on any/all pages as required). Examples include share, print, book mark, download, etc. Can we identify some more complex ones early, with sufficient knowledge of their importance that work can start on them now?; and
    • Online Services: More complex, two-way, transaction-based functionality that allows the University to deliver a service to an audience online. Examples include buy, ask a question, subscribe, rate, register, change my details, etc. Can we identify some more complex ones early, with sufficient knowledge of their importance that work can start on them now?

...

  • 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 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 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

...