Another approach taken in UKOER for the use management and sharing of OER management has been to use mainstream web publishing tools such as WordPress, Content Management Systems, and ‘simple’ websites (‘simple’ being a website created and managed without using a CMS ). One of the challenges this approach faces is that such tools are often not designed to export resources and a number of the projects have had some challenges when considering how to represent their OER(s) within JorumOpen.

Drupal

• TRUE
• OpenSpace
  • OpenSpace created a virtual learning studio for collaborative creative script writing and storyboarding
  • Explored the integration of Kaltura with Drupal
  • the OER is not only the environment but also a example of it’s use (using a example (real) course with student work)
• Phorus

Plone

• OTTER
  • OTTER have had problems exporting metadata they had created within Plone

Websites

• numbat
  • XHTML and PHP based search

WordPress

It is worth noting in passing that many projects have extensively used blogs throughout the programme for communication, discussion and dissemination. This has provided a valuable way to engage and stay up to date with projects but that usage is a different topic entirely.

• ChemistryFM
  • WordPress used as the primary ‘repository’ for content and publishing platform. Courses broken down into into one sub-topic per post comprising of embedded videos and related supporting resources.
  • The posts are tagged with the appropriate course code – this allows the courses to be put together through the blog interface.
  • can export resources via OAI-ORE for import to other repositories
• C-Change
  • is investigating the use of wordpress as a possible local publishing tool for their members of their consortium who need (especially in the longer term) a way to publish OERs.