¿Cambiar a Español?
Yes
Work

Our new website: An update on progress

Article originally published by Rob Greig on the blog of the Royal Opera House, where I worked as a Digital Developer

Our new website: An update on progress
12 February 2012

Chief Technology Officer Rob Greig on our forthcoming new website

Since my last post, there has been a great deal of progress in developing our new and improved website. Like the rest of the team here, I was delighted with the feedback given to my last blog; it’s great to know that we’re on the right track with delivering many of the things you’re looking for.

The focus of the last month has been data, data and more data; we’ve been trying to find the best ways to display all the important information about our performances and productions in a way that makes sense to everyone using it.

A lot of the information you see on our website today has to be manually entered, meaning that we’re limited in how we can present the data, an increased likelihood of mistakes, and a lot of time spent updating for our team. This is also not one project, it's four; technology, the content, the ticket and e-commerce, and the repurposing of all the content from the old to the new.

Like all the work we do at the Royal Opera House it could not happen without the people who work behind the scenes, so I wanted to introduce you to the dedicated technical team who are making this all happen. We’ll look at the work of the content team in another blog.

The Royal Opera House development team © ROH 2012
The Royal Opera House development team © ROH 2012

Firstly they are the often unsung heroes, the development team of two developers and a manager. Jamie and his small team are building the site from the ground up. Working with reams of data, they’ve recently been building a new more integrated way to reserve a restaurant table - one of the consequences of which is that we won't be asking for a restaurant deposit on the new site. Other fundamental work includes keeping data open and accessible. This will, for example, impact the way we store and showcase our ever-popular production photography, which will be managed through Flickr.

The Royal Opera House IT team © ROH 2012
The Royal Opera House IT team © ROH 2012

Then there is the Technology team who is working behind the scenes with staff from all over the house to perform a major upgrade of the supporting systems and databases that hold the data and ultimately sell the tickets. Experienced and skilled techies though they are, they’re not your typical IT crowd - including a cellist, an actor, writer, dancer, and an ex-orchestra pit manager. Head of IT Chris and his team have to make sure the behind-the-scenes systems are safe, secure and responsive for both the website and the box office.

POP: the team building our ticketing system © ROH 2012
POP: the team building our ticketing system © ROH 2012

We also have a partner in all this; POP will be building the ticketing system and has taken on the formidable challenge of building an online sales system capable of handling our busiest periods without the need for a waiting room. They have a long history of working with arts venues in the UK, previously creating the system that sends you our emails as well as our iPhone ticketing app. They’re currently working on a new select-a-seat tool that will be simpler to use than the current incarnation and works on other devices that don’t support Flash. Their next task is to build single-click purchasing similar to Amazon’s.

After all these developments, I’m sure that your ultimate question is “When is it going to be launched?”, but I’m afraid we’re going to keep you guessing, for now at least. I can tell you that we start our first round of testing in the middle of March. We must get this right; there are always issues with complex new websites, and we want to be sure we give you the best possible experience when we go live.

Before you continue...

By clicking "Accept All", you agree to the storing of cookies on your device to enhance site navigation and analyze site usage.

Languages

¿Cambiar a Español?