-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PRE REVIEW]: RCTab: An Azure Subscription Management System #6082
Comments
Hello human, I'm @editorialbot, a robot that can help you with some common editorial tasks. For a list of things I can do to help you, just type:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
|
|
Wordcount for |
|
👋 @Iain-S - note that your paper does not compile. Please follow the example paper and note that you can click on the error above to find out more about it. Please feel free to make changes to your .md file, then use the command Also, it's very unusual not to have references. Can you say anything about this? I'm also unsure that this is research software as defined by JOSS, but once the paper is ready, I'll ask other editors to weigh in. Finally, where is the code that JOSS would review? |
@editorialbot generate pdf |
Five most similar historical JOSS papers: hotsub: A batch job engine for cloud services with ETL framework FRIEDA: Flexible Robust Intelligent Elastic Data Management Framework secuTrialR: Seamless interaction with clinical trial databases in R Translational Informatics Management System (TIMS): Towards OMICS based clinical data management for long term curation of clinical studies Castellum: A participant management tool for scientific studies |
Hi @danielskatz, I think it has compiled OK now.
The codebase comprises four repositories, in addition to the one containing the paper, which has documentation:
I wouldn't expect a reviewer to be able to look at the whole codebase in depth but can point out critical or representative sections if it would be helpful.
We thought it might fall under a liberal interpretation of the "supports the functioning of research instruments or the execution of research experiments" part of the definition as I presume FRIEDA and hotsub (found by the editorial bot, above) do.
There was very little academic literature on the adoption of cloud computing for research that we could find to draw on. We certainly did use other sources for the paper and, where possible, I have included them as inline links. I notice that the hotsub paper also references websites such as DockerHub and Azure documentation. If you think it would be appropriate to add similar references, I'm more than happy to. |
Thanks for your response. I'll now start a scope review re the "is this research software" question. |
@arfon - can you check on the LOC in these 4 repositories to help with the scope query? |
@editorialbot query scope |
Submission flagged for editorial review. |
@editorialbot generate pdf |
Five most similar historical JOSS papers: hotsub: A batch job engine for cloud services with ETL framework FRIEDA: Flexible Robust Intelligent Elastic Data Management Framework secuTrialR: Seamless interaction with clinical trial databases in R Translational Informatics Management System (TIMS): Towards OMICS based clinical data management for long term curation of clinical studies Castellum: A participant management tool for scientific studies |
@Iain-S - I'm sorry to say that after some discussion amongst the JOSS editors, we have decided that this submission is not research software as defined by JOSS. (Note that this definition has been interpreted somewhat more strictly over time, so it's possible that some published work from years ago would not be considered in-scope today.) This does not mean that it is not software that is useful in research, but just that JOSS does not consider it in scope for review as research software. Please see https://joss.readthedocs.io/en/latest/submitting.html#other-venues-for-reviewing-and-publishing-software-packages for other suggestions for how you might receive credit for your work. |
@editorialbot reject |
Paper rejected. |
Submitting author: @Iain-S (Iain Stenson)
Repository: https://github.com/alan-turing-institute/rctab
Branch with paper.md (empty if default branch): joss-paper
Version: v1
Editor: Pending
Reviewers: Pending
Managing EiC: Daniel S. Katz
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @Iain-S. Currently, there isn't a JOSS editor assigned to your paper.
@Iain-S if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
Editor instructions
The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:
The text was updated successfully, but these errors were encountered: