Maria is the digital data analyst and content editor for the digital communications team. From Newcastle originally, Maria has lived in Dundee for the last five years while completing her degree in English and working in marketing for small, start-up businesses. Maria is usually found analysing Google Analytics and the results of usability testing.

View the new accommodation pages

As part of the external website programme, just before Christmas digicomms updated a large part of the Study at St Andrews section of the website. This involved restructuring information for prospective students.

A significant portion of the team’s time was devoted to the redesign of the accommodation webpages. Previously these pages were held in T4v7, so they were rebuilt in T4v8. The structure of the site was reimagined, the content was rewritten and the pages were given a new lease of life.

So what’s changed?

Continue reading “View the new accommodation pages”

Study at St Andrews: usability results

As part of the external website project, we are reconfiguring the current Study at St Andrews section to improve the prospective student’s experience.

Digicomms recently conducted testing specifically to determine the usability of the title for the ‘Study at St Andrews’ section of the University’s website. For this, the following three titles were tested:

  • Study at St Andrews (current name of section)
  • Prospective students
  • Why choose St Andrews?

Continue reading “Study at St Andrews: usability results”

Usability testing around the University

The digital communications team has been conducting usability testing since 2015. Usability testing allows us to evaluate the design of a webpage, or more specifically, a particular process such as signing up for a visiting day.

Digicomms is keen for other units and departments within the University to consider conducting usability testing on their webpages. This post looks at the process for conducting usability testing in another department.

Find out more: What is usability testing and why do we do it?

Continue reading “Usability testing around the University”

What is Google Data Studio?

Over the next few weeks I will be updating my existing training session: Google Analytics: creating a dashboard. Recently, Google updated Google Analytics and this update saw the removal of the humble ‘add to dashboard’ button. This subtle change meant that the majority of the training needed to be re-written.

Google has released Google Data Studio as an alternative way to visualise data, so I looked into it and this was definitely the direction my training needed to go. The new tool, which is currently beta, is more user friendly, offers more features and is likely to revolutionise how data is shared in organisations. Continue reading “What is Google Data Studio?”

An update on the 2018 digital prospectus

Last month the digital communications team were busy launching the new site structure, a big milestone in our external website project. Now that’s out of the way, we have more time to focus on our business as usual work, and this means ensuring all of the 2018-entry postgraduate taught and undergraduate course webpages are ready for September 2018.

New methods

2017 was the first year that the web publishing schedule for postgraduate programmes aligned with Publications, which meant that all drafts of the webpages were sent out at the same time as the draft print prospectus for each subject. This was done in an effort to make the proofing process easier for Schools, as all feedback could be sent back to Publications in one go. Undergraduate pages were still sent out separately, but digicomms hope that, in the future, these can also be sent out with print prospectus information.

Uploading

Once digicomms receives all the Word documents back from Schools, the next step is to upload the content to T4v8.

When each course is uploaded, the content team checks the page against specially written acceptance criteria for the undergraduate and postgraduate pages.

The first phase is to upload the postgraduate pages. Once they have all been uploaded, there will be a final overall QA in which the content team will read over for typos, test all links, and check each page against the acceptance criteria and the print prospectus.

Once the postgraduate pages have been signed off, we will begin uploading the undergraduate pages. The process will be the same for UG as it is for PGT, although, due to UG pages having more subpages, and more content on each page, we expect this will take longer.

The schedule

The deadline for Schools to return the postgraduate taught pages was 24 May, and the deadline for undergraduate page returns was 7 July.

We aim to have both undergraduate and postgraduate course pages live on the University website by the 1 September 2017.

Once the new 2018 pages are live, both the 2017 postgraduate and undergraduate pages will move into the archive.

Launching the new site structure

On Thursday 6 July, the digital communications team will be changing the structure of the University’s website. All academic information that currently resides under Study at St Andrews will be moved from there into the Subjects section.

The digital communications team will be migrating Entry requirements, Study options, Non-degree programmes and Postgraduate taught courses.

The new site structure for the Subjects section will go live on Thursday 6 July 2017.


Continue reading “Launching the new site structure”

Prospective student information: usability testing and results

As part of the external website project we are retiring the Study at St Andrews section of the website and moving its content into either Subjects or Prospective students. Certain information will now live under Subjects, including:

  • Study options
  • Entry requirements
  • Non-degree courses

Last week we conducted a control usability test which asked users to find information in the pages listed above. The purpose behind this test was to see how users currently found this information within Study. Continue reading “Prospective student information: usability testing and results”

