Any views expressed within media held on this service are those of the contributors, should not be taken as approved or endorsed by the University, and do not necessarily reflect the views of the University in respect of any particular issue.

Author: Duncan MacGruer

I’m currently in the fifth week of my eight week internship with the UWP tech team. So far it’s been a really enjoyable experience.

Due to high demand for the service, on 5 May 2015 we’re going to run a special website support clinic dedicated to assisting people with their EdWeb migration preparation tasks.

On Monday 23 February, I was invited to come along to the Innovative Learning Week’s “Smart Data Hack”, hosted by the School of Informatics, to talk about prototyping.

In last month’s support clinic, we conducted a ‘QA‘ assessment: a review of a site that is due to go live, to ensure it meets the best practices of the University website.

Last week we brought together representatives of the entire EdWeb project team to review the Polopoly to EdWeb migration process, with a goal to make it as easy as possible for University web editors to prepare for, and get information on, the progress of the migration of their site.

On 23 October, I attended a workshop session intended to introduce ideas for generating video subtitles, in order to enhance the availability and accessibility of our video training.

On 17 October, I attended the “Office 365 Collaboration Tools Event for Further and Higher Education” conference in Edinburgh, which sought to bring together experiences of these services in the further and higher education sector.

This month in our support clinic we’ve been considering digital strategy: firstly, developing one; then promoting adherence to it, once in place.

This months’ Web Publishing Community saw our latest update on the Drupal project (EdWeb), an update on Google Analytics events tracking, and a presentation from Andy Todd about his experiences of creating training videos for the IS Skills team.

We’ve recently been considering the need to provide a distinct name for the CMS we’re developing to bring clarity to what we are providing, and future project communication.

css.php

Report this page

To report inappropriate content on this page, please use the form below. Upon receiving your report, we will be in touch as per the Take Down Policy of the service.

Please note that personal data collected through this form is used and stored for the purposes of processing this report and communication with you.

If you are unable to report a concern about content via this form please contact the Service Owner.

Please enter an email address you wish to be contacted on. Please describe the unacceptable content in sufficient detail to allow us to locate it, and why you consider it to be unacceptable.
By submitting this report, you accept that it is accurate and that fraudulent or nuisance complaints may result in action by the University.

  Cancel