Closed whedon closed 2 years ago
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.48550/arXiv.1907.07587 is OK
- 10.1109/5.58337 is OK
MISSING DOIs
- None
INVALID DOIs
- 10.5555/3122009.3242010 is INVALID
:wave: @openjournals/jose-eics, this paper is ready to be accepted and published.
Check final proof :point_right: https://github.com/openjournals/jose-papers/pull/99
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/jose-papers/pull/99, then you can now move forward with accepting the submission by compiling again with the flag deposit=true
e.g.
@whedon accept deposit=true
Hmm. It doesn't look like JMLR mints Does. Do you want to instead link to the URL?
url = {http://jmlr.org/papers/v18/17-468.html}
https://dl.acm.org/doi/abs/10.5555/3122009.3242010
This doi seems to link to the source? I can do whatever you prefer.
Interesting. The DOI itself does not resolve at http://doi.org/10.5555/3122009.3242010
EDIT: that is the link that will be automatically added in compiling the PDF, so I think it is best to add it as URL and not a DOI.
Ok. Should I create a new release with the doi changed to url???
No need. The release and archive are really targeting the package. The paper will be deposited by JOSE with its own DOI and will be archived too.
Ok, then I've committed the new bib file.
@whedon generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@whedon accept deposit=true
Doing it live! Attempting automated processing of paper acceptance...
๐จ๐จ๐จ THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSE! ๐จ๐จ๐จ
Here's what you must now do:
Party like you just published a paper! ๐๐๐ฆ๐๐ป๐ค
Any issues? Notify your editorial technical team...
Congratulations, @lindseysbrown, your JOSE paper is published!
Huge thanks to our Reviewers: @rasbt, @Atcold โ we couldn't do this without you ๐
: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://jose.theoj.org/papers/10.21105/jose.00161/status.svg)](https://doi.org/10.21105/jose.00161)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/jose.00161">
<img src="https://jose.theoj.org/papers/10.21105/jose.00161/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://jose.theoj.org/papers/10.21105/jose.00161/status.svg
:target: https://doi.org/10.21105/jose.00161
This is how it will look in your documentation:
We need your help!
Journal of Open Source Education 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:
Wow, awesome, congrats @lindseysbrown, @rachelmoonstar, and David Sondak! ๐๐๐พ
๐ฅณ๐ฅณ๐ฅณ
@labarba โ the submitting author contacted me (on admin@theoj.org) to ask for an update to their paper (see this change: https://github.com/lindseysbrown/Auto-eD/commit/7c1eef58e5d568c739c4902b7b3706ae7a22bc92). This should be possible with a simple @editorialbot reaccept
but before I do this I wanted to get an explicit :+1: from you.
The URL points to a broken page. Update not approved.
I am able to view the updated url: https://autoed.onrender.com Note that render can be slow to spin up on the free tier. (The update was from the heroku link which is broken.)
When I tried it was not working. Now it works.
Submitting author: !--author-handle-->@lindseysbrown<!--end-author-handle-- (Lindsey Brown) Repository: https://github.com/lindseysbrown/Auto-eD Branch with paper.md (empty if default branch): master Version: v1.0.2 Editor: !--editor-->@labarba<!--end-editor-- Reviewer: @rasbt, @Atcold Archive: 10.5281/zenodo.6800009 Paper kind: software
:warning: JOSE reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSE is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
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
@rasbt & @Atcold, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @labarba 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 โจ
Review checklist for @rasbt
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
paper.md
file include a list of authors with their affiliations?Review checklist for @Atcold
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
paper.md
file include a list of authors with their affiliations?