3 ms·

Two times I have published my research code - both times I have found many other papers/projects plagiarized my work without giving me any credit. This happens

by nicec2 5y ago

Two times I have published my research code - both times I have found many other papers/projects plagiarized my work without giving me any credit. This happens way more than you would think, especially if you are working under less known advisor, and at less known university. As the other comment said, if you care about "advancing the science", and won't mind stuff like the above happening, then go for it. In my experience, it is not worth it.

iamcreasy 5y ago
This in my experience as well. How did you find it out though?
vitorsr 5y ago
> Two times I have published my research code - both times I have found many other papers/projects plagiarized my work without giving me any credit. This happens way more than you would think, especially if you are working under less known advisor, and at less known university. This has been very much my experience.
jonnycomputer 5y ago
I wonder how often it is the case that code isn't considered an academic product per se, and so free to use. May have to make it very explicit.
- webmaven 5y ago
  > I wonder how often it is the case that code isn't considered an academic product per se, and so free to use. As an outsider with occasional glimpses into academia, I've observed a bimodal response: On the one hand, code seems to be seen as more available for reuse in terms of copy-and-paste, particularly in the exploratory phase. On the other hand, code reuse is somewhat less likely to trigger an acknowledgement and citation. This unacknowledged copy-and-paste borrowing of code seems in turn to be one influential factor inhibiting the derived code from being shared in turn. > May have to make it very explicit. That certainly can't hurt. I've certainly seen that reusable tools aren't cited as often as they are used, which in turn inhibits efforts from being made by academics in the production and refinement of such tools (the citation being the primary currency and reward mechanism for publication in academia). Explicitly asking for citations (and getting them) helps with that, though the more general issue of "releasing open source software isn't seen as 'publication' for academic status purposes such as being considered for tenure" remains a problem, though it varies considerably by field, institution, and department. But if given some thought and extra effort, a researcher might actually get more papers (possibly with different sets of collaborators) out of roughly the same body of work, especially if they look more broadly for appropriate conferences and journals. BTW, again as an outsider with occasional glimpses into academia, it seems to me that there are many vacant niches for cross-disciplinary journals and conferences focused on reusable assets such as datasets and tools necessary for research.

by nicec2 5y ago

iamcreasy 5y ago

This in my experience as well. How did you find it out though?

vitorsr 5y ago

> Two times I have published my research code - both times I have found many other papers/projects plagiarized my work without giving me any credit. This happens way more than you would think, especially if you are working under less known advisor, and at less known university. This has been very much my experience.

jonnycomputer 5y ago

I wonder how often it is the case that code isn't considered an academic product per se, and so free to use. May have to make it very explicit.

webmaven 5y ago
> I wonder how often it is the case that code isn't considered an academic product per se, and so free to use. As an outsider with occasional glimpses into academia, I've observed a bimodal response: On the one hand, code seems to be seen as more available for reuse in terms of copy-and-paste, particularly in the exploratory phase. On the other hand, code reuse is somewhat less likely to trigger an acknowledgement and citation. This unacknowledged copy-and-paste borrowing of code seems in turn to be one influential factor inhibiting the derived code from being shared in turn. > May have to make it very explicit. That certainly can't hurt. I've certainly seen that reusable tools aren't cited as often as they are used, which in turn inhibits efforts from being made by academics in the production and refinement of such tools (the citation being the primary currency and reward mechanism for publication in academia). Explicitly asking for citations (and getting them) helps with that, though the more general issue of "releasing open source software isn't seen as 'publication' for academic status purposes such as being considered for tenure" remains a problem, though it varies considerably by field, institution, and department. But if given some thought and extra effort, a researcher might actually get more papers (possibly with different sets of collaborators) out of roughly the same body of work, especially if they look more broadly for appropriate conferences and journals. BTW, again as an outsider with occasional glimpses into academia, it seems to me that there are many vacant niches for cross-disciplinary journals and conferences focused on reusable assets such as datasets and tools necessary for research.