Interoperability

Advertisement:

We are continually working to expand the functionalities of ReviewerCredits. New APIs allow a smoother dataflow, heeding to the automation of tasks currently performed manually with great benefits in terms of scalabilty, operational time and reduction of human errors.

 

Open Journals Systems (OJS) plugin

If your journal uses OJS from the Public Knowledge Project to manage manuscript submission download and install our free plugin developed by 4Science: highly engaged in open access solutions based on open source technologies, 4Science has been providing technical contributions to the communities of DSpace, DSpace-CRIS, IIIF and OJS.

This plugin allows automated transfer of peer review data from your journal to our database enabling a seamless experience to your reviewers. Installing the plugin, journals will interact automatically with our API (see below). The plugin is released within the OJS plug n gallery, according to the OJS licence rules. The plugin is compatible with OJS 3.x versions. We recommend that before you install the plugin you register your journal. 

 

 

Plugin installation

 

Download plugin now
  • Unpack the plugin package
  • Save it in the plugin folder of your OJS installation. The plugin will be added to your OJS plugins page
  • Proceed to configure it with your journal credentials for ReviewerCredits

 

How does it work?

The plugin connects your journal to ReviewerCredits database using the Reviewer’s ORCID or email address. If a reviewer is not registered on ReviewerCredits it will not be possible to transfer peer review information.

Upon submitting their review (in review step 3), reviewers will find a tick box to agree to the transfer of data to ReviewerCredits.com.  Which data is transferred?

  • Peer reviewer Email address and ORCID (for matching purposes)
  • Manuscript ID
  • Peer review due date
  • Peer review submission date

Upon successful transfer of data, the reviewer will receive a confirmation pop up message from OJS:

Peer review claim information will be visible in you journal’s page  and no further action is required on your part.

If a reviewer is not registered to ReviewerCredits or should the claim transfer fail,  a  pop up message will be displayed, for example:

In this case the reviewer will be prompted to register his/her review claim manually to the ReviewerCredits service.

 

API (Application Programming Interface)

We are have developed API (Application Programming Interface) which allows, at first, the automated transferral of peer review data from publishing platforms. APIs has been developed by 4Science and specifications can be found here.

Our APIs are developed following the paradigm of simplicity and uniformity of mature RESTful webservice. More specifically the API are designed to target level 3 of the Richardson Maturity Model (read the Martin Fowler article here). Our API specifications are fully documented using Swagger (https://swagger.io/) allowing easy consultation and testing with the ability to self generate clients for the most used programming languages including PHP, Java, Python, R, Ruby, Node.js and many others. 

We are interested to enhance our APIs to support new users and integrations: contact us and let us know about your user cases and projects. We are currently working on APIs to query our database from other platforms (e.g. institutional repositories) to retrieve data relative to peer review or conference activities recorded by our members.

API are available to all registered journals. Interested in join us? Click here!

 

Advertisement:
Share This