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
[REVIEW]: SNIK Graph—Visualizing Knowledge about Management of Hospital Information Systems #180
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @bwatson, @behollister it looks like you're currently assigned to review this paper 🎉. Due to the challenges of the COVID-19 pandemic, JOSE is currently operating in a "reduced service mode". ⭐ Important ⭐ If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/openjournals/jose-reviews) repository. As a reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all reviews 😿 To fix this do the following two things:
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 |
|
|
Hi @bwatson, @behollister 👋 — Thank you for agreeing to review for JOSE! I am the editor-in-chief, and @juanklopper is the handling editor for this submission. This issue thread is where the action happens: work your way through the review checklist, feel free to ask questions or post comments here, and also open issues in the submission repository as needed. Godspeed! |
👋 @bwatson, please update us on how your review is going (this is an automated reminder). |
👋 @behollister, please update us on how your review is going (this is an automated reminder). |
I have sent an email to each reviewer (cc'ing the handling editor @juanklopper) reminding them of this pending review and asking if they will still be able to contribute, given the long delay. If they do not reply in a week or so, we may need to find alternative reviewers. Thank you for your patience. |
Thank you for contacting them! |
@whedon remind @behollister in 3 weeks |
Reminder set for @behollister in 3 weeks |
We've heard back from both reviewers, @bwatson, @behollister, via email. We should see some activity in this review soon. Thank you for your patience! |
Sorry for the delay. Was busy meeting manuscript deadlines. Should be able to finish my review by the middle of this week. Still need to complete Functionality/Documentation checklist points. |
Possible issue with instructions for using Node. See snikproject/graph#393 (comment) |
@behollister: Thanks for the correction! Fixed the documentation. |
Issue with developer docs. See snikproject/graph#395 (comment) |
finished review. only would make suggestions about usability, such as scaled labels for nodes hard to see at various zoom levels, and overlapping popup text for menu items. otherwise, all claims have been met by project for jose. |
one more note. was not able to reach service locally on windows after having completed all installation steps in docs. worked fine on linux however. |
The issue has been fixed, thanks for notifying us! |
We usually develop under Linux but would like to enable development under Windows as well. |
@bwatson: As behollister has completed the review, it would be really nice if you could find the time to review the paper soon. |
@KonradHoeffner — thanks for your patience! We have heard from Bruce via email and he is aware and will be working on it these days. |
@KonradHoeffner — I request your patience in this, with a gentle reminder to leave the task of following up with reviewers to the editor. You are welcome to tag me or @juanklopper, but try not to ping the reviewer directly with reminders. This is just to respect editorial roles (remembering that everyone is a volunteer!). Of course, you can address the reviewers directly when responding to their review comments. Thanks! |
@labarba: Sorry, I will not ping the reviewers with reminders again. |
Just a quick update that we have been in email contact with reviewer @bwatson, and he is looking into this! |
@behollister: The overlapping mouseover text was adressed in snikproject/graph#379 and is now fixed in snikproject/graph@974580a. |
@bwatson good to have caught up with you via email. How are you doing for time? |
@whedon generate pdf |
OK, @bwatson is no longer a reviewer |
I just went through my notes from one year ago and remembered that this paper still exists, is there anything I can do to get this moving again? |
Hi there,
TBH, I thought that it was moved off my plate, but was moved ahead in any case. Is it somehow stuck, and action needed from me?
Best regards to you, Bruce
On 19 Jun 2023, at 12:04, Konrad Höffner ***@***.******@***.***>> wrote:
I just went through my notes from one year ago and remembered that this paper still exists, is there anything I can do to get this moving again?
—
Reply to this email directly, view it on GitHub<#180 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAGAYTNXL3YZZQ3DXQU6KL3XMAP2ZANCNFSM53KJ74RA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
The integrity and confidentiality of this email are governed by these terms. Disclaimer<https://www.sun.ac.za/emaildisclaimer/default.aspx>
Die integriteit en vertroulikheid van hierdie e-pos word deur die volgende bepalings bereël. Vrywaringsklousule<https://www.sun.ac.za/emaildisclaimer/default.aspx>
|
@bwatson It has indeed been moved off your plate, no worries! |
@juanklopper: Is there anything I can do to get this going again? |
@labarba, @juanklopper: This paper is now in the review queue for almost 1.5 years, is there anything I can do to get this to continue? |
@labarba @juanklopper once again nearly a month has passed with no visible change, should I retract this paper and submit it elsewhere or is there anything I can do to get this review going again? |
@labarba @juanklopper new year, new try :-) Is there any way I can help moving this process forward? |
@Lorena After our previous discussions regarding the reviewer, can we move ahead and accept this for publication? |
@whedon generate pdf |
My name is now @editorialbot |
@editorialbot generate pdf |
@juanklopper @labarba: Another three months later, I hope it is OK to ask again if I can do anything to move this forward :-) |
Submitting author: @KonradHoeffner (Konrad Höffner)
Repository: https://github.com/snikproject/snik-graph
Branch with paper.md (empty if default branch):
Version: 3.0.0
Editor: @juanklopper
Reviewers: @behollister
Archive: Pending
Status
Status badge code:
Reviewers and authors:
Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)
Reviewer instructions & questions
@behollister, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @juanklopper know.
✨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest ✨
Review checklist for @behollister
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
paper.md
file include a list of authors with their affiliations?The text was updated successfully, but these errors were encountered: