Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Proposed orderProject phaseContent area

Current location(s)

Proposed location(s)

 

Delivery approach (to move from current to proposed)

Implications

Dependencies

Risks (or in risk register)

1Phase 2Topics (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

  1. 'Remove' subject pages from school/faculty sites when topic pages go live; or
  2. 'Move' the asset for subject pages from school/faculty sites to VI and then 'remove' subject pages from school/faculty sites when topic pages go live.

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

  1. Remap Future Students and VI to the new topic pages in the same "batches" as we plan to use for go-live on Future Students; or
  2. Work in moving old content to a new location, but it would allow us to bundle up all the batches on Future Students to one release for Victoria International.

 

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.

2Phase 2Undergraduate degree pagesUG 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 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.

'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

This approach relies on the new programme page containing the "rules" for all majors before it can go live, even if those majors are taught by another faculty to that which "administers" the programme in question. For example, we can only enable the new BA programme page when it covers all 40 majors (plus 6 listed minors and "hanger on" subjects), including the 8 taught by other faculties.


 

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

 

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.
3Phase 2Postgraduate programme pagesPG 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.

'Remove' PG programme pages when new PG programme pages go live

Might be sensible to leave all PhD and Doctoral programmes until we do FGR?

Exclude PhD/doctoral/higher degrees, which will be handled in Phase 3PG 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

 

4Phase 2Postgraduate informationInformation, forms and resources for 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 TBDRemove all the PG student information and resources from 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. The experience for PG students, an important customer group, remains suboptimal.
5Phase 2Research informationInformation 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 TBDRemove all the research information from 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.

 

 These will wait a long time and some are already long overdue for attention
6Phase 2School and faculty sitesSchool and faculty information exist on faculty sites and school sites.Homesite, exact location TBDDevelop new content for the new sites. Any content or media that is "reused" will be loaded again in the new location. 

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. 

7Phase 3FGR site and postgraduateLife      
8Phase 4Research centres, institutes and chairs