Posts Tagged ‘products’

BBC Online Strategy

Posted on April 14th, 2011 by Alex Bilbie

In February 2010, BBC Online sumbitted it’s response to the BBC Strategy (read: budget) Review, announced the summer before.

Along with committing to reducing it’s budget by 25% by 2013, they’ve committed to halving the number of top-level directories# (i.e. anything that falls after http://bbc.co.uk/, such as /eastenders or /drwho). The BBC currently has over 400# of these top-level directories (not including redirects) and by the end of this year, 172# will be shut down with their content moved to other areas of the site or archived offline.

The new online strategy focuses on doing “fewer things better” and they plan on grouping online content into one of ten categories:

Noticeable changes will include programmes no longer having their own top-level directory, for example Eastenders will move from http://bbc.co.uk/eastenders to http://www.bbc.co.uk/programmes/b006m86d. Likewise http://bbc.co.uk/cbeebies and http://bbc.co.uk/cbbc will probably become http://bbc.co.uk/children which will then link off to CBBC/CBeebies and teaching material such as Bitesize from the Knowledge and Learning product.

There’s already been some lively discussion on the issues around deleting and archiving BBC websites facing removal that kicked off with an initial post from Adactio blogger Jeremy Keith. He suggested that the BBC’s plans to halve its top level directories were cultural vandalism. The tenor of the criticism was the same – that the BBC is failing in its duty to preserve a record of its online past. Some sites, like http://www.bbc.co.uk/ww2peopleswar/ which is a collection of 47,000 memories and 15,000 image created by people who lived through World War 2, has been debated heavily of something that should be preserved regardless of it’s age or irrelevance to the BBC’s new strategy simply because of it’s historical and cultural value to people around the world.

This massive re-organisation that BBC Online are currently undertaking is very similar to our Linking You project; as we have discovered so far, higher education institution’s websites (including our own) have also over the years become monolithic beasts. I think for the BBC, with the huge success of iPlayer and the huge increase in second screen viewing (e.g. chatting to your friends on Facebook whilst watching TV) has made the BBC realise that they need to wake up a bit and envelop themselves in the digital age. This quote below by Erik Huggers (director of BBC Future Media and Technology) particularly emphasises the point:

“The BBC’s online strategy has, for many years, been to play a supporting role to our broadcast output. Programme first, website later. This is not the best way to deliver our public purposes in a digital age.” #

Likewise universities are slowly realising that their primary audiences (i.e. students) aren’t living in a world of paper handouts and prospectuses any more; they’re connected 24/7 and want real time, personalised content. In age of increased tuition fees, potential students are going to be more interested in HE websites that suggest courses to them based on the things they’ve “liked” on Facebook and email you a personalised prospectus, versus those institutions that ask for their address so they can send them a massive document in the post a fortnight later.

The recent redesign of University of Lincoln’s homepage has already started the process of culling unnecessary links and the grouping of content into, not products, but areas of interest:

In terms of a URI model this could easily convert into:

/home
/undergraduate
/postgraduate
/business
/schools (or /departments)
/information

and maybe a few others such as:

/contact
/news
/current_students

From this BBC debate I think the thing that we’ve got to consider as we develop a model for HE websites is that we are going to have to make sacrifices because physical value does not necessarily represent value on the web (e.g. a University may stand by it’s vice chancellor’s vision but that doesn’t mean it is necessarily worth being a top-level directory on a HE website at /vc_message). Also we need to work out exactly what elements a university is made up such as courses, faculties, accommodation information and then try to fit it into a group of core categories (similar to the BBC’s “online products”).

Aims, Objectives and Final Outputs of the project

Posted on February 16th, 2011 by Joss Winn

Ready! Steady! Go!! Linking You is now up and running. This and the next few posts constitute our project plan and is meant to be an updated, easy to read version of our original project bid. Here, I’d like to introduce you to our objectives for this project and make clear what we intend to do over the next four months.

Like most other HEIs, Lincoln’s web presence has grown ‘organically’ over the years, using a range of authoring and content management technologies to satisfy long-term business requirements while meeting the short-term demands of staff and students. We recognise the value of our .ac.uk domain as an integral part of our ‘Learning Landscape’ and, building on recent innovations in our Online Services Team, intend to re-evaluate the overall underlying architecture of our websites with a range of stakeholders and engage with others in the sector around the structure, persistence and use of the open data we publish on the web. Some preliminary work has already been undertaken in this area and we intend to use this opportunity to consolidate what we’ve learned as well as inform our own work through a series of wider consultations and engagement with the JISC community.

The context

The University of Lincoln recently led the HEFCE-funded Learning Landscapes project which looked closely at the design and use of space for research, teaching and learning across several universities, including our own. An outcome of that project was the design of a tool to help investigate the spatial criteria that are encompassed in three fundamental qualities of good design. These are efficiency, effectiveness and expression. The project clearly recognised the role of technology in creating an ‘edgeless university‘ and the use of the web as integral to the learning landscape of the university. Just as the physical space can benefit from a re-evaluation of its efficiency, effectiveness and expression, so can the virtual space and in doing so, we think that the structure, persistence and openness of our online domain should be valued in a similar way to our physical assets.

