Is there a possibility to determine the number of submissions (published and declined) in a specific time frame (all submissions of one year) and the average time it took to process a submission (time submission → decision, time submission → publication)?
In OJS 2.4.8 I could filter the archive for the submission date and the statistics function gave results for the second. There is no appropriate filter for the archive in OJS 3 and the report plugins only work with the published articles. I also tried the PKP usage statistics report but it does not seem to contain submission dates?
We would need the data to evaluate and optimize our editorial workflow. I have no server access, only site admin rights to our OJS.
Hi @heike_riegler,
This would be a relatively easy query to write if you had access to phpMyAdmin or some other way of accessing your database – however it sounds like you probably don’t have that.
I think this would be a good candidate for a new report plugin, but I’m not aware of anything that currently provides that data.
Regards,
Alec Smecher
Public Knowledge Project Team
A couple of our journals request for this exact data like 3-4 times a year. Every time I do the required queries I think of writing a report plugin that would do it for me and I could just send them the instructions. Have not written it yet, but it very well could be I will do it in the near future.
I think that this data was also mentioned in the OJS report plans that were discussed in the PKP Sprint in Montreal last summer. Not sure how that is progressing?
Hi all,
@ajnyga, I think you’re talking about the internal statistics sprint group documented here? There’s an issue filed in github for OJS 3.2, but work hasn’t progressed on it yet.
Regards,
Alec Smecher
Public Knowledge Project Team
2 Likes
Hi all,
thanks for the replies. Theoretically, I could ask our IT guy to do a query on the database, but since I need to monitor these data regularly, a monthly or quarterly request for the same thing might make me unpopular with him 
I better save my bother-the-IT-guy-time for more important things.
I will keep watching the GitHub issue, though.
Regards,
Heike