/joss

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TRACKING: Archiving JOSS content #495

Open
arfon opened this Issue Feb 7, 2019 · 6 comments

Comments

Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
4 participants
@arfon @labarba @danielskatz @gforsyth
@arfon
Copy link
Member

arfon commented Feb 7, 2019

There are a couple of things we should probably be doing to archive JOSS content for the long-term:

Archiving reviews

As discussed in #269 & #490, this could be some kind of script that attempts to pull the comments for the review and deposit them as an archive in e.g. Zenodo. We would presumably then link to this review archive in the paper.

Alternatively we could use archive.org to create snapshots of the review page (e.g. https://web.archive.org/web/20190207112842/https://github.com/openjournals/joss-reviews/issues/1207) - it looks like this could be done programmatically https://archive.readme.io/docs/creating-a-snapshot .

Archiving papers

We should probably use CLOCKSS to archive the papers from JOSS. This would require a fee of ~$250 per year and also for us to be generating JATS XML (which we currently don't).

FWIW, it's also possible to archive the papers with archive.org but it's not clear to me if this is better or worse than CLOCKSS: https://web.archive.org/web/20190207113237/http://joss.theoj.org/papers/10.21105/joss.01027 & https://web.archive.org/web/20190207113247/https://www.theoj.org/joss-papers/joss.01027/10.21105.joss.01027.pdf

@arfon arfon added the enhancement label Feb 7, 2019

@labarba

This comment has been minimized.

Sign in to view
Copy link
Member

labarba commented Feb 7, 2019

CLOCKSS offers a full-featured service that includes public release under a Creative Commons license after a journal goes under, and it has the respect of librarians and publishers across the globe. I support joining CLOCKSS.
@labarba

This comment has been minimized.

Sign in to view
Copy link
Member

labarba commented Feb 7, 2019

Ping @gforsyth 👋 — You wrote a script to download an issue thread into a markdown file, no? (to grab our review tracking for the inexact-gmres paper?) Do you have that script handy?
@arfon

This comment has been minimized.

Sign in to view
Copy link
Member

arfon commented Feb 7, 2019

CLOCKSS offers a full-featured service that includes public release under a Creative Commons license after a journal goes under, and it has the respect of librarians and publishers across the globe. I support joining CLOCKSS.

Me too. I wonder if CLOCKSS supports archiving reviews too? I'll get in touch with them and start exploring adding Open Journals to CLOCKSS.
@danielskatz

This comment has been minimized.

Sign in to view
Copy link
Collaborator

danielskatz commented Feb 7, 2019

It feels like the JATS part would also be good in general, though I'm not sure exactly why.
@arfon

This comment has been minimized.

Sign in to view
Copy link
Member

arfon commented Feb 7, 2019

It feels like the JATS part would also be good in general, though I'm not sure exactly why.

Yes, this would allow us to be indexed in PubMed.
@gforsyth

This comment has been minimized.

Sign in to view
Copy link

gforsyth commented Feb 7, 2019

Do you have that script handy?

It might be somewhere on theo? Probably simpler just to rewrite it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment