I am highly skeptical of the CHORUS system proposed by scientific publishers as an end run around PubMed Central

Just read this news story … Scientific Publishers Offer Solution to White House’s Public Access Mandate – ScienceInsider

It reports on an effort by various scientific publishers to create something they call “CHORUS” which stands for “Clearinghouse for the Open Research of the United States.” They claim this will be used to meet the guidelines issued by the White House OSTP for making papers for which the work was supported by federal grants available for free within 12 months of being published.

This appears to be an attempt to kill databases like Pubmed Central which is where such freely available publications now are archived.  I am very skeptical of the claims made by publishers that papers that are supposed to be freely available will in fact be made freely available on their own websites.  Why you may ask am I skeptical of this?  I suggest you read my prior posts on how Nature Publishing Group continuously failed to fulfill their promises to make genome papers freely available on their website.

See for example:

We need to make sure such papers are freely available permanently and the only way to do this is via making them available outside of the publishers own sites.  Pubmed Central seems to be a good solution for this.  I would be happy to hear other possible solutions – but leaving “free” papers under the control of the publishers is a bad idea.

UPDATE 6/27/2013

Saw this Tweet

//platform.twitter.com/widgets.js Seemed potentially really interesting. Read the story and got pointed to a new Nature paper on the ancient horse genome. I guess not so surprisingly, despite the fact that they report a new genome sequence, it is not openly available. We really cannot trust Nature on this can we? They could say “Well, this is a draft genome, and we did not mean to apply our policy to draft genomes.” Well, that would be weird since, well, they have applied this to draft genomes before. And then I decided to search for other examples … and in about ten minutes I found a few. See

//platform.twitter.com/widgets.js

//platform.twitter.com/widgets.js