Skip to content

Document zenodo deposits#1547

Open
sneakers-the-rat wants to merge 9 commits into
openjournals:mainfrom
sneakers-the-rat:docs-zenodo
Open

Document zenodo deposits#1547
sneakers-the-rat wants to merge 9 commits into
openjournals:mainfrom
sneakers-the-rat:docs-zenodo

Conversation

@sneakers-the-rat

Copy link
Copy Markdown
Contributor

Finishing up a review, about to ask the author to make the archival deposit, and noticed we didn't have docs for this.

Zenodo's docs are pretty clear but they are across many different pages, so I just tried to link to them and give a very very brief summary that links out to the relevant sections.

Made a new "post review" section and moved the post-review parts of the "review process" section there, similar to prior changes to editorial guide.

Comment thread docs/_static/css/joss.css
Comment on lines +9 to +10
a code {
text-decoration: underline;

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

regular links aren't underlined, but without this, links with backticked text (like the .zenodo.json link) are indistinguishable from non-link text.

Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
sneakers-the-rat and others added 3 commits May 21, 2026 12:08
Co-authored-by: William Gearty <willgearty@gmail.com>
Co-authored-by: Daniel S. Katz <d.katz@ieee.org>
Comment thread docs/submitting.md Outdated
@sneakers-the-rat

Copy link
Copy Markdown
Contributor Author

Scope of this PR has changed a bit from "provide docs for how to use zenodo" to "how to make the archival deposit," sorry about that, but i think we really do need a bit of clarity on this part of the process because there is a lot of potential gray area, and it's important to ensure the ability for JOSS publications to be usable/understandable as scholarly archival records in the long run.

Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Comment thread docs/submitting.md Outdated
Co-authored-by: Daniel S. Katz <d.katz@ieee.org>
@warrickball

Copy link
Copy Markdown
Contributor

I haven't had a chance to really think about where to include this but I think it's worth noting that post-review changes to the paper do not require an update to the software archive. I routinely tweak papers (or ask the authors to do so) between recommend-accept and accept.

@sneakers-the-rat

Copy link
Copy Markdown
Contributor Author

sounds more like editorial/eic guide to me? not something that would typically be relevant to authors, but would be relevant to editors/eics asking for edits

@warrickball

Copy link
Copy Markdown
Contributor

But authors sometimes ask. As in, they make changes to the paper and then say "oh do I need to update the archive?"

@sneakers-the-rat

Copy link
Copy Markdown
Contributor Author

But authors sometimes ask. As in, they make changes to the paper and then say "oh do I need to update the archive?"

alright, how about this 9e01419

anything else needed here? have had to refer to this twice when doing editorial checks, would be good to get it live!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants