As predicted, the popular and useful Social Sciences repository SSRN, having been acquired by Elsevier, is now being destroyed. Papers are being quietly vanished from SSRN, without their authors even being notified. This is happening even in cases when the copyright is held by the authors (who posted them, giving implicit permission for them to be redistributed), and even more astonishingly when papers are under Creative Commons licences. Details at PrawfsBlawg.

These are not the actions of a publisher acting in good faith.

6a00d8341c4eab53ef01bb09011389970d-800wi

As James Grimmelmann comments:

There’s no longer a point in deterring SSRN. Its new owners at Elsevier have made their true colors clear, and we as a community canot afford to centralize our scholarly communications in the hands of for-profit publishers.

It is time to depublish all of our articles from SSRN and walk away completely. It doesn’t matter if they reverse course now. We can’t trust them in the long run. It’s time to walk away from SSRN.

And as Tony Ross Hellaur puts in, an another comment on the same post (emphasis mine):

Anybody who bought Elsevier’s line that “both existing and future SSRN content will be largely unaffected” following the sell-off should now wake up. Elsevier is aggressive in enforcing copyright, and have the resources and scale to be able to make extreme judgements on what constitutes copyright violation and then to put the burden of proof on individual researchers to show otherwise.

The good news: Brandon Butler points out in the comments that there is a new and open alternative to SSRN: Announcing the development of SocArXiv, an open social science archive. SocArXiv has some very good people behind it. I hope it takes off, and that the zombie SSRN is rapidly defleshed.

Update (29 December 2017)

As requested by SSRN themselves, I am updating to note that it seems nothing has changed at SSRN so far. Brett D. Currier‏ pointed out that SSRN is now charging $38 to download some of its papers, but as Tom Reller pointed out, they have in fact always done this. I don’t know whether such articles have always been presented in a way that encourages you to pay $38 for the publisher’s formatter version, and hides the free version behind a misleading “There are 2 versions of this paper” message (which i assumed meant an original submission and a revised version), but that’s how they do it now. (Does anyone who used to use it back in the day remember if it was always thus?)

 

A few months ago I got an email from Nathan Myers, who asked me:

Do you have advice for someone who wants to spin up a new OA journal? Is there automation for the boring parts? Is someone you know well versed in what to do?

In many ways, I’m the wrong person to ask: I’ve never started a journal, OA or otherwise, nor even served on an editorial board.

But, hey, I’m not one to let something like that stop me. So here’s what I told Nathan. I’m sure I missed a lot of important possibilities: please point them out in this comments. I’ll try to keep this post updated as the landscape changes.


There are several good options at this point.

The simplest and cheapest is probably to use Annotum, a WordPress plugin that helps with the review workflow. I’ve not used it myself, but I know it’s what PLOS Currents uses, so it’s obvious battle-ready. I’m not sure but I think you can use it as a theme in a wordpress.com-hosted free blog.

Scholastica offers very low-cost support for running an overlay journal, as for example the recently launched Discrete Analysis: see Tim Gowers’ blog-post about the new journal.

Open Journals Systems is a widely used software package for running open-access journals — IIRC they have more that 10,000 running installations worldwide. I’ve not used it, but it evidently has what it takes.

If you have some funding to cover production charges, or are able to charge an APC, you can use a full-service option from a low-cost OA publisher such as Ubiquity Press.

PeerJ’s system is widely liked — very easy for authors and reviewers to use. Its software is all on GitHub, though I think some work would be needed to tie it all together. If you have the software engineering chops, this may be the best option for performance/price ratio.

What else?