Google Analytics training: an overview

Recently, the digital communications team launched the digital visa, a programme of training sessions which enables staff to feel competent working on digital communications projects. One of the courses within the visa is Google Analytics: creating a dashboard – this post outlines in more detail what the Google Analytics training session covers.

The session

By the end of every training session, each participant walks away with their own Google Analytics dashboard. A dashboard allows users to quickly access relevant data within Google Analytics.

Creating a dashboard means collating specific reports in one place, with the main purpose of having all the most important and most frequently used reports at hand. The training session covers five reports:

  1. Who visits your site? (Location report)
  2. How do users visit your site? (Mobile device report)
  3. How many pageviews does your site receive? (Pageviews report)
  4. How do users reach your site? (Traffic source report)
  5. Number of sessions from social media. (Social media report)

With each report, participants are shown what the report looks like in the dashboard, what the report can tell you about a site, and how to add the report to the dashboard.  

Once a report has been added, participants also have the option of editing the style of each widget in the dashboard so they present the data in a suitable manner. For example, instead of showing the mobile device report as a table, participants are shown how to change it to a pie chart.

Alongside creating a dashboard, participants are introduced to key terminology associated with the tool. For example:

  • bounce rate
  • entrance
  • exit rate
  • organic
  • pageview
  • referral
  • session
  • unique pageviews.

Additional reports

There is time allocated in the training session to look at any additional reports that users would like to include but have not been covered in the session. For example, in the first training session, one participant asked if it were possible to monitor PDF downloads. The whole class was shown how to implement this report in the dashboard.

Resources

After the training session, each participant is emailed a training pack which includes information about the reports that were covered in the lesson, along with videos showing the steps involved if additional reports need to be added.

If you’re interested in signing up for Google Analytics: creating a dashboard or any of the other courses in the digital visa, please email digitalcommunications@st-andrews.ac.uk.

Updating the undergraduate pages with HEFCE information

A couple of weeks ago, the content team spent some time going through a ‘Information for Students’ guide from the Quality Assurance Agency for Higher Education, but we call it the HEFCE guide (HEFCE stands for Higher Education Funding Council for England, for whom the guide was developed). The guide aims to help universities present good quality information to prospective students. 

Digicomms are using this guide to help shape the new 2018 undergraduate pages – this blog post explains what the HEFCE guide is and looks at the information that the undergraduate pages are missing.

The guide

Including the right information is essential in terms of consumer protection legislation, and also for user experience. The guide states which information HEFCE thinks universities should be providing and when it should be provided – it also includes examples of how this information should be displayed. Digicomms worked through the document and made a note of all of the information that St Andrews does not currently include on its undergraduate pages.

It is important to note that some of the recommended information does not apply to the University of St Andrews because the HEFCE guide is a document written with English universities in mind.

However, digicomms feel it is important to align the University’s content with industry standards in England, as many prospective students will compare St Andrews with English universities. In addition, similar guidelines could be implemented or suggested in the future in Scotland.

What we don’t include

Overall, we already included a lot of the recommended information. However, we were missing a few bits:

  • start and end date of undergraduate courses
  • geographic location of study
  • timetable information
  • how to apply through other routes
  • accreditation of prior learning
  • an explanation of how the academic year is organised
  • a copy of rules and regulations
  • optional modules and how those modules are chosen
  • teaching and learning information
  • assessment and progression information.

Some information on this list is easier to implement than others and digicomms have already drafted text for many of those items listed. However, with things like optional module information, this is where it gets a little more complicated.

This complication arises due to the fact that St Andrews is a Scottish university, where students have a far wider choice of modules at sub-honours. If every optional module was listed, there would be up to a thousand modules on the page. Furthermore, it’s difficult to state how these modules are chosen, because availability depends on a range of factors including staff availability, interest in modules and staff research interest.

Next steps

There isn’t a ‘one-size fits all’ for this information; we need to ensure that the right people are involved with what and how much needs to be said regarding academic progression.

To date, the digicomms team have taken an undergraduate programme and added the information that was missing. The next steps for the team will be to sign off the new content, which can then be added to the new 2018 undergraduate pages.

Common content mistakes and how to fix them

Part of the work done by members of digicomms is ensure all content on the University’s website meets digital standards. In particular, any text on the website or in print materials must meet the University’s house style. Here are some of the most common mistakes found when the team check over content. Continue reading “Common content mistakes and how to fix them”