OER 2 Technical Requirements

Following the experiences of projects funded under the HEFCE / Academy / JISC Open Educational Resources Pilot Programme CETIS have made some minor revisions to the technical guidelines for the current OER 2 Programme. These guidelines reiterate and hopefully clarify the guidelines provided in the Programme Circular and presented at the Programme Start Up Meeting.

Resource Description

As with the OER Pilot Programme, the OER 2 Programme will not mandate the use of one single platform to disseminate resources and one single metadata application profile to describe content. However projects still need to ensure that content released through the programme can be found, used, analysed, aggregated and tagged. In order to facilitate this, content will have to be accompanied by some form of metadata. In this instance metadata doesn’t necessarily mean de jure standards, application profiles, formal structured records, cataloging rules, subject classifications, controlled vocabularies and web forms. Metadata can also take the form of tags added to resources in applications such as flickr and YouTube, time and date information automatically added by services such as slideshare, and author name, affiliation and other details added from user profiles when resources are uploaded. Consequently the OER 2 Programme only mandates the following “metadata”:

Programme tag – ukoer

Project tag – each project should devise a short tag for use in conjunction with the programme tag. e.g. projectname

Title – of the resource being described

Author / owner / contributor – Most systems, whether repositories, vles or applications such as SlideShare, YouTube, etc allow registered users to create a user profile detailing their name and other relevant details. When a user uploads a resource to such a system these details are usually associated with the resource.

Date – This is difficult to define in the context of open educational resources which have no formal publication date. Most applications are likely to record the date a resource is uploaded but it will also be important to record date of creation so users can judge the currency of a resource.

URL – Metadata must include a url that locates the resource being described. The system must assign each item a unique url.

Licence information – Creative Commons is the preferred licence for programme outputs. The cc:license element can be used to provide a URI for the licence chosen and the dc:rights element can be used to provide general textual information about copyrights, other IPR and licence. Embedding the license within the resource is also recommended where practicable. Projects may refer to the OER IPR Support Project for further guidance

Technical information such as file format, name and size may be added but is no longer mandatory.

The hash symbol # should be added to the programme and project tag for use on twitter. E.g. #ukoer for twitter, ukoer for blogs etc.

Projects are also encouraged to think about providing additional information that will help people to find and access resources. For example:

Language information – The language of the resource.

Subject classifications – Specific subject classifications vocabularies are not mandated for the OER Programme. However if a controlled vocabulary is required, projects are advised to use a vocabulary that is already being used by their subject and domain communities. It is not recommended that projects attempt to create new subject classification vocabularies.

Keywords – May be selected from controlled vocabularies or may be free text.

Additional Tags – Tags are similar to keywords. They may be entered by the creator / publisher of a resource and by users of the resource and they are normally free text. Many applications such as flickr, SlideShare and YouTube support the use of tags.

Comments – Are usually generated by users of a resource and may describe how that resource has been used, in what context and whether it’s use was successful or otherwise.

Descriptions – In contrast to comments, descriptions are usually generated by the creator/ publisher of a resource and tend to be more authoritative. Descriptions may provide a wide range of additional information about a resource including information on how it may be used or repurposed.

It’s also useful for projects to be aware that once OERs are released they can easily become separated from their metadata descriptions, if this information is recorded in an associated file. Consequently projects are encouraged to consider embedding relevant descriptive information within the open educational resource where practicable. For further discussion of this approach see Open Educational resources, metadata and self description.

Delivery Platforms

Projects should deposit their content in JorumOpen and in at least one other openly accessible system or application with the ability to produce RSS and / or Atom feeds; for example an open institutional repository, an international or subject area open repository, an institutional website or blog, or a Web 2.0 service.

The RSS / ATOM feed should list and describe the resources produced by the project, and should itself be easy to find. Where a project produces a large number or resources it may not be practical to include them all in one single feed. In such cases it may be necessary to create several feeds in order to list all the resources. If a number of feeds are required to represent the whole collection, the discovery of the complete set of feeds should be facilitated. A number of approaches to enable this are possible, e.g. by creating an OPML file and using multiple instances of the element in the HTML header, or simply listing all feeds in a human readable web page.

There are many other approaches that projects may choose to investigate and use to facilitate resource discovery including search engine optimisation, site maps, OAI-PMH or APIs for remote search (SRU, OpenSearch, ad hoc RESTful search). CETIS will provide further guidance on these approaches in due course.

Projects will be expected to report to JISC on resource use so it is highly recommended that if the chosen delivery platform has tracking functionality this should be switched on and monitored.

For an overview of the wide range of delivery platforms used by the OER Pilot Programme projects may find it useful to refer to the UKOER Technology Overview

Content Standards

The OER 2 Programme is expected to generate a wide range of content types so mandating specific content standards is impractical. However projects should consider using appropriate standards for sharing complex objects e.g. IMS Content Packaging, IMS Common Cartridge and IMS QTI for assessment items.

