Page tree
Skip to end of metadata
Go to start of metadata
ObjectivesKey results
Keep our critical frameworks up-to-date
  1. Complete upgrade of key frameworks including Ruby and Rails to supported versions by end of Q3 2019.
  2. Identify all frameworks and have an actionable plan for ongoing updates by end of Q4 2019. Aim to stay within 1 minor version of latest.

Transition of templates

  1. Transition Guides and Announcements by end of Q4 2019.
  2. Transition remaining Content Types, have corresponding Lens templates available, and programatically migrate content where possible, at a rate of 1.5 per quarter.
Improve our outward communication
  1. Remove out of date, incorrect, confusing messages by middle of Q3 2019
  2. Establish our communications strategy by end of Q3 2019
  3. Communicate our communications strategy at start of Q4 2019
Transition of content
  1. Remove content which is no longer needed from OpenCms by end of 2019:
    1. Use Master organisation list to indicate areas which are fully or partially transitioned and flag up where there are issues by end of Q3 2019
    2. Establish with Computing Services any grey areas around what is ours and what is theirs by end of Q3 2019
    3. Make a note of important information that cannot be currently transitioned by end of Q3 2019
    4. Delete/archive content by end of 2019
  2. Remove static content which is no longer needed from 'W' drive by end of Q2 2020
  3. Guidance to be written or updated for templates by the end of Q3 (in line with delivery of dev changes to templates) (Content)
  4. As each guide is written we should notify x numbers of content authors/Typecase users of changes
  5. Set up content clinics around templates - one per month
Improve accessibility standards across the website, frontend and backend
  1. Obtain an accessibility accreditation from an external organisation by end of Q1 2020
  2. We have trained x% of publishers on accessibility literacy by end of 2019

Reduce technical debt by rolling out pinned item search to all Content Types using Pinned Item Sections

  1. Migrate all pinned items sections to use search by end of Q3 2019
  2. Investigate suitability of the interface for other related item sections (e.g. events sections) by end of 2019

Make search, filter and export available to admins and editors through the Typecase interface to assist in content management

  1. Make content filters available to Digital team by end of Q3 2019
    1. Use SQL queries from Pinned Item Search to provide additional filtering options (e.g. by ContentType) by middle of Q3 2019
    2. Combine filters and query to enhance refinement of search results (e.g. by ContentType and Organisation containing the word "research") by end of Q3 2019
    3. Filter by relevant dates (e.g. last edited) or status (e.g. unpublished) by end of Q1 2020
  2. Reduce requests for dev time to provide basic management information by end of Q1 2020
    1. Ability to export the results of filtered searches to CSV or other suitable format by end of Q4 2019
    2. A technical information view of content items that shows the kind of information about relations that cause errors on delete e.g. (“is this page pinned to other pages and, if so, which ones?”)

Review process for developing new Content Types

  1. Investigate what would be involved in creating new Containers before creating the final Content Type by end of Q3 2019
  2. If this is a viable process (possibly with the use of dummy Content Types to attach them to):
    1. Document new process with plans to implement it written and agreed by middle of Q4 2019
    2. Identify Containers which will be required in several Content Types and model them with all Content Types in mind by end of Q4 2019
Enable users to request redirects and deletion in the Typecase interface
  1. Make use of existing information in Typecase to streamline the deletion request process by end of Q4 2019
    1. Implement buttons (as for Unpublish) which send standard information to the supporter and flag urgency by end of Q3 2019
    2. Develop a workflow to enable the supporter to batch process requests by end of Q4 2019
  2. Make use of existing information in Typecase to request a redirect by end of Q4 2019
    1. Use JS to identify a title change (or subtype if relevant) and give user option to request a redirect by end of Q3 2019
    2. Develop a workflow to enable the supporter to batch process requests. This should probably include generating config code to make the process as simple as possible by end of Q4 2019
Introduce Video Standards across the University
  1. Have a set of standards drafted and approved by Marketing Managers by the end of Q3 2019
  2. Present standards to the video working group
  3. Create an asset file for video (idents/fonts/logos) by the end of Q4 2019
  4. Put on the website after they have been signed off Q3
Understand prospective applicants and analyse/validate their behaviour
  1. Validate the international student user journeys with real users by the end of Q3 2019
  2. Share results with stakeholders and explain in a workshop to Marketing Managers and Faculty web editors how to use them during Q4 2019
Complete Professional Services transition
  1. Audit OpenCMS and review links to understand scope
  2. By the end of October 2019, transition all possible content from OpenCMS to Typecase
  • No labels