Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Support some form of issue tracking #331
Issues in Scirate?
Scirate enables us to express comments/opinions on published works. Another very useful kind of feedback for research papers is issues. By "issue" I mean exactly the kind of thing I'm writing right now: a description of
This differs from comments which are just statements of opinion which don't require any reaction from the author. We all know that issues are essential in developing software, and based on a recent experience where I used github to host development of a research paper with three coauthors and more than a dozen group members providing feedback, I think that issues should also be used for research papers.
It might be nice to attach an issue tracker to Scirate, or at least have Scirate give links to an external issue tracker attached to each paper.
Why not just use a public github repo and get the issue tracker for free?
Making a github repo public makes everything public, including any sensitive information including comments about particular works/people. Having written a paper using github, I can imagine the authors would not want to make that repo public before going through the entire issue history making sure nobody said anything embarrassing/demeaning/etc. about anyone else or any other works. I think this is more of a problem in scientific publishing than in open source software because of the competitive nature of research and publishing in academia. As evidence, I proposed everyone in science using public github repos for their papers to a colleague, and he said he'd never do it because of the increased chance of being scooped and the obvious problems with the public seeing referee reports.
So, it seems the best system would be for the authors to use a git repository (and an issue tracker!) for their own purposes, and to then release only curated versions of the finished work for public consumption. Of course, the repository for storing curated versions of published works is spelled "arXiv". Therefore, I think it would be nice to have an issue tracker for scientific works which points at arXiv versions. For example:
The author would respond to this issue by fixing the problem, releasing a new version on arXiv, and marking the issue as fixed.
Since Scirate already points at arXiv and is already in good use in quantum information (a field I care about), I'm wondering if it would be useful to add this sort of issue tracker to Scirate.
I just got an email from a colleague which reads roughly like this:
The email came with a link to the paper on arXiv.
My reaction was to offer to review the parts of it on which I think I have expert knowledge and put together some kind of joint review with my colleague. In other words, I'd like to respond to particular parts of the paper. It will take work for my colleague and I to coordinate our feedback into some kind of cohesive review.
If only there were some service which hosted reviews/issues for papers published on arXiv...
It looks like orcid has this kind of functionality. (See https://arxiv.org/user/confirm_orcid_id ) We could link scirate accounts to orcid accounts but that sounds like a bit of a pain. aram…
On Sun, Nov 27, 2016 at 4:19 PM, Daniel Sank ***@***.***> wrote: From Paul Ginsparg at arXiv, regarding how to indicate ownership of arXiv submissions. short answer is "i don't know" (but which probably means "no", depending what you mean by "easy"). (there's of course a clunky way, which would involve the 3rd party sending an email to the address listed on abstract, providing a confirm token, but i wouldn't with that on anyone, not to mention someone receiving email might click on it automatically and erroneously give authority). the closest i think is to start with an "author_id" and claim your articles (see https://arxiv.org/help/author_identifiers ) then possibly some service could be built on top of that. there's still the question of how to convince 3rd party you're the owner of that author page (suggestions?) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#331 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABwIQYiI_HweQWLpcCGzSolUimAfgs7Vks5rCfPIgaJpZM4KhneO> .