Closed editorialbot closed 1 year ago
@editorialbot recommend-accept
This will generate the version I'll proofread
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1007/978-3-319-66158-2_34 is OK
- 10.1137/1.9781611975673.15 is OK
- 10.24963/ijcai.2019/149 is OK
- 10.1016/j.artint.2011.05.002 is OK
- 10.24963/ijcai.2022/261 is OK
- 10.21105/joss.04708 is OK
- 10.1007/978-3-030-67658-2_3 is OK
- 10.1093/bioinformatics/btn490 is OK
- 10.3390/e18050164 is OK
- 10.1016/j.artint.2015.04.003 is OK
- 10.1007/978-3-319-44953-1_22 is OK
- 10.1002/widm.1207 is OK
- 10.14257/ijhit.2013.6.6.30 is OK
- 10.1002/aaai.12081 is OK
- 10.1609/aaai.v36i11.21542 is OK
- 10.3389/frai.2022.868085 is OK
MISSING DOIs
- None
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/4495, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@ChaVer - I've suggested some minor changes in https://gitlab.com/chaver/choco-mining/-/merge_requests/4 - please merge this, or let me know what you disagree with.
Also, I'm unsure of the inconsistency between "Choco Solver" and "Choco-solver" as both are used in various places in the paper.
@danielskatz I've just accepted the merge request.
I've also updated the paper to replace "Choco Solver" with "Choco-solver". Should I also update the title of the paper ?
I think that updating the title as well would make sense
I've just updated the paper with the new title.
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1007/978-3-319-66158-2_34 is OK
- 10.1137/1.9781611975673.15 is OK
- 10.24963/ijcai.2019/149 is OK
- 10.1016/j.artint.2011.05.002 is OK
- 10.24963/ijcai.2022/261 is OK
- 10.21105/joss.04708 is OK
- 10.1007/978-3-030-67658-2_3 is OK
- 10.1093/bioinformatics/btn490 is OK
- 10.3390/e18050164 is OK
- 10.1016/j.artint.2015.04.003 is OK
- 10.1007/978-3-319-44953-1_22 is OK
- 10.1002/widm.1207 is OK
- 10.14257/ijhit.2013.6.6.30 is OK
- 10.1002/aaai.12081 is OK
- 10.1609/aaai.v36i11.21542 is OK
- 10.3389/frai.2022.868085 is OK
MISSING DOIs
- None
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/4496, 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: Vernerey given-names: Charles orcid: "https://orcid.org/0000-0002-2922-2833" - family-names: Loudni given-names: Samir orcid: "https://orcid.org/0000-0001-6245-7661" contact: - family-names: Vernerey given-names: Charles orcid: "https://orcid.org/0000-0002-2922-2833" doi: 10.5281/zenodo.8263971 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Vernerey given-names: Charles orcid: "https://orcid.org/0000-0002-2922-2833" - family-names: Loudni given-names: Samir orcid: "https://orcid.org/0000-0001-6245-7661" date-published: 2023-08-18 doi: 10.21105/joss.05654 issn: 2475-9066 issue: 88 journal: Journal of Open Source Software publisher: name: Open Journals start: 5654 title: A Java Library for Itemset Mining with Choco-solver type: article url: "https://joss.theoj.org/papers/10.21105/joss.05654" volume: 8 title: A Java Library for Itemset Mining with Choco-solver ```
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 @ChaVer (Charles Vernerey) and co-author on your publication!!
And thanks to @skadio and @jgFages for reviewing! JOSS only succeeds because of volunteers, and we appreciate your work
: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.05654/status.svg)](https://doi.org/10.21105/joss.05654)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05654">
<img src="https://joss.theoj.org/papers/10.21105/joss.05654/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05654/status.svg
:target: https://doi.org/10.21105/joss.05654
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:
Thank you @skadio and @jgFages for your reviews and @danielskatz for your help.
Submitting author: !--author-handle-->@ChaVer<!--end-author-handle-- (Charles Vernerey) Repository: https://gitlab.com/chaver/choco-mining Branch with paper.md (empty if default branch): Version: v1.0.2 Editor: !--editor-->@danielskatz<!--end-editor-- Reviewers: @skadio, @jgFages Archive: 10.5281/zenodo.8263971
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
@skadio & @jgFages, 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 @jgFages
π Checklist for @skadio