Closed whedon closed 2 years ago
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks.
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
For a list of things I can do to help you, just type:
@whedon commands
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
@whedon generate pdf
Wordcount for paper.md
is 1478
Software report (experimental):
github.com/AlDanial/cloc v 1.88 T=0.04 s (466.8 files/s, 185112.7 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Rmd 2 271 520 2140
R 9 175 1233 1355
TeX 3 31 0 521
Markdown 2 100 0 312
YAML 1 15 1 68
-------------------------------------------------------------------------------
SUM: 17 592 1754 4396
-------------------------------------------------------------------------------
Statistical information for the repository '9da9031ad554ed0ec6c0f5d2' was
gathered on 2021/09/21.
The following historical commit information, by author, was found:
Author Commits Insertions Deletions % of changes
jessicatytam 2 19 19 100.00
Below are the number of rows from each author that have survived and are still
intact in the current revision:
Author Rows Stability Age % in comments
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1073/pnas.0507655102 is OK
- 10.1111/tbed.12221 is OK
- 10.1111/mam.12066 is OK
- 10.1007/s11192-015-1798-9 is OK
- 10.1007/s11192-007-1859-9 is OK
- 10.1371/journal.pone.0131004 is OK
- 10.1111/mam.12038 is OK
- 10.1038/s41598-017-09084-6 is OK
- 10.1139/facets-2016-0011 is OK
- 10.1007/s11192-006-0147-4 is OK
- 10.1017/S1367943004001799 is OK
- 10.1371/journal.pone.0189577 is OK
- 10.1007/s11192-006-0146-5 is OK
- 10.1016/S0169-5347(01)02381-3 is OK
- 10.1038/s41467-018-07916-1 is OK
- 10.1111/acv.12586 is OK
- 10.1038/s41477-021-00912-2 is OK
- 10.1016/j.gecco.2018.e00423 is OK
- 10.1007/s11160-019-09556-0 is OK
- 10.1111/j.1523-1739.2006.00616.x is OK
- 10.1111/j.1523-1739.2010.01453.x is OK
- 10.1108/07378830610715473 is OK
MISSING DOIs
- 10.1093/eurheartj/ehx446 may be a valid DOI for title: Other Metrics: beyond the Impact Factor
INVALID DOIs
- None
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@Bisaloo are you up for editing this submission?
@whedon invite @Bisaloo as editor
@Bisaloo has been invited to edit this submission.
Hi @kthyng and @jessicatytam, yes, I can edit this submission
@whedon assign me as editor
OK, the editor is @Bisaloo
@jessicatytam, while I'm looking for reviewers, could you please have a look at the missing DOI detected by whedon in this comment?
@ahasverus, would you be interested in reviewing this paper & R package for JOSS?
:wave: @dombennett, you signaled interest in reviewing papers for JOSS. Would you have time to review this paper & package that matches the research interests you listed?
Hi @kamapu :wave:, I saw your post on rOpenSci slack and this package seems relevant to your interests. Would you be able to help JOSS with a review?
Hi @kamapu wave, I saw your post on rOpenSci slack and this package seems relevant to your interests. Would you be able to help JOSS with a review?
This seems to be an interesting package. I may not feel comfortable reviewing a package but if the matter of review is a manuscript, I can take the challenge :+1:
@kamapu, thanks for your answer. You can learn more about the review process at JOSS in our documentation. The section "review criteria" and "review checklist" should answer your questions.
In short, we review both the package & the paper. I believe it is possible to bring valuable insights by trying to use the package a way any user would: try to install it, read the documentation, see if you get any errors at any point, tell us if any crucial functionality seems to be missing, etc. Some items may require a slightly more advanced knowledge of R (e.g., does the package have tests?) but seeing that you already developed a couple of packages, you might already be familiar with these concepts.
Feel free to take a couple of days to think about it if you'd like. But if you are already sure you do not wish to review this package & paper, I understand and respect your decision :+1:.
@kamapu, thanks for your answer. You can learn more about the review process at JOSS in our documentation. The section "review criteria" and "review checklist" should answer your questions.
In short, we review both the package & the paper. I believe it is possible to bring valuable insights by trying to use the package a way any user would: try to install it, read the documentation, see if you get any errors at any point, tell us if any crucial functionality seems to be missing, etc. Some items may require a slightly more advanced knowledge of R (e.g., does the package have tests?) but seeing that you already developed a couple of packages, you might already be familiar with these concepts.
Feel free to take a couple of days to think about it if you'd like. But if you are already sure you do not wish to review this package & paper, I understand and respect your decision +1.
I learned programming by doing but it may be the case of many of us, thus I may oversee some technical details but I can take the challenge of assessing this package and attached article from the perspective of an user.
I learned programming by doing but it may be the case of many of us, thus I may oversee some technical details but I can take the challenge of assessing this package and attached article from the perspective of an user.
Great! Thank you for your help! Let me find a second reviewer and we can get started.
@whedon add @kamapu as reviewer
OK, @kamapu is now a reviewer
Hi @tom-gu :wave:, would you have any interest in helping us to review this package and paper? I understand this is only tangentially related to the core of your research interests (which I discovered via the bdverse
) but I believe this has the potential to pique your interest :wink:
Hi @DrMattG :wave:, would you be able to help us review this R package and paper for JOSS? This seems really close to the interests you list in our review volunteering form and in your GitHub README!
Hi @tom-gu π, would you have any interest in helping us to review this package and paper? I understand this is only tangentially related to the core of your research interests (which I discovered via the
bdverse
) but I believe this has the potential to pique your interest π
Hi @Bisaloo π Yes, I can review the R package and paper for JOSS. What's a reasonable timetable?
Thanks for your answer! The review at JOSS is slightly different than others journals. In short, we have found it is usually more efficient to have a more interactive review, where reviewers can post their comments/suggestions/questions as they come as GitHub issues in the submission repository. This differs from "traditional" reviews where you send all your review comments at once. More details are available in our documentation. I'll post a detailed guide when the review process officially starts.
We usually aim to have comments within 1-2 weeks (you will receive an automated reminder after 2 weeks asking you about your current progress) but there is room for some flexibility.
Hi @DrMattG π, would you be able to help us review this R package and paper for JOSS? This seems really close to the interests you list in our review volunteering form and in your GitHub README!
Hi @Bisaloo I'd be happy to!
Hi @DrMattG wave, would you be able to help us review this R package and paper for JOSS? This seems really close to the interests you list in our review volunteering form and in your GitHub README!
Hi @Bisaloo I'd be happy to!
Amazing! With 3 reviewers, we are ready to go! The review can now formally start :tada:.
@whedon add @tom-gu as reviewer
OK, @tom-gu is now a reviewer
@whedon add @DrMattG as reviewer
OK, @DrMattG is now a reviewer
@whedon start review
OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/3776.
Submitting author: @jessicatytam (Jessica Tam) Repository: https://github.com/jessicatytam/specieshindex Version: 0.3.1 Editor: @Bisaloo Reviewers: @kamapu, @tom-gu, @DrMattG Managing EiC: Kristen Thyng
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @jessicatytam. Currently, there isn't an JOSS editor assigned to your paper.
The author's suggestion for the handling editor is @Bisaloo.
@jessicatytam if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission (please start at the bottom of the list).
Editor instructions
The JOSS submission bot @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type: