Skip to main content

First demo of the new University web site

The project to develop a Drupal content management system for the University's web site reached a significant milestone last Thursday, when the project board were given a demo of the first web site to be migrated to the new platform. It looked good.  The display automatically adjusts to the size of the screen (responsive design) and the navigation has been redesigned to be simpler and to accommodate this adaptive behaviour. 

For editors, the system is much easier to use.  You can log in from any page of the website and start editing it then and there - if you have the right permissions.  The content editor is both more flexible and more straightforward.  The first users are describing the interface as a joy to use (and this is before the team have finished tidying it up).

Behind the scenes, this was a close-run demo.  The content was migrated only the day before and the editors were working frantically to tidy it up on the morning before the board meeting.  We would all have preferred to have reached that stage several weeks earlier.  Unfortunately we were delayed, in part by unexpected infrastructure problems.  So I have to thank the team for working flat out to get everything back on track.

We were helped by our automated content migration tools.  With these, we can export pages from the old CMS and load them into the new one such that only a small amount of tidying up is needed.  The process of preparing the demo shows that these tools worked smoothly, which bodes well for the large amount of content migration we face in the coming year.


Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.

This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…