search

openjournals / joss-reviews

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

[REVIEW]: A tool for qualitative data analysis designed to support computational thinking #7031

Closed editorialbot closed 1 month ago

editorialbot commented 4 months ago

Submitting author: !--author-handle-->@cproctor<!--end-author-handle-- (Chris Proctor) Repository: https://github.com/cproctor/qualitative-coding Branch with paper.md (empty if default branch): Version: v1.6.0 Editor: !--editor-->@ymzayek<!--end-editor-- Reviewers: @SamHames, @cmaimone Archive: 10.5281/zenodo.13784403

Status

status

Status badge code:

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

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

@SamHames & @cmaimone, 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 @ymzayek 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 @cmaimone

📝 Checklist for @SamHames

editorialbot commented 1 month ago

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

cproctor commented 1 month ago

@crvernon thank you for your feedback and for catching these errors. I have pushed a fix and confirmed that the proof looks correct.

crvernon commented 1 month ago

@editorialbot accept

editorialbot commented 1 month ago 
Doing it live! Attempting automated processing of paper acceptance...
editorialbot commented 1 month 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: Proctor given-names: Chris orcid: "https://orcid.org/0000-0003-3492-9590" doi: 10.5281/zenodo.13784403 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Proctor given-names: Chris orcid: "https://orcid.org/0000-0003-3492-9590" date-published: 2024-10-14 doi: 10.21105/joss.07031 issn: 2475-9066 issue: 102 journal: Journal of Open Source Software publisher: name: Open Journals start: 7031 title: A tool for qualitative data analysis designed to support computational thinking type: article url: "https://joss.theoj.org/papers/10.21105/joss.07031" volume: 9 title: A tool for qualitative data analysis designed to support computational thinking ```

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 month ago

🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘

editorialbot commented 1 month ago

🦋🦋🦋 👉 Bluesky post for this paper 👈 🦋🦋🦋

editorialbot commented 1 month 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/5998
  2. Wait five minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.07031
  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...

crvernon commented 1 month ago

🥳 Congratulations on your new publication @cproctor! Many thanks to @ymzayek for editing and @SamHames and @cmaimone for your time, hard work, and expertise!! JOSS wouldn't be able to function nor succeed without your efforts.

Please consider becoming a reviewer for JOSS if you are not already: https://reviewers.joss.theoj.org/join

editorialbot commented 1 month 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.07031/status.svg)](https://doi.org/10.21105/joss.07031) HTML: DOI badge reStructuredText: .. image:: https://joss.theoj.org/papers/10.21105/joss.07031/status.svg :target: https://doi.org/10.21105/joss.07031 ```

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: