Closed editorialbot closed 6 months ago
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1007/10968987_3 is OK
- 10.1109/MCSE.2015.68 is OK
- 10.21105/joss.00622 is OK
MISSING DOIs
- No DOI given, and none found for title: SLURM Dashboard
- No DOI given, and none found for title: R: A Language and Environment for Statistical Comp...
- No DOI given, and none found for title: shiny: Web Application Framework for R
- No DOI given, and none found for title: shinydashboard: Create Dashboards with βShinyβ
INVALID DOIs
- None
:wave: @openjournals/csism-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/5340, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@editorialbot accept
Doing it live! Attempting automated processing of paper acceptance...
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:
``` cff-version: "1.2.0" authors: - family-names: Walzthoeni given-names: Thomas orcid: "https://orcid.org/0009-0009-3995-709X" - family-names: Singiali given-names: Bom Bahadur - family-names: Rayner given-names: N. William orcid: "https://orcid.org/0000-0003-0510-4792" - family-names: Casale given-names: Francesco Paolo - family-names: Feest given-names: Christoph orcid: "https://orcid.org/0000-0002-0772-7267" - family-names: Marr given-names: Carsten orcid: "https://orcid.org/0000-0003-2154-4552" - family-names: Wachsmann given-names: Alf orcid: "https://orcid.org/0000-0002-7736-3059" contact: - family-names: Walzthoeni given-names: Thomas orcid: "https://orcid.org/0009-0009-3995-709X" doi: 10.5281/zenodo.10064783 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Walzthoeni given-names: Thomas orcid: "https://orcid.org/0009-0009-3995-709X" - family-names: Singiali given-names: Bom Bahadur - family-names: Rayner given-names: N. William orcid: "https://orcid.org/0000-0003-0510-4792" - family-names: Casale given-names: Francesco Paolo - family-names: Feest given-names: Christoph orcid: "https://orcid.org/0000-0002-0772-7267" - family-names: Marr given-names: Carsten orcid: "https://orcid.org/0000-0003-2154-4552" - family-names: Wachsmann given-names: Alf orcid: "https://orcid.org/0000-0002-7736-3059" date-published: 2024-05-10 doi: 10.21105/joss.06017 issn: 2475-9066 issue: 97 journal: Journal of Open Source Software publisher: name: Open Journals start: 6017 title: "SCAS dashboard: A tool to intuitively and interactively analyze Slurm cluster usage" type: article url: "https://joss.theoj.org/papers/10.21105/joss.06017" volume: 9 title: "SCAS dashboard: A tool to intuitively and interactively analyze Slurm cluster usage" ```
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.
πππ π Toot for this paper π πππ
π¨π¨π¨ THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! π¨π¨π¨
Here's what you must now do:
Any issues? Notify your editorial technical team...
Congratulations to @wathom (Thomas W.) and co-authors on your publication!!
And thanks to @aturner-epcc and @phargogh for reviewing this work! JOSS depends on volunteers and wouldn't be successful without your efforts
: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.06017/status.svg)](https://doi.org/10.21105/joss.06017)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.06017">
<img src="https://joss.theoj.org/papers/10.21105/joss.06017/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.06017/status.svg
:target: https://doi.org/10.21105/joss.06017
This is how it will look in your documentation:
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:
Great, many thanks to the editor @danielskatz and the reviewers @aturner-epcc and @phargogh
@editorialbot reaccept
(Nothing to see here, just re-accepting this to make sure the JATS output are in the correct format)
Rebuilding paper!
:warning: Couldn't update published paper. An error happened.
Submitting author: !--author-handle-->@wathom<!--end-author-handle-- (Thomas W.) Repository: https://github.com/Bioinformatics-Munich/scas_dashboard Branch with paper.md (empty if default branch): Version: v1.0.0 Editor: !--editor-->@danielskatz<!--end-editor-- Reviewers: @aturner-epcc, @phargogh Archive: 10.5281/zenodo.10064783
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
@aturner-epcc & @apjez & @verolero86, 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:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @danielskatz 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 @aturner-epcc