Mobile // Mobile Applications
News
3/17/2014
09:06 AM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Code You Can Quote

GitHub, FigShare, and Mozilla join forces to make programming code fit for academic citation.

"Software is eating the world," declared entrepreneur Marc Andreessen in 2011, arguing that software-based businesses will disrupt many industries in the years to come.

Nowhere is that disruption more apparent than in academia, where online courses are transforming established traditions of education and even non-technical academic disciplines are becoming increasingly data-driven.

But software poses a problem in a world founded upon literature and published research: It isn't easily cited in a way that's meaningful to academic standards and expectations. At the same time, as more and more research papers and projects incorporate and rely upon computer code, researchers who create code find their career prospects constrained when their contributions are not documented in the accepted manner.

"Every level of academia is becoming more computational," explained Mark Hahnel, founder of FigShare, in a phone interview. "There are a lot of post-docs who create code but don't get credit for their work."

To help remedy the situation, FigShare, on online research sharing and citation service, has partnered with online code repository GitHub and Mozilla Science Lab, a Mozilla Foundation project supporting open science, to help those who write software get credit for their code in published research.

Through the partnership, programmers will be able to archive code created for research projects in a public GitHub repository and receive a citable digital object identifier (DOI) through FigShare. The resulting code will thus represent "research output" and will exist in a publicly accessible space where it will be available for reuse, to reproduce experimental results if necessary.

However, traditional publications don't make it easy to reproduce experiments. "A significant portion of research is technically impossible to reproduce," says Kaitlin Thaney, director of Mozilla Science. A reliable way to cite the code used in experiments could change that.

[But will this help Windows XP users? Read Windows XP Goes Dark: 5 Things To Expect.]

Hahnel observes that the initiative comes at a time when there's a push, particularly in government and policy circles, to make data more available. Last month, PLOS announced a new data-sharing policy for its various journals: "Authors must make all data publicly available, without restriction, immediately upon publication of the article."

With any luck, DOI-documented code will help ensure that experimental output is scientifically meaningful rather than dubious data.

Image Credit: Kjetil Korslien
Image Credit: Kjetil Korslien

It turns out there's quite a bit of dubious data: Nature last month reported that publishers Springer and IEEE decided to withdraw more than 120 papers from their subscription services after a French researcher found the works were "computer-generated nonsense." The papers were generated by software called SCIgen, created by MIT researchers in 2005 to demonstrate that academic conferences would accept gibberish.

Software may be eating the world, but blame human nature for the quality of the food.

Thomas Claburn has been writing about business and technology since 1996, for publications such as New Architect, PC Computing, InformationWeek, Salon, Wired, and Ziff Davis Smart Business. Before that, he worked in film and television, having earned a not particularly useful ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Michael Endler
50%
50%
Michael Endler,
User Rank: Author
3/17/2014 | 5:55:13 PM
Awesome Idea
When I was in grad school not so long ago, standards were still changing regarding how to handle even simple tech citations, such as websites and digital media. Had I wanted to write an essay that involved heavy analysis of code (and I can think of reasons that might have been interesting), I can only imagine how clumsy and unwieldy the result would have been, lacking as I would have been in standards and resources for doing so. The better we enable scholars and other interested parties to discuss and analyze code, the better off we'll be.
Yuschick
50%
50%
Yuschick,
User Rank: Author
3/17/2014 | 3:04:30 PM
Great Step Forward
I find this to be a great step forward.  Programmers and their code are solving problems with modern, technical solutions.  These solutions to realworld problems should be able to be wuoted and referenced in a similar fashion as testimonies or research articles in medical magazines.  I have can see Node.js becoming a language that will be referenced as well as its poential for large-scale solutions is great.
Building A Mobile Business Mindset
Building A Mobile Business Mindset
Among 688 respondents, 46% have deployed mobile apps, with an additional 24% planning to in the next year. Soon all apps will look like mobile apps – and it's past time for those with no plans to get cracking.
Register for InformationWeek Newsletters
White Papers
Current Issue
InformationWeek Tech Digest September 18, 2014
Enterprise social network success starts and ends with integration. Here's how to finally make collaboration click.
Flash Poll
Video
Slideshows
Twitter Feed
InformationWeek Radio
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.