More recently, we have attempted to address our virtual learning landscape through investigations into more effective and efficient use of space-time data. In the JISC-funded Total ReCal project, we are exposing space-time data in an open, standardised format that can then be queried and aggregated by a student-centred calendaring service. In Total ReCal, each event is given a unique, arbitrary, non-repeatable identifier which serves to identify the event in the future regardless of any changes to the underlying data architecture. In the Jerome project, we are also assigning similar identifiers to every unique work and copy of a work, allowing those resources to be reliably referenced.

We recognise that identifiers and URI structure play a role in expressing a well-designed, efficient and effective learning landscape. Well constructed, they can act as navigational and spatial signs to users, as can be seen from the syntax used on our WordPress CMS: e.g. http://totalrecal.blogs.lincoln.ac.uk/2010/10/18/how-we-make-things-faster/ Through the use of well-constructed URIs, a mental image of the virtual space can be easily built, allowing students and staff (and developers!) to understand and use their learning landscape more easily and effectively.

The problem(s)

However, not all of our existing web pages use such ‘cool URIs‘ and we are now having to cope with around 600 sub-domains using a variety of URI syntaxes. There is currently no policy on the management of domains, only an ad hoc agreement between departments. Many sub-domains are misnamed or occupy valuable name spaces. Clearly, resources at the sub-domain and domain level need to be administered at an institutional level under a recognised system of governance. As technology advances, platforms and addressing systems are becoming ever more numerous and complex. Operational management of URIs, identifiers and associated addressing systems has proved very difficult without an authorised institutional mapping system. Ideally, this mapping system should conform to agreed rules which will benefit core practices and users.

Currently, we have a number of publishing systems. For example, our corporate pages are still managed ad-hoc using FrontPage, we use Sharepoint for our Portal, we have an EPrints research repository, a Multi-Site installation of WordPress (with over 300 sites), a Mahara e-Portfolio system and our HIP Library catalogue. We also have our own URI shortening service at http://lncn.eu. Each of these systems uses its own URI syntax, which while generally consistent within the service, are very dissimilar when taking the institution as a whole.

When a department changes its name or moves to another faculty, traffic from the root of the old site is redirected to the new root on the server. When pages move or change they are redirected using META tags. However, this is only where it is deemed essential. Otherwise there would be too many to manage. A redirect system is in place, so that clicking a course on the UCAS site, or typing the UCAS code after our main URI, will send the visitor to the course page. i.e. http://www.lincoln.ac.uk/B343 goes to BSc (Hons) Acupuncture. Furthermore, we own a number of unique domains, such as http://undergraduatelincoln.com and http://studyatlincoln.com

Such is the extent of the problem. Clearly this ad hoc approach is neither desirable nor sustainable and is increasingly at odds with more recent work to provide personalised access to our online services through open APIs (Total ReCal & Jerome) and the benefits we have seen from our work on JISCPress. (The JISCPress project allowed us to evaluate WordPress as a source of structured open data and its integration with third-party services such as Talis platform and Open Calais). We are currently preparing to undertake a full review of our institutional web sites and the work for Linking You will help us raise awareness about the value of our identifiers and developing a persistent data model.

We feel strongly that by considering this project on identifiers within the context of the university’s leadership and experience of learning landscapes in higher education, we are able to offer an innovative and broadly informed approach to thinking about spatiality and the role of identifiers in the research, teaching and learning culture of higher education. We are aware of the existing work done in this area within the university sector, as well as discussions elsewhere1 and will ensure that our work is informed by current best practice.

What will we actually deliver over the next four months?

  1. A ‘blue sky’ technical consultation on the use of virtual space and the role of identifiers, based on what we now know.
  2. A data model based on the outcome of this consultation. This is a technical representation of our ideal, future virtual learning landscape.
  3. A poster-sized visual representation of this data model for use in consultations with a wider range of stakeholders. ‘The role of identifiers in the Learning Landscape.’ This should make sense of identifiers to non-technical staff and students.
  4. A prototype of the agreed data model, including an explicit URI syntax and persistent structured data outputs, with use case examples. We’re not sure if this is going to be a real prototype website or a series of diagrams/models.
  5. Use case scenarios, including comparative studies of two other HEIs and documentation on the use and re-use of Lincoln’s data. For us, this is the business case for why we move forward after the project.
  6. Participation in a relevant workshop/conference so that we can talk face-to-face with other institutions about what we’ve learned.

That’s it for our introduction. Now on to a post about the benefits of undertaking this project.

  1. i.e. http://patterns.dataincubator.org/book/shared-keys.html & http://www.bbc.co.uk/blogs/radiolabs/2008/06/the_simple_joys_of_webscale_id.shtml & http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml []