Open editorialbot opened 8 months ago
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
👋 @mspada @Flaminietta apologies for the delay! Summer got in the way, but I think this is pretty close to ready for publishing! A few things before we do that:
So close! I'll check in soon, thanks again for lending your expertise @B3J4y @limengbinggz
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@mspada @Flaminietta could you review this version with the changes, please? If you are satisfied you can deposit your software in Zenodo and post the DOI here and the most recent version. I can kick off the publishing steps after that.
@editorialbot set <DOI here> as archive
@editorialbot set <version here> as version
@editorialbot generate pdf
@editorialbot check references
and ask author(s) to update as needed@editorialbot recommend-accept
Hi @galessiorob,
Let us know if you need something else from us. Thank you for the support @mspada and @Flaminietta
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
✅ OK DOIs
- 10.1007/s10669-020-09784-x is OK
- 10.1016/j.envsoft.2021.105208 is OK
- 10.1016/S0377-2217(97)00163-X is OK
- 10.1016/j.dss.2022.113848 is OK
- 10.1016/j.softx.2023.101368 is OK
- 10.21105/joss.04567 is OK
- 10.1016/j.envsoft.2020.104890 is OK
- 10.1016/j.omega.2017.04.007 is OK
- 10.1007/978-1-4757-2500-1_2 is OK
- 10.1007/0-387-31099-1_2 is OK
- 10.1007/s11205-017-1832-9 is OK
- 10.1016/j.ecolind.2018.06.009 is OK
- 10.1016/j.ecolind.2019.105731 is OK
- 10.1016/j.ijggc.2016.08.023 is OK
- 10.1007/978-1-4939-3094-4_12 is OK
- 10.1016/j.ecolind.2014.05.014 is OK
🟡 SKIP DOIs
- No DOI given, and none found for title: The global competitiveness report 2018
❌ MISSING DOIs
- None
❌ INVALID DOIs
- https://doi.org/10.48550/arXiv.2404.06370 is INVALID because of 'https://doi.org/' prefix
@mspada and @Flaminietta thanks for the swift changes! Could you check that last DOI that is showing up as invalid, please? Just remove the "https://doi.org/" prefix
And the "The global competitiveness report 2018", could you add it too, please?
@galessiorob for the "The global competitiveness report 2018" there is no doi, but just an ISBN, should I added it or not?
@galessiorob Do we need to create an additional Release after updating the paper with the doi problem?
Do we need to create an additional Release after updating the paper with the doi problem?
I don't believe so, but will ask the Editor in Chief
"The global competitiveness report 2018" there is no doi, but just an ISBN, should I added it or not?
Yes, let's add it please, and we can also ask the Editor, we'll leave a note. Thanks!
Hi @galessiorob, we removed the "https://doi.org/" prefix where requested and added the ISBN to the report. Should we generate a new tag? Thanks
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
✅ OK DOIs
- 10.1007/s10669-020-09784-x is OK
- 10.48550/arXiv.2404.06370 is OK
- 10.1016/j.envsoft.2021.105208 is OK
- 10.1016/S0377-2217(97)00163-X is OK
- 10.1016/j.dss.2022.113848 is OK
- 10.1016/j.softx.2023.101368 is OK
- 10.21105/joss.04567 is OK
- 10.1016/j.envsoft.2020.104890 is OK
- 10.1016/j.omega.2017.04.007 is OK
- 10.1007/978-1-4757-2500-1_2 is OK
- 10.1007/0-387-31099-1_2 is OK
- 10.1007/s11205-017-1832-9 is OK
- 10.1016/j.ecolind.2018.06.009 is OK
- 10.1016/j.ecolind.2019.105731 is OK
- 10.1016/j.ijggc.2016.08.023 is OK
- 10.1007/978-1-4939-3094-4_12 is OK
- 10.1016/j.ecolind.2014.05.014 is OK
🟡 SKIP DOIs
- No DOI given, and none found for title: The global competitiveness report 2018
❌ MISSING DOIs
- None
❌ INVALID DOIs
- None
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@editorialbot set 10.5281/zenodo.13694286 as archive
Done! archive is now 10.5281/zenodo.13694286
@editorialbot set v1.1.0 as version
Done! version is now v1.1.0
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@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/s10669-020-09784-x is OK
- 10.48550/arXiv.2404.06370 is OK
- 10.1016/j.envsoft.2021.105208 is OK
- 10.1016/S0377-2217(97)00163-X is OK
- 10.1016/j.dss.2022.113848 is OK
- 10.1016/j.softx.2023.101368 is OK
- 10.21105/joss.04567 is OK
- 10.1016/j.envsoft.2020.104890 is OK
- 10.1016/j.omega.2017.04.007 is OK
- 10.1007/978-1-4757-2500-1_2 is OK
- 10.1007/0-387-31099-1_2 is OK
- 10.1007/s11205-017-1832-9 is OK
- 10.1016/j.ecolind.2018.06.009 is OK
- 10.1016/j.ecolind.2019.105731 is OK
- 10.1016/j.ijggc.2016.08.023 is OK
- 10.1007/978-1-4939-3094-4_12 is OK
- 10.1016/j.ecolind.2014.05.014 is OK
🟡 SKIP DOIs
- No DOI given, and none found for title: The global competitiveness report 2018
❌ MISSING DOIs
- None
❌ INVALID DOIs
- None
:warning: Error preparing paper acceptance. The generated XML metadata file is invalid.
IDREFS attribute rid references an unknown ID "TableU0025202"
IDREFS attribute rid references an unknown ID "TableU0025203"
IDREFS attribute rid references an unknown ID "TableU0025201"
Found the issue with the table ids pointed above, here's a PR that removes the spaces. I think this should fix it. @mspada @Flaminietta
Hi @galessiorob, we just merged your push into the main. Let's hope it will work out now. Thanks! @mspada and @Flaminietta
@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/s10669-020-09784-x is OK
- 10.48550/arXiv.2404.06370 is OK
- 10.1016/j.envsoft.2021.105208 is OK
- 10.1016/S0377-2217(97)00163-X is OK
- 10.1016/j.dss.2022.113848 is OK
- 10.1016/j.softx.2023.101368 is OK
- 10.21105/joss.04567 is OK
- 10.1016/j.envsoft.2020.104890 is OK
- 10.1016/j.omega.2017.04.007 is OK
- 10.1007/978-1-4757-2500-1_2 is OK
- 10.1007/0-387-31099-1_2 is OK
- 10.1007/s11205-017-1832-9 is OK
- 10.1016/j.ecolind.2018.06.009 is OK
- 10.1016/j.ecolind.2019.105731 is OK
- 10.1016/j.ijggc.2016.08.023 is OK
- 10.1007/978-1-4939-3094-4_12 is OK
- 10.1016/j.ecolind.2014.05.014 is OK
🟡 SKIP DOIs
- No DOI given, and none found for title: The global competitiveness report 2018
❌ MISSING DOIs
- None
❌ INVALID DOIs
- None
:warning: Error preparing paper acceptance. The generated XML metadata file is invalid.
IDREFS attribute rid references an unknown ID "Table2"
IDREFS attribute rid references an unknown ID "Table3"
IDREFS attribute rid references an unknown ID "Table1"
@oliviaguest would you mind taking a look at this Table ID issue in the formatting of md to XML, please? This is the last thing to check off before publishing. Thanks in advance!
@galessiorob I checked all items in the check list, sorry for the delay.
Submitting author: !--author-handle-->@Flaminietta<!--end-author-handle-- (Flaminia Catalli) Repository: https://github.com/wetransform-os/ProMCDA Branch with paper.md (empty if default branch): main Version: v1.1.0 Editor: !--editor-->@galessiorob<!--end-editor-- Reviewers: @limengbinggz, @B3J4y Archive: 10.5281/zenodo.13694286
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
@limengbinggz & @B3J4y, 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 @galessiorob 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 @limengbinggz
📝 Checklist for @B3J4y
📝 Checklist for @paulrougieux