openjournals / joss-reviews

Reviews for the Journal of Open Source Software
Creative Commons Zero v1.0 Universal
718 stars 38 forks source link

[REVIEW]: {histoc} histocompatibility functions for organ transplantation #4807

Closed editorialbot closed 1 year ago

editorialbot commented 2 years ago

Submitting author: !--author-handle-->@balima78<!--end-author-handle-- (Bruno A Lima) Repository: https://github.com/txopen/histoc Branch with paper.md (empty if default branch): Version: v0.2.1 Editor: !--editor-->@crvernon<!--end-editor-- Reviewers: @turgeonmaxime, @aj2duncan Archive: 10.5281/zenodo.7338242

Status

status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/1913c20af5e50aa41711781623339c90"><img src="https://joss.theoj.org/papers/1913c20af5e50aa41711781623339c90/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/1913c20af5e50aa41711781623339c90/status.svg)](https://joss.theoj.org/papers/1913c20af5e50aa41711781623339c90)

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

@turgeonmaxime & @aj2duncan, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review. First of all you need to run this command in a separate comment to create the checklist:

@editorialbot generate my checklist

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @crvernon 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 ✨

Checklists

πŸ“ Checklist for @turgeonmaxime

πŸ“ Checklist for @aj2duncan

crvernon commented 1 year ago

@editorialbot recommend-accept

editorialbot commented 1 year ago
Attempting dry run of processing paper acceptance...
editorialbot commented 1 year ago

:wave: @openjournals/bcm-eics, this paper is ready to be accepted and published.

Check final proof :point_right::page_facing_up: Download article

If the paper PDF and the deposit XML files look good in https://github.com/openjournals/joss-papers/pull/3773, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

editorialbot commented 1 year ago
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.32932/pjnh.2020.07.070 is OK
- 10.1053/j.ajkd.2005.07.031 is OK
- 10.1097/TP.0000000000001326 is OK

MISSING DOIs

- None

INVALID DOIs

- None
Kevin-Mattheus-Moerman commented 1 year ago

@balima78 I am the AEiC for this track and here to help process this work for acceptance. There are some issues below which need to be addressed first:

balima78 commented 1 year ago

@Kevin-Mattheus-Moerman , done and done! thank you for your attention

Kevin-Mattheus-Moerman commented 1 year ago

@editorialbot generate pdf

editorialbot commented 1 year ago

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

Kevin-Mattheus-Moerman commented 1 year ago

@editorialbot accept

editorialbot commented 1 year ago
Doing it live! Attempting automated processing of paper acceptance...
editorialbot commented 1 year ago

🐦🐦🐦 πŸ‘‰ Tweet for this paper πŸ‘ˆ 🐦🐦🐦

editorialbot commented 1 year ago

🐘🐘🐘 πŸ‘‰ Toot for this paper πŸ‘ˆ 🐘🐘🐘

editorialbot commented 1 year ago

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

  1. Check final PDF and Crossref metadata that was deposited :point_right: https://github.com/openjournals/joss-papers/pull/3776
  2. Wait a couple of minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.04807
  3. If everything looks good, then close this review issue.
  4. Party like you just published a paper! πŸŽ‰πŸŒˆπŸ¦„πŸ’ƒπŸ‘»πŸ€˜

Any issues? Notify your editorial technical team...

Kevin-Mattheus-Moerman commented 1 year ago

Congratulations @balima78 on your publication in JOSS!

Thanks @crvernon for editing this work, and special thanks to the reviewers: @turgeonmaxime and @aj2duncan!!!

editorialbot commented 1 year ago

:tada::tada::tada: Congratulations on your paper acceptance! :tada::tada::tada:

If you would like to include a link to your paper from your README use the following code snippets:

Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.04807/status.svg)](https://doi.org/10.21105/joss.04807)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04807">
  <img src="https://joss.theoj.org/papers/10.21105/joss.04807/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04807/status.svg
   :target: https://doi.org/10.21105/joss.04807

This is how it will look in your documentation:

DOI

We need your help!

The Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following: