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]: RMAVIS v1.0: a R Shiny application for the analysis of vegetation survey data and assignment to GB NVC communities #6615
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:
|
|
Software report:
Commit count by author:
|
Paper file info: 📄 Wordcount for ✅ The paper includes a |
License info: 🟡 License found: |
Hi @ZekeMarshall and thanks for your submission! I am looking for some specific items to make sure your submission fits our requirements at a high level (not at the more detailed review level) before moving on to finding an editor or putting this on our waitlist if no relevant editors are available. I'll comment over time as I have a chance to go through them:
In the meantime, please take a look at the comments above ⬆️ from the editorialbot to address any DOI, license, or paper issues if you're able (there may not be any), or suggest reviewers. For reviewers, please suggest 5 reviewers from the database listed above or your own (non-conflicted) extended network. Their github handles are most useful to receive but please don't use "@" to reference them since it will prematurely ping them. |
Hi @ZekeMarshall you have two license files — the MIT one is what we'd normally expect but is there a reason you need both files? |
Hi @kthyng , thanks for taking a look at this so quickly! Thanks for pointing out the surplus licence file, I've now removed this. Just to check, is it ok to review from the v1 branch? Here is my list of suggested reviewers:
Thanks again! |
I've double-checked my list of references and only managed to replace one reference without a DOI, there are no DOI's for the others unfortunately! |
@editorialbot check references |
|
@editorialbot generate pdf |
@editorialbot generate pdf |
Yes that's fine, though I see it is out of date compared to the main branch now. Is there a reason for that? If you are actively developing it might be best to keep the branch up to date until the review starts, unless there is reason to keep the branch where it is for the review. |
@ZekeMarshall I am going to ping the editorial board to take a make sure this submission is in scope as a web application. This process will take 1-2 weeks. Thank you for your patience! |
@editorialbot query scope |
Submission flagged for editorial review. |
Hi @kthyng , thanks, I hope it is within scope! Thanks again, Zeke |
Hi @kthyng , no problem! What i'll do is make a v0.999 release on the main branch to clean things up, then just use the main branch for the review. Thanks again, Zeke |
@editorialbot set main as branch |
Done! branch is now main |
@editorialbot generate pdf |
@editorialbot set v0.999 as version |
Done! version is now v0.999 |
Thanks @kthyng , sorry to be a bother, the version is now 0.9992, I had to make some corrections. The app has now been released to the public (https://www.ceh.ac.uk/data/software-models/modular-analysis-vegetation-information-system-mavis/rmavis) so this will be the last change before the review process. Thanks again! |
@editorialbot set v0.9992 as version |
Done! version is now v0.9992 |
This passed scope query! @mikemahoney218 Would you like to edit this? |
@editorialbot invite @mikemahoney218 as editor |
Invitation to edit this submission sent! |
@editorialbot assign me as editor Happy to take this one on! And I see that @ZekeMarshall has already listed suggested reviewers -- thanks for that, it's a huge help. I'll start pinging people for reviews today and tomorrow and will follow up as I hear back! (And as a note to myself and to keep myself honest -- I just finished sending out the first round of invites) |
Assigned! @mikemahoney218 is now the editor |
Hi @mikemahoney218 , thank you for accepting the role of editor and sending out reviewer invitations! |
@editorialbot add adithirgis as reviewer |
I can't add that reviewer: adithirgis is not a username |
@editorialbot add @adithirgis as reviewer |
@adithirgis added to the reviewers list! |
@ZekeMarshall , would you be able to recommend any potential reviewers who have experience using GB NVC data in their research? I'm having a bit of a hard time finding anyone with a GitHub account who's worked with this data before, but think it's important that we get a review perspective from possible users of this tool as well as from R and Shiny experts -- if you can think of anyone from your network (so long as they don't have a conflict of interest) it would be a huge help. As before, please do not ping them using |
Hi @mikemahoney218 , one potential reviewer would be Kevin Watts (watts-km) from Forest Research. I will ask my co-authors and get back to you about additional reviewers! Just to note RE conflicts of interest, I used to work at Forest Research, but in a different research group and never on any projects directly with Kevin. Thanks! |
Additional potential reviewers who are very experienced with vegetation ecology, but not necessarily the British NVC, and are active on Github could include:
Another potential reviewer would be Maximilian Hesselbarth (mhesselbarth). Thanks! |
@mikemahoney218 , a few suggestions from my co-authors for persons experienced with the British NVC, but who aren't necessarily active on Github could include:
Please let us know if you need any additional suggestions. Thanks again! |
Thank you so much! This will be a huge help. |
@editorialbot add @rasanderson as reviewer |
@rasanderson added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #6682. |
Submitting author: @ZekeMarshall (Zeke Marshall)
Repository: https://github.com/ZekeMarshall/RMAVIS/
Branch with paper.md (empty if default branch): main
Version: v0.9992
Editor: @mikemahoney218
Reviewers: @adithirgis, @rasanderson
Managing EiC: Kristen Thyng
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @ZekeMarshall. Currently, there isn't a JOSS editor assigned to your paper.
@ZekeMarshall 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: