| 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) | 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 the VI | 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 am 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.
| 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 degree 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. | 'Remove' UG programme pages when new UG degree pages go live, which in turn is best linked to then the feeder topic pages go live (see row 1 above) | See above We probably | 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:
Still waiting to see if the Foundation Certificate in Jazz is having one year off or being ended
| |
| 3 | 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 | 'Remove' PG programme pages when new PG programme pages go live | PG user research to identify the user requirements, especially their information needs | Needs that are so different that they can not be let by a topic or a programme page approach
| |
| 4 | ||||||||
| 5 | ||||||||
| 6 | ||||||||
| 7 | Implication of COO on f&s: Need page/space for outlines until COO is fully operational. | |||||||
| 8 | ||||||||
| 9 |
General
Content
Integrations