This is why I've given up trying to work in the field or found a company in the sector... Anyone with an idea and need a technical cofounder? ;)
This is why I've given up trying to work in the field or found a company in the sector... Anyone with an idea and need a technical cofounder? ;)
In the long run I see such system emerging and being successful, and eventually replacing everything else. Needless to say it will take a lot of time though to popularize it.
What do you think? Could this be done?
The real tragedy is the general reference, social science, and humanities journal diaspora where the usage and demand has skyrocketed with the increased access online resources allow to lay researchers. The science journal communities are way ahead in self-sufficiency in adapting, and are increasingly open to the corrupt state of publishing and alternate community publishing platforms.
I'm way more interested in informal discussion of interesting papers and news than anything else.
As everyone else has mentioned, the big issue is getting a large community. So what would be really cool would be to figure out how to do something like HN or SO without active involvement by a large community. In my field there's a lot of discussion/review/etc of working papers and published results, but it's all scattered across different blogs and commenting systems. Plus papers build on each other and some are clear replies to other research. If you could take that sort of dispersed discussion and put it into an HN or reddit style threaded view that was available at one spot (or an SO style question and answer format, if you prefer), that would be awesome.
edit: typo
Arxiv even has a paid fellowship, but it is postdoc wages, not professional wages.
So there's an ongoing transition now by researchers/editorial boards/etc to move to a system with lower access costs (some of which involves taking back journal ownership, some doesn't). There's some logistical overhead and fixed costs, but those are falling. It seems like in 20 years (conservatively) all new research will be available to whomever wants it no matter what Elsevier or other companies do in the meantime (the papers may not be literally free, but affordable).
So, like I said initially, I can see how some software for logistics or communication would be helpful, but the main issues don't strike me as technical.
Is it a "technical issue"? No, but neither is booking your flight via phone, that worked just fine. Could it be made much better, more accessible, cheaper, and overall better via technology. Yes.
Maybe you could give details about what you mean by "antiquated idea behind publishing" because I'm pretty sure what I described is not 1970s speed. Now, if your point is that what I've described is not common practice, I agree completely. But that means that people need to be persuaded to use existing technical tools -- I can't see a specific step that's going to be a significant pain point (I'll grant that not everyone can/will use github, but uploading a zip archive of the paper's directory to a personal webpage is easy and is almost as good for code and data dissemination).
Other anecdotes are blogs that announce and discuss new research:
http://johnhcochrane.blogspot.com/2012/10/nber-asset-pricing...
http://johnhcochrane.blogspot.com/2012/09/woodford-at-jackso...
That is legitimate academic discourse, put out by an extremely established and credentialed economist, almost instantly. On blogger.
My viewpoints are limited to life sciences, where people have no idea what FTP means, let alone GIT. Also, what you did is not typical, people (at least in my field of neurobiology) have no intention of doing something like that in fear of being scooped. The antiquated idea behind publishing is the concept of doing an experiment, filtering out all the negative data, and then submitting their positive data to a journal that they think will publish their data. We've been waiting for 7 months now for a paper to get published in PNAS due to this antiquated process. 7 months to do what you did in a few minutes uploading your data online and making it public.
Meanwhile, 'search' as we know it rules the world and is the driving force enabling the entire tech industry. It wouldn't be hard to throw a little effort in building out their platforms, but there's no competition to force further development in their products.
Elsevier in particular is spending ridiculous amounts on internal research & acquisitions for its platform (called SciVerse, http://www.hub.sciverse.com/), following the latest advancements in machine learning and NLP for data mining, etc etc.
They also host competitions for start-ups and developers to produce new apps for their platform.
These businesses may be unethical and not to everyone's liking, but they are not stupid.
This would add real value to the scientific publishing and simply help the researchers to find what they need.
I don't think this is a technical issue. Journals make mistakes on which papers to publish all the time, even when the referees work hard and take the review seriously, so this is hard for committed people to do well.
There are some arguments for both approaches, but I believe that the double-blind approach is much better.
Project: Very briefly, I'm working on collecting raw data (positive AND negative), indexing it, and making relationships between datasets. For example, my neuroscience study has relationships to cancer biology, so the data presented to the user would include results from both.
Re: Publishing, I'm going to provide raw data to scientists and create a venue for them to "blog" about these datasets. I think science needs to move incrementally (at internet speed) and get away from taking 3 years to produce a study and publishing a big paper of only positive data. Also, I'd like for the "peer review" portion to be more transparent, so that we can avoid the insane bias that goes into peer review.
Goal 2: Create "big data" by combining small academic science results into a big ass database. Meta data could be the new preliminary data for academic grants.
So yeah, if anyone is interested in playing with this, let me know. klg2142 @t columbia.edu
A couple years ago, I spent many nights and weekends working on the academic publishing problem. The effort culminated in a massive hypermedia-style XML schema for distributed and inter-connected publishing, referencing, archiving, etc. There were hundreds of elements just in the common metadata model before I even got around to defining content modules.
Then something hit me like a ton of bricks. I think it was seeing backbone.js for the first time. I realized how quickly web technology was moving forward, how easy it was becoming, and, by contrast, how absolutely shitty it was going to be to write mountains of XSLT on top of my huge DTD. Even in my attempt to create something really different, my approach was still totally clouded by the prevailing anti-wisdom of the academic publishing technology community.
I realized I was on the wrong path. It was a great thought exercise that contributed immeasurably to my day work, but I had to move on.
Happy to share more information if you like, though I'd need to dig the files out of deep storage.