What lessons have we learned?

Posted on November 1st, 2012 by Joss Winn
Bebop has gone remarkably smoothly – not all projects do – and I’m pleased to say that we’ve achieved everything we set out to do. We did learn things along the way and things we already knew were reconfirmed:

  • WordPress/BuddyPress is a viable and versatile platform for managing staff profiles at a university and brings the benefits of mandating staff to engage with a popular social media platform if they are to update and maintain their professional profile.
  • WordPress has a very active and open community of users and developers and consequently values contributions from HEIs. It is a versatile technology that can bootstrap different types of projects where content management is key. We knew this before the project started, but through releasing a plugin and responding to its use by different people, the benefits of contributing to such a community have been reaffirmed. For developers new to writing open source software, WordPress offers a mature community with a very low barrier-to-entry.
  • When working with third-party services, each API is different and takes time to learn. Maintaining compatibility with changes to third-party APIs is a problem for the sustainability of the software. It’s important that there is institutional value to integrating such services with your software so that there is the justification for maintaining compatibility.
  • Identify an expert partner and cost them into your project for evaluation purposes. It doesn’t matter where in the world they live. Expert code review improves staff skills and the quality of code, benefitting all involved.
  • OERs are teaching and learning materials that areĀ  licensed for re-use. Often, the licensing information is not provided as part of the API or syndication feed. Bebop overcomes this by providing a curatorial tool that allow the user to select specific resources for re-publication. There is less ambiguity about whether a resource is avaialable for re-use if the user has selected to include it in their profile.
  • There are a limited number of platforms that are widely used for publishing OERs in the UK. We were surprised that Jorum, the main national repository for OERs, does not yet have a method for extracting information about the resources deposited by a specific individual. The benefits of publishing OERs have often been discussed in terms of institutional benefits, but in order to provide individual benefits and therefore incentives, work on user profiles and OER use seems key.


Leave a Reply