Timeline for Publishing software in a convenient way
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:49 | history | edited | CommunityBot |
replaced http://academia.stackexchange.com/ with https://academia.stackexchange.com/
|
|
| Nov 28, 2016 at 23:51 | comment | added | E.P. | @user1420303 You can get a citable DOI from a release on GitHub, but I'm not sure that you will later on be able to get a citation count on it. You don't need to publish on a journal, though - you could just write documentation and upload it to the arXiv, which does get citation counts on Google Scholar if nothing else. | |
| Nov 28, 2016 at 20:20 | history | edited | Austin Henley | CC BY-SA 3.0 |
added 16 characters in body
|
| Nov 28, 2016 at 19:00 | vote | accept | user1420303 | ||
| Nov 28, 2016 at 18:55 | comment | added | Austin Henley | @user1420303 In the paper you could add a footnote with the github URL or a full reference. In the github repo, add a link to your paper in the readme. | |
| Nov 28, 2016 at 18:33 | comment | added | user1420303 | The second route fits better to my need. But I am unsure of how exactly to proceed. Lets say that I already have written the scientific manuscript that uses the code. How to link it with, let say github? Should the paper said that the code is in github? If someone find it in github, how does he know about the paper (for the citation)? | |
| Nov 28, 2016 at 18:26 | comment | added | Austin Henley | @user1420303 Writing a paper like that is one route (well suited for a workshop or industry track). The other route is to write a more standard research paper that contributes new knowledge but does so using your software (which people could in the future cite for its method/software). | |
| Nov 28, 2016 at 18:23 | comment | added | user1420303 | Sorry, I misunderstood you. You say that I should write an entirely new paper about the software. Yes, I was thinking in github repo or something like that. | |
| Nov 28, 2016 at 18:16 | comment | added | Austin Henley | @user1420303 The paper could either be written as (A) all about the system, how it works, and why it is better (if similar things exist) or (B) a scientific contribution that uses the program to achieve said contribution. You don't ask for citations, and they would cite the paper (and or the github repo), not a web page (unless you were referring to the github repo's page). | |
| Nov 28, 2016 at 18:14 | comment | added | user1420303 | Thanks. So, the steps would be: 1. Upload it to $X$. 2. Add some lines in the paper about what the software does. 3. Once published, ask for citation in the webpage $X$. Is that correct? | |
| Nov 28, 2016 at 18:09 | history | answered | Austin Henley | CC BY-SA 3.0 |