What We Hope To Learn

We have learned a great deal from the technical choices and experiences of the OER Pilot Projects but we still have much to learn about how to describe and distribute open educational resources most effectively on the open web. Consequently we strongly encourage projects to share their comments, queries, successes and frustrations with CETIS and with other OER 2 projects. CETIS OER Programme Support Officer R. John Robertson will be undertaking informal technical review calls with all OER 2 projects over the course of the programme. Feel free to comment here, or contact John with comments, queries and suggestions.

Open e-Textbook Use Case

This open e-textbook usecase was produced as a contribution to the ISO/IEC JTC1 SC36 Study Period on e-Textbooks by Phil Barker, R. John Robertson and myself. We’d be interested to know if this is an area that others are interested and whether anyone has any comments.

Scope

A teacher wants to collate open educational resources to create an open e-textbook

Description

A teacher collates a range of open educational resources from different sources with different Creative Commons licences and creates an open e-textbook.

The source content may include assessment items, video, images, sound, text. This content may contain embedded licence information (e.g. in the exif or id3 file information for images and audio respectively), or licence information included as images or text in the content, or associated licence information in lmetadata records linked to or packaged with the content.

Level of participant(s) addressed

Applies to all participants.

Description or list of the technologies used

A wide range of technologies may be used. These include repositories, content management systems, web 2.0 tools, content-authoring systems, virtual learning environments, course management systems, search engines, licence embedding or attribution tools.

Scenario Sequence

  • Determine topic, curricula, textbook scope, learner requirements
  • Search for stuff
  • Find stuff
  • Evaluate stuff
  • Check licence
  • Select stuff
  • Assemble collection of stuff
  • Edit stuff
  • Format e-textbook
  • Create e-textbook
  • Disseminate e-textbook
  • Revise textbook

Primary Actor(s) and Role(s)

Teacher (content editor/ assembler)

End goal of activity

Students are provided with an open e-textbook tailored to their requirements by their teacher.

Trigger(s) / Pre-condition(s)

The teacher must be able to find sufficient clearly licensed open educational resources that meet their requirements

What issues or challenges have been encountered during the implementation and use of the e-Textbooks?

  • Content interoperability
  • Display of different media formats
  • Handling interactive content
  • Clear licensing
  • Licence compatibility
  • Maintaining granular licence information

Who is using what is described in this use case?

Widely used by learners, other teachers, and learning technologists.

Additional Information Relevant to Understanding the Use Case

A similar use case could be constructed for an e-textbook which did not use OER. However, the licensing implications and rights management implications would be very different.

CETIS OER Technical Support Project Final Report

The CETIS OER Technical Support Project was funded by JISC from August 2009 – April 2010 to provide support to the JISC HEA Open Educational Resources Pilot Programme. The project’s Final Report is now available to download from the Publications page of the CETIS website.

Support provided to the programme included advising JISC on technical direction, setting technical guidelines for the programme, reviewing and advising on projects’ technical choices and liaising with other programme support elements, particularly JourmOpen. The project conducted technical review calls with all 29 projects and recorded the outcome of these interviews using the CETIS PROD directory. Over the duration of the programme CETIS facilitated a number of programme support events including a technical round table at the annual CETIS conference, and two 2nd Tuesday online seminars in addition to participating in all three JISC programme level events.

The outputs of the CETIS Technical Support Project have been synthesised and published in a series of posts on the CETIS blogs and pages on the CETIS wiki. These outputs were also disseminated through more formal channels including position papers, journal papers and presentations at a number of national and international conferences. The support project surfaced a number of technical issues worthy of further investigation these include; the use of RSS for depositing resources into repositories, technical approaches to aggregating resources and methods of tracking resources. These issues are now being taken forward through an additionally funded technical project.

An interesting tracking case study…

Earlier this afternoon my colleague Phil Barker led a fascinating Elluminate session exploring resource tracking issues for the JISC / HEA Open Educational Resources Programme. One approach to tracking Phil raised was the use of unique keys or tag combinations which are embedded in resources and then released into the wild. Googling for the unique key will then indicate where your resource has been reused and by whom, more or less.

Now I’m no authority on tracking technologies but this reminded me of a very interesting article I read in the Guardian today How Belle de Jour’s secret ally Googlewhacked the press. This explains how a blogger known as Derren used some astute guesswork and a unique key combination of two terms associated nowhere else on the web to monitor whether anyone else was coming close to guessing the identity of the anonymous call girl Belle de Jour.

At the OER Technical Roundtable at last week’s CETIS Conference one of the actions participants prioritiesd was case studies and examples of different approaches to tracking. I’m not entirely sure that the above is the kind of case study the projects had in mind but it’s a pretty good real world example never the less! Just thought I’d mention it….. ;-)

Phil’s slides from the Elluminate session are available on Slideshare and no doubt there will be blog posts to follow.