The history, status, and future of RQC

On this page:

History of the RQC initiative

Story told by Lutz Prechelt.

1997-2010

2012

2013

2014

2015

2016

History of the RQC software implementation

Story told by Lutz Prechelt.

2012

2013

2015

2016

2017

Future of the RQC initiative

Future of the RQC software implementation

Many small changes and improvements will be made to the software frequently for a long time. The larger pending improvement steps are the following:

1. RQC for research institutions

Development capacity is small and irregular, so there are no scheduled dates for any of this.

2. RQC manuscript handling system API

The main reason why RQC starts with conferences is that it is simpler:

For journals, the manuscript handling systems will need to tell RQC what happens wrt reviewing so RQC can handle those episodes.
For that, RQC needs to provide an API (application programming interface), a well-documented and publicly available set of operations that can be called over the network via HTTP.

To make RQC available to journals, the providers of the manuscript handling systems need to extend their software to call the RQC API. (Getting them to do that will likely be one of the most difficult aspects of achieving large-scale RQC adoption.)

Such an API needs to be very well thought-out, because it cannot be changed often -- the providers of the manuscript handling systems would not like that.
Therefore, we will need a playground for trying it out and making it sound and stable. This playground will be OJS, an Open Source manuscript handling system used by many Open Access journals.

3. API trial phase

Next are a number of trial uses with journals using OJS in order to validate and perfect the API.

4. RQC for journals and publishers

Only then does it make sense to actually roll out the API. Until the providers of the manuscript handling systems have implemented their use of the API, there is time to build the remaining parts of the journal and publisher functionality.

5. ...and then some

I already (as of mid-2016, before even the conference version of RQC has launched) have a number of ideas of extensions of the core functionality of RQC that will allow providing substantial additional benefits. And I expect there will be more such ideas until the core parts are complete.

Expect news about RQC for a long time.

Want updates?

If you would like to receive updates on the status of RQC (12 messages per year max.), subscribe to the mailing list.



Mon 2017-10-23 04:16 UTC

Review Quality Collector  © 2012-2017

Imprint / Impressum