Jorum for Developers

Jorum has a range of technical interfaces to help you get content, metadata and data out of Jorum, and to help us pull your content and metadata into Jorum. This page is still under development; it gives an overview of what you can expect. For more detailed information please contact us at


Overview of Basic Technical Details

DSpace Repository

Jorum is a repository for open educational resources (OERs) built on the open source repository platform DSpace 4. Users deposit to Jorum through the standard DSpace deposit interface.


Metadata and Licensing

All of our OERs are openly licensed with Creative Commons licences and have Dublin Core metadata (with some extensions of our own) describing them.


Usage Data

We collect, store and make available data about views and downloads of our OERs. See our Reports for the user interface to this data- and see below under Jorum API for accessing it.


Access Management

Anyone in UK Higher or Further Education can deposit resources in Jorum by logging in using their institutional Shibboleth or OpenAthens account. For those who have resources that are suitable for UK HE and FE, but no institutional login account, we offer Trusted Depositor accounts.


Web Interface

We have our own custom-built user interface for searching and browsing Jorum’s resources and accessing reports on usage data on the Web. This is built on our own API with DSpace, ElasticSearch and SOLR pulled together, and uses Cottage Labs FacetView. The diagram below explains Jorum’s architecture (Click on the image to enlarge).


Jorum architecture diagram


Technical Interfaces

Pulling content, metadata and data out

We offer access to Jorum resources via:

  • OAI-PMH and RSS feeds to our collections. These allow you to pull out metadata about and links to our resources.
  • The Jorum API

Depositing content and metadata

We have bulk deposit options:

  • OAI-PMH ingest. We can pull in metadata and links from other repositories using their OAI-PMH feeds, as long as (a) the resources are Creative Commons licensed, with the licence URL in the dc.rights field; (b) you provide a link to the resource in the metadata and © you make your keywords or tags available in the dc.subject field. Users will be able to access your collection within Jorum under its own name, or find your resources through searching. Once they have found a resource from your collection, they click a link and end up in your repository.
  • SWORD deposit. We have implemented SWORD v2 as a deposit interface, which will enable those with content creation tools to offer a Deposit to Jorum feature. This allows files and their metadata to be deposited without going through the DSpace deposit user interface. More on this soon. Please contact us if you want to work with us on this:
  • Bulk deposit by spreadsheet. We have in the past offered bulk deposit via CSV / spreadsheet; this has not been updated yet for the new version of DSpace we are running on, but we are monitoring whether this will remain a requirement and are open to developing this further.
  • RSS ingest. We have in the past offered RSS feed ingest, but this is now deprecated as it proved unsuitable for repository deposit.




What is OAI-PMH and how does Jorum use them?

OAI-PMH (Open Archives Initiative Protocol for Metadata Harvesting) is “a low-barrier mechanism for repository interoperability”. Data Providers, such as Jorum, are repositories that expose structured metadata via OAI-PMH. Other services (Service Providers) can make OAI-PMH “service requests” to harvest that metadata. Service requests are defined by the OAI-PMH specification and allow Service Providers to retrieve information about the metadata held in a repository that has been made available by a Data Provider.

OAI-PMH has a concept of “sets”. Sets are groups of records that the Data Provider has decided to expose via OAI-PMH. In the case of Jorum these sets are mapped directly to the “collections” held in the Jorum repository. OAI-PMH has a concept of “sets”. Sets are groups of records that the Data Provider has decided to expose via OAI-PMH. In the case of Jorum these sets are mapped directly to the “collections” held in the Jorum repository. Please note that currently there is one collection / set that contains resources that are not openly licensed: “College Development Network (Resources Licensed to Colleges)”. These resources do not appear in Jorum, but are in the Re:Source repository supported by Jorum as one of our Jorum Powered partners. For each of these sets, metadata records describing the resources held in that set may be retrieved and processed by a Service Provider.

Service Provider Configuration

Further information on how to retrieve metadata records and specify date intervals can be found at the OAI-PMH website. If you have any questions then please contact us for any help or guidance.




Following basic REST principals but searched via Value:Key pairs in the querystring.

A basic userguide can be found here:

The first public version of the Jorum API was released in April 2014.