search

openjournals / joss-reviews

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

[REVIEW]: PlatiPy: Processing Library and Analysis Toolkit for Medical Imaging in Python #5374

Closed editorialbot closed 1 year ago

editorialbot commented 1 year ago

Submitting author: !--author-handle-->@pchlap<!--end-author-handle-- (Phillip Chlap) Repository: https://github.com/pyplati/platipy Branch with paper.md (empty if default branch): joss-paper Version: v0.6.1 Editor: !--editor-->@samhforbes<!--end-editor-- Reviewers: @agisga, @tomelse Archive: 10.5281/zenodo.8032858

Status

status

Status badge code:

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

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

@agisga & @tomelse, 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 @samhforbes 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 @agisga

📝 Checklist for @tomelse

pchlap commented 1 year ago

Hi @pchlap this is all looking really good. I think you've done a great job with software and paper, and I'm going to hand over to the EiC now with a recommendation to accept!

Thank you @samhforbes, this has been a great experience. I have really enjoyed the JOSS review process, thanks a lot for coordinating! :)

Kevin-Mattheus-Moerman commented 1 year ago

Post-Review Checklist for Editor and Authors

Additional Author Tasks After Review is Complete

Editor Tasks Prior to Acceptance

Kevin-Mattheus-Moerman commented 1 year ago

@pchlap I am the AEiC for this track and here to help process the final steps. I have studied this review, the paper, the software repository, and the archive link, and all seems in order. I will now process this work for acceptance in JOSS.

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

Ensure proper citation by uploading a plain text CITATION.cff file to the default branch of your repository.

If using GitHub, a Cite this repository menu will appear in the About section, containing both APA and BibTeX formats. When exported to Zotero using a browser plugin, Zotero will automatically create an entry using the information contained in the .cff file.

You can copy the contents for your CITATION.cff file here:

CITATION.cff

``` cff-version: "1.2.0" authors: - family-names: Chlap given-names: Phillip orcid: "https://orcid.org/0000-0002-6517-8745" - family-names: Finnegan given-names: Robert N. orcid: "https://orcid.org/0000-0003-4728-8462" doi: 10.5281/zenodo.8032858 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Chlap given-names: Phillip orcid: "https://orcid.org/0000-0002-6517-8745" - family-names: Finnegan given-names: Robert N. orcid: "https://orcid.org/0000-0003-4728-8462" date-published: 2023-06-26 doi: 10.21105/joss.05374 issn: 2475-9066 issue: 86 journal: Journal of Open Source Software publisher: name: Open Journals start: 5374 title: "PlatiPy: Processing Library and Analysis Toolkit for Medical Imaging in Python" type: article url: "https://joss.theoj.org/papers/10.21105/joss.05374" volume: 8 title: "PlatiPy: Processing Library and Analysis Toolkit for Medical Imaging in Python" ```

If the repository is not hosted on GitHub, a .cff file can still be uploaded to set your preferred citation. Users will be able to manually copy and paste the citation.

Find more information on .cff files here and here.

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/4348
  2. Wait a couple of minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.05374
  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

@pchlap congratulations on this publication in JOSS!

@samhforbes thanks for editing this submission!

And also a special thanks to the reviewers: @agisga, @tomelse !!!!

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.05374/status.svg)](https://doi.org/10.21105/joss.05374)

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

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

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: