Timeline for Publishing outside of my PhD Research
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 15, 2015 at 21:55 | comment | added | BrianH | @SashoNikolov That's a good question about IP and research - and I don't know the answer! Since people don't need the university sign-off on publishing generally, I don't know where the lines are drawn in such a matter. I imagine it has something to do with the difference in copyright and IP ownership and licensing. | |
| May 15, 2015 at 20:57 | comment | added | ham-sandwich | @SashoNikolov Sorry, just to clarify the code nor the knowledge is yet in the public domain. The codebase was developed in my own time, using my home equipment. However, the problem itself couldn't have been solved without inspiration from my in work research. It's a predicament which I have chosen to approach the university about. Thank you for all your responses. | |
| May 15, 2015 at 20:48 | comment | added | Sasho Nikolov | @BrianDHall that makes sense, but it applies to the code, which it seems OP has already released to the public (and that might be a problem, I agree). But am I mistaken that IP issues do no apply to research publications? | |
| May 15, 2015 at 20:42 | comment | added | Mr. Mascaro | @SashoNikolov, if any work was done on the project during paid working time or the code was written on a university PC or the code is based upon current, unpublished research it could definitely involve IP litigation if this side project were to be commercialized at some point. | |
| May 15, 2015 at 19:44 | comment | added | BrianH | @SashoNikolov This is somewhat based upon the country, but in many areas it is not uncommon that one of the legal employment documents one signs to join the program include assumptions of intellectual property ownership being held by the University (or jointly with it). Therefore releasing source code or other such research products could run afoul of the agreements one has already signed. It's often easy-enough to deal with this, but if you don't know such agreements exist then you could get yourself into some unpleasant disagreements. | |
| May 15, 2015 at 19:01 | comment | added | Sasho Nikolov | I do not understand either of your points. Sure, ham-sandwich should make sure to fulfill his obligations to his advisor and/or whoever is funding him. But as long as he does that, I don't think the advisor needs to be informed about side projects. It's probably better to be open and upfront about such things, but not necessary if they are not getting in the way of paid work. I am even more puzzled about the IP comment. The question is about publishing and not about distributing code, and this is the first time I hear about checking with the IP office before you publish something. | |
| May 15, 2015 at 16:46 | vote | accept | ham-sandwich | ||
| May 15, 2015 at 16:42 | history | answered | aeismail | CC BY-SA 3.0 |