RQC implementations for various manuscript handling systems (MHS)

last change: 2018-11-19

How your manuscript handling system (MHS) works together with RQC. MHSs not mentioned here are not supported by RQC so far. If you need this to change, contact the makers of your MHS and point them to the RQC API definition.

On this page:

EasyChair

Status: EasyChair is supported since 2016-09. It was the first MHS supported by RQC.

EasyChair support works via web scraping: RQC reads the same web pages that humans look at and pulls the information from them. This means the RQC implementation may break when the EasyChair folks modify the structure of the web pages. Such breakage happens about once every one or two years and will be rapidly repaired as soon as we notice it. If it happens to you, tell us.

HotCRP

Status: HotCRP is supported since 2017-07.

In contrast to EasyChair, HotCRP has a proper API by which RQC can grab the reviewing data. The HotCRP adapter has not yet been used in practice, so there is a (small) question mark whether it covers all practical cases in the appropriate manner.

Open Journal Systems (OJS 3)

Status: A plugin for [OJS 3.2] is under development. It will be the pilot implementation for RQC for journals.

It maps editor roles as follows: - The OJS journal manager is always the (only) level-3 editor in RQC. - For any submission, if there are OJS editors with and without editorial decision privilege, all those with such privilege in OJS will become level-2 editors in RQC and all those without such privilege ("recommend-only") will become level-1 editors in RQC. - If there is no OJS editor without decision privilege, the OJS editors with decision privilege will be level-1 editors in RQC rather than level-2 editors. - If there is also no OJS editor with decision privilege other than the journal manager, the journal manager will be both level-3 and level-1 editor in RQC.



Sun 2018-12-09 23:36 UTC

Review Quality Collector  © 2012-2018

Imprint / Impressum