Timeline for How to manage a colleague in your research group taking your idea?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 24, 2021 at 16:06 | comment | added | Captain Emacs | Perhaps I should partially agree with Spark and should make my statement more precise by not saying not to share at all, but to be careful who to share with and to keep good ideas to only select few trusted people. The department structures seem to sail precariously close to possible misconduct ("has the support of a senior member of the group [with] the power to block me"). This is not enough evidence for systemic violations, but the scooper seems to have got away with a history of such tactics. Care is advised. | |
| Jan 24, 2021 at 16:02 | comment | added | Captain Emacs | If someone with lots of threads of research, loses one thread to a scooper it's not a major issue, if annoying. However, if one has few, crucial lines of research (which is more likely for young academics) and the scooper indulges in a systemic appropriation of other people's ideas, then I quite disagree with you. In the worst scenario, the scooper could actually accuse OP of plagiarising them, trying to lock OP out of their own field. This is not a theoretical situation. I am the first to acknowledge parallel discoveries, but this case here smells bad ("known for such tactics"). | |
| Jan 24, 2021 at 12:24 | comment | added | Spark | I don’t know if this is good long term advice. Unless their department is a cesspool of misconduct, hindering collaboration due to one bad apple will hurt them academically. | |
| Jan 24, 2021 at 2:35 | comment | added | Captain Emacs | "On paper". Yes, things like that are hard to prove, but for a young researcher, this can be quite frustrating. OP should better protect their ideas in the future, e.g. by keeping them to themselves. | |
| Jan 23, 2021 at 23:53 | history | answered | Spark | CC BY-SA 4.0 |