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.
- FTP - sending JATS XML metadata plus any binary files as a zipped package (or unzipped if particular rules are followed)
- SWORD2 deposit - as per SWORD2 specification
- Publications Router API - a REST web service (Publications Router's JSON structure).
Note that we are open to supporting alternative formats and new mechanisms for receiving notifications from publishers and other sources so this list may expand in the future.
Institutions may receive the notifications directly into their repository or CRIS (if the vendor supports this) by any of these mechanisms:
- SWORD2 deposit - which allows Publications Router to push the notifications to those repositories that support this protocol (such as Eprints and DSpace)
- OAI-PMH - which enables repositories to pull the notifications from Publications Router via an exposed end-point (URL)
- Publications Router API - which enables repositories or CRISs to pull notifications via a REST web service.
In order to use Publications Router both publishers and institutions must have completed the sign-up process which results in creation of a Publications Router account. This is used to configure and administer Publications Router settings that are necessary for inter-connection.
Matching of notifications to an institutional repository is a key function of the Publications Router. This is done using a set of matching criteria that each participating institution maintains via their administration screen. Each notification is compared with these criteria and those that match are flagged for routing to that institution's repository. Criteria may include any of the following:
- Institution name variants (reflecting different ways that an institution is known)
- Email or web domain names associated with the institution
- Postcodes of an institution's various premises
- Grant numbers
- ORCIDs of authors
- Email addresses of authors.
Matched notifications are stored for 90 days in Publications Router. This gives repositories and CRISs that use either of the "pull" mechanisms (OAI-PMH or Router's API) ample time to obtain the notifications. It also allows Institutions to view the metadata of those notifications via their administration screen.
Further information on how to set-up and configure Publications Router is provided in the following sections for institutions and publishers.