| Proposed order | Project phase | Content area | Current location(s) | Proposed location(s)
| Delivery approach (to move from current to proposed) | Implications | Dependencies | Risks (or in risk register) |
|---|---|---|---|---|---|---|---|---|
| 1 | Phase 2 | Topics (and associated subjects) | Topic pages are a new creation and do not currently exist. Subjects exist on faculty sites, school sites, Future Students and Victoria International (VI). They are likely to be based on the same content (i.e. one "asset ID").
. | Future Students (until renamed Study at Victoria). Will pull through to VI. Could pull listing through to school and/or faculty sites, if required. | Approximately 50 topics pages to develop, including 2 PG only topics (that could be differed). At the highest level we either develop all topic and programme pages in private and then go live with them all in one go, or we go live in batches If the later we either
I would discarding the option of publishing new topic and programme pages but leaving the old ones (on at least some sites) live until all topic-programmes are up and then turn off all the old ones. We do not want to increase the number of versions of the truth or leave old/dated subject pages live any longer than we have to. | Launch the full mega-topic and topic structure with the first topic(s), but with all other topics/subjects mapping to the existing subject pages
| Enabling new topic pages with the matching UG programme page seems to be the most sensible approach, in that it delivers returns early, minimises the risk of a big go-live and allows us to learn and tailor our approach as we go Subjects that can be studied (only) at the PG level could be mapped to existing PG pages until we remap them. However, turning off subject pages may, in some case, remove programme rules that are not available elsewhere on the website In this case we might have to move the PG rules from a subject page to somewhere on the existing PG programme page. The related topics block might be "messy" until all topic pages are developed. We could map to old subject as an interim or develop the block in a later release.
| Knowledge of the topic approach is held by only a few people. Resistance or objection to this direction could, at least slow us down, but might even force a change of approach Reputation/image during the transition period: Some subjects are covered by new topic pages while others are still on old subject pages. Faculties' willingness to have the new-old version split live at the same time. Easier to manage when a faculty has a tight offering but difficult for the broad ones. (No matter how much we try) We will fail to identify all the links that we break when turning old pages off. So long as we fix them promptly when we find them (ideally via a pro-active tool search but at least when reported) it should be okay. |
| 2 | Phase 2 | Undergraduate programme pages | UG degrees exist on faculty sites, school sites, Future Students and Victoria International (VI). They are likely to be based on the same content (i.e. one "asset ID"). | Future Students (until renamed Study at Victoria). Will pull through the VI. Might pull listing through to faculty (probably not school) sites. | Approximately 18 UG programme pages (including 3 pre-degree ones that map from subjects and need to be taken off school sites, and 2 Honours that are really qualitative passes in the 2 four year Batchelor degrees) to develop. Decommission the old UG programme pages when new UG programme pages go live, which in turn is best linked to then the feeder topic pages go live (see row 1 above and the pseudo step in the row below) | See above This approach relies on the new programme page containing the "rules" for all majors. I had initially thought that this programme page could only go live once all majors were included, even if those majors are taught by another faculty to that which "administers" the programme in question (e.g. the BA has 40 majors (plus 6 listed minors and "hanger on" subjects), including 8 taught by other faculties). However, following the same reasoning as captured in the following row, I realised that we probably have some options here. We could go live with a new programme page and the majors it represented by the subjects in the first (few) topic pages maybe one mega-area's worth), while leaving either the new or the old programme page mapping to the old subject pages for all the other majors.
| See above Further, it is unlikely that we can "remove" old subject pages until we have enabled the new programme pages, as the subject page currently has the appropriate major rules. So, our rewrite of the programme page is not only to "refresh" the content but also to integrate all the major rules that are currently on the subject pages but will not make it through to the new topic pages. Ideally, all courses would have outlines published via COO. We should map to the course finder result, even knowing that it is only a subset of attributes available on an outline. I believe that we also have to deal with a small number of pre-degree programmes, content about which is only available on current school site (and even then patch and hard to find). I believe that there are only three, the first two of which have a topic mapping:
| The TEC Information for Learners initiative could result in prescriptive requirements for UG degree pages. At the current time, not enough is known to plan for this. Vic has a representative on the working group, but they are not part of Marketing/Web. There is a risk that programme (or subject) pages on the old faculty and school sites is shared or surfaces in more places than we realise. Decommissioning pages would then cause other things to break. An alternative to decommissioning is to "deindex"(making the page hard to find) and stop linking to it, but leave it "live". |
| 3 | This row is not the next step in content deliver, but a discussion on the two rows above. The table as it stands implies a linear approach (i.e. we will do all topic pages before doing the first programme page). My preference is that we do (i.e. research, write, load, and commission) "pairings" or "bundles" of a programme page with the matching topic pages. For example, we do the BAS programme with the architecture topic page, the BBSc programme page with the building science topic page, the BDI programme page with the design topic page. These bundles make up the releases to production, allowing us to deliver early (relatively) and often, so benefits acrue to the users and the university. This only leaves a transition challenge to deal with. How can we ensure a good experience for all website users from the time we publish the first bundle until we publish the last? It might be many months and users will roam all over the topic-subject-programme offering. No matter whether they are viewing new or old pages they still need to understand where they are and have some unifying elements I believe the solution is in the new taxonomy. We augment the topic nodes to (temporarily and as navigation only) include the subjects, then map each and every subject to the existing subject pages. This navigation could be integrated to the existing Homesite now (i.e. without any new topic or programme pages) and even deployed in production, dealing with many of the navigation bugs we would otherwise encounter when the first bundle goes live. Then, as we release the programme-topic bundles we remove the temporary subject navigations and break the links to the old pages, replacing them with the new pages. From the time that the first bundle is live (say architecture) all users can use the taxonomy-based cascading navigation as the unifying element. We can add bundles as and when they are ready, incrementally converting the links from old subject pages to new topic pages. There are some cases where this mapping is less than perfect, so a little "fudge factoring" will be required, but there is nothing too alarming. Another advantage of this approach is that it works well for topic pages that map to two programmes (e.g. Electornics and mechatronics in the Engineering and Computing mega-area). The topic page can go live when the first programme page is ready, with the second programme linking to the existing programme page, until such time as we rewrite the second programme page. There is an issue where a subject maps to two programmes (e.g. Economics on the Economics topic page, or Actuarial science on the Finance topic page). We are unable to decommission the subject page when the topic-first programme pairing goes live, because the major rules for the second programme would be lost. This only affects 9 subjects, 8 being the BA majors taught outside FHSS (6 of these are also majors in the BSc, 1 in the BCom and music (shared with NZSM and the challenges of another site)) and Actuarial science (BCom and BSc). I have thought of two options to address this issue:
With an approach for these known issues the main risk is going live with (one or more) releases during the main enrolment period. Good testing prior to go-line will reduce likelihood of this risk materialising, and a prompt response will minimise the impact. Maybe we can rate/rank this more formally in the project risk register. We could also Discussions with the faculties and schools impacted is important, as they need to understand the implications of the "mixed" user experience, as well as the benefits of having the new marketing material being used for this season's enrolment. | |||||||
| 4 | Phase 2 | Postgraduate programme pages | PG programmes exist on faculty sites, school sites, Future Students and Victoria International (VI). They are likely to be based on the same content (i.e. one "asset ID"). | Future Students (until renamed Study at Victoria). Will pull through the VI. Might be pulled through to a PG hub/zone, if and when one is created | Approximately 120 programme pages that map from topics and subjects (even though this is unlikely to be the primary path to discover them) to develop. Decommission old PG programme pages when new PG programme pages go live.
| Exclude PhD/doctoral/higher degrees, which will be handled in Phase 3 with FGR. For many subjects there are a large number of PG programme options. We will probably have to help users distinguish/compare easily/quickly. This implies new data and maybe tools, as well as a possibly new "programme set" that should go live at the same time. There are also pathways of "nested" qualification that will require special attention to display and deliver. An example is that in the same time as it takes to do an MBA one could do a certificate, a diploma and then a masters, giving three exist points and only requiring a small time/cost commitment for each qualification step. | PG user research to identify the user requirements, especially their information needs. Most international students are PG, so input from the International Office is a requirement.
| Needs that are so different that they can't be met by topics and/or programmes, requiring us to develop an entirely new approach. The sheer number of programmes mean that this task will take quite some time. The Calendar often combines a certificate and a diploma in to the same set of rules. Can we do the same (i.e. combine some programmes pairings on to one page)?
|
| 5 | Phase 2 | Staff profiles | Staff profiles exist on school and faculty pages (as well as elsewhere), in different places and using different methods | Homesite, exact location TBD | Develop and deploy the templates and technology, then encourage people to start moving. Supported by training material? | All staff profiles must be moved before we decommission a faculty/school site. If we follow an opt in approach, what do we do with the profiles where staff have "created" a new one. Can be surfaced on school/faculty sites, once these are built. | Solution for the various edge cases Support from ITS, possibly Webstruxtures. | Our proposed solution, while better and more consistent that the current practice, may still not cater to all types of profile need. |
| 6 | Phase 2 | Information for current UG students | Information, forms and resources for current UG students exist on faculty sites, school sites, and Future Students. It is unlikely that it is the same content (i.e. one "asset ID") but 'Tash can probably confirm. | Homesite, exact location TBD | By content area: Remove all the UG student information and resources from all old school and faculty sites, sort it to remove duplication, and find a "home" for it on Homesite (assuming that it is not already there). | That the content is valuable enough to keep/move and that a place can be found to put it. If school specific it will be located on the new school site Would include scholarships, support, etc. | I/A work on the Current Students hub Core team capacity | |
| 7 | Phase 2 | Information for current PG students | Information, forms and resources for current PG students exist on faculty sites, school sites, and Future Students. It is unlikely that it is the same content (i.e. one "asset ID") but 'Tash can probably confirm. | Homesite, exact location TBD | By content area: Remove all the PG student information and resources from all old school and faculty sites, sort it to remove duplication, and find a "home" for it on Homesite (assuming that it is not already there). | Exclude FGR's faculty site and postgraduateLife, which will be handled in Phase 3. If school specific it will be located on the new school site
| Core team capacity | The experience for PG students, an important customer group, remains suboptimal. |
| 8 | Phase 2 | Research information | Information for, on and about research (including funding, etc) exist on faculty sites, school sites, and Future Students. It is unlikely that it is the same content (i.e. one "asset ID") but 'Tash can probably confirm. | Homesite, exact location TBD | By content area: Remove all the research information from all old school and faculty sites, sort it to remove duplication, and find a "home" for it on Homesite (assuming that it is not already there). | Exclude research centres, institutes and chairs, which will be handled in Phase 4, assuming that they are currently in their own site. Where these entities have a web presence that is not a site, but part of a school or faculty site another approach is required. This would be to leave the appropriate page(s) live but not indexed, while decommissioning the rest of school/faculty site. If school specific it will be located on the new school site
| Engagement work Core team capacity | These will wait a long time and some are already long overdue for attention |
| 9 | Phase 2 | Other content still to be identified. | Information currently on most school and faculty sites, required going forward but unlikely to be located on the new school and faculty sites. | Homesite, exact location TBD | By content area: Remove all this content from all old school and faculty sites, sort it to remove duplication, and find a "home" for it on Homesite (assuming that it is not already there). | A place holder for areas we haven't yet identified, or are not yet well placed to assess. Recognises that we might want to follow the "by content area" approach for longer before starting the first faculty site. | ||
| 10 | Phase 2 | School and faculty sites | School and faculty information exist on faculty sites and school sites. | Homesite, exact location TBD | Develop new content for the new sites. Any content or media that is "reused" will be loaded again in the new location. | Include the following at this time: Alumni: Five schools and faculties only; could be moved to engagement hub, if one exists by then. If not, try Alumni, Overseas exchanges: Move to Victoria Abroad
| If COO is not fully implemented/rolled out we will need to create a page/space for outlines, at least temporarily.
| Sites of some research centres are very similar to school sites, but we won't consider how to improve them until later. See F&S proposal: A new approach to faculty and school content (v.2) for other risks related to the implementation of the approach. |
| 11 | Phase 3 | FGR site and postgraduateLife | ||||||
| 12 | Phase 4 | Research centres, institutes and chairs | ||||||
General
Content
Integrations