Jisc Publications Router

Introduction

Jisc Publications Router aims to streamline the process of depositing journal articles in an institutional repository. As described by Jisc:

"Jisc Publications Router is a messaging system that receives notifications about article publications from publishers and other sources (e.g. Europe PMC) and routes these using a matching algorithm to particular institutional repositories. At its simplest, a notification is simply a metadata package providing details of an article that has either been accepted for publication or has been published. The notification may also include the article text either embedded in the metadata or in associated binary files, for example PDF or WORD documents and graphics files." (see https://pubrouter.jisc.ac.uk/about/resources/)

PubRouter and Eprints

Jisc PubRouter is able to deposit directly into Eprints, either a manage deposits queue or directly into a review queue, using its in-built SWORD interface.

Two modes of integration are available:

• Basic connection to a "vanilla" Eprints repository which requires minimial (if any) configuration on the Eprints side. This results in deposits with a basic set of meta-data and some limitations on populating particular fields, such as an attached document's License terms (although in these cases the information is available in the Additional Information field).

• Jisc PubRouter RIOXXplus Connector plugin for Eprints repositories that have the RIOXX2 plugin installed. This will populate the additional RIOXX fields with meta-data and will also populate other fields that the basic connection has to work-around. You will need to install this plugin from Eprints Bazaar and configure it - see further details below.

To take advantage of PubRouter -- Eprints integration you will need to establish a PubRouter account. Details on how to do this may be found on the PubRouter website: https://pubrouter.jisc.ac.uk/.

Jisc PubRouter RIOXXplus Connector Plugin

The Jisc PubRouter RIOXXplus Connector plugin, available from the Bazaar, receives input from Jisc PubRouter in the form of XML to describe an Article for automatic deposit in the repository. The plugin is designed to work with Eprints repositories that also have the RIOXX2 plugin installed. The plugin will create an Eprints record containing the received meta-data values and also the article PDF or other files where these are available.

The PubRouter data may also contain links to documents that are either hosted on the PubRouter or elsewhere. Where possible, documents are downloaded from the specified links and added to the newly created EPrint record. Documents hosted on the PubRouter are only accessible with the use of an API key that the repository must provide when requesting the document.

In order to receive data from PubRouter you will need an account (see previous section). You will also need to update the plugin's configuration file - details below.

For Developers

The Jisc PubRouter RIOXXplus Connector plugin installs a configuration file at the local archive level, named: zzz_pubrouter_rioxx_importer.pl.

This needs to be updated with your PubRouter API Key which will be available once you have a PubRouter account. This is required so that the plugin can retrieve article PDFs and related files for attachment to the Eprint record.

This API key is stored here:

 #PubRouter API key for importing document via URL supplied by PubRouter
 $c->{plugins}{"Import::PubRouter"}{params}{api_key} = "ENTER PUBROUTER API KEY HERE";

The configuration file also sets a flag that enables the repository to download and import documents from the Web, which the import plugin needs if documents are to be added to the imported records.

 #allow documents to be imported via URL
 $c->{enable_web_imports} = 1;

Also, it ensures that the Atom Export plugin, required for generating SWORD deposit responses, has not been disabled.

 $c->{plugins}->{"Export::Atom"}->{params}->{disable} = 0;

A new mapping of license values to URLs is also provided for the purpose of autocompleting RIOXX fields where the RIOXX2 plugin is installed.