Answers.Body: <p>I am having trouble finding anything that directly addresses the issue of failed collaborations leading to scooping, but here are some examples of similar behavior:</p>
  <ul>
  <li><p>it is sort of implicit in the discussion <a href="https://drugmonkey.scientopia.org/2016/04/07/the-girl-who-cried-scoop/" rel="nofollow noreferrer">here</a>.</p>
  </li>
  <li><p>This question on <a href="https://academia.stackexchange.com/questions/88219/how-do-i-address-my-research-publication-being-scooped">academia SE</a> is related but not exactly right.</p>
  </li>
  <li><p>There are some related stories <a href="https://www.immpressmagazine.com/avoiding-the-scoop/" rel="nofollow noreferrer">here</a>.</p>
  </li>
  <li><p><a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3967854/" rel="nofollow noreferrer">Here is an article about plagiarism among collaborators</a>, which is quite similar.</p>
  </li>
  <li><p>I feel like a lot of <a href="https://advances.sciencemag.org/content/4/5/eaar2133" rel="nofollow noreferrer">the discourse around preprinting etc.</a> is similar but again not quite there.</p>
  </li>
  </ul>
  <p>As for punishment, that sounds hard. Scooping is sort of built into science; fighting over precedence is a big deal and has been for a long time. My solution would be to get rid of current academic publication and have everyone's open digital lab notebooks streaming results to publication feeds in real time; that way there's no ambiguity. Preprints and <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5836261/" rel="nofollow noreferrer">micropublications</a> are sort of a poor man's version of this.</p>
  <p>This is not a very complete answer but there may be enough there to help.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-11-21T18:25:37.253Z
Answers.Text: Thanks, excellent points. Just to add some extra in terms of GeneMatcher. Most collaborations flowered and only a few sour. Someone else has had a similar experience to my colleague, so it is not uncommon. The solution is to use `collaboration agreements` to safeguard against this —even if these are laughably enforceable.
Answers.UserDisplayName: Matteo Ferla
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-11-21T18:15:55.703Z
Answers.LastActivityDate: 2020-11-21T18:15:55.703Z
Answers.UserDisplayName: Maximilian Press
Body: <p>A colleague has uploaded about a dozen candidate disease genes to GeneMatcher, described <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4833888/" rel="nofollow noreferrer">here</a> and <a href="https://www.nature.com/articles/s41436-018-0383-z" rel="nofollow noreferrer">here</a> and located <a href="https://genematcher.org/" rel="nofollow noreferrer">here</a>,  with excellent success. However last year and again recently he has encountered the case wherein a case was uploaded and a cohort formed, but a few months down the line one of the dropped out collaborators published an n=1 paper in a low tier journal, basically using GeneMatcher to check whether the disease link of the gene was legitimate, to assess the phenotypic range and see what test are worth doing.</p>
  <ul>
  <li>Is there documented precedence of this behaviour (preferably citable)? If not,</li>
  <li>does anyone have personal experience of this and what is the ratio of incidences over total submissions (I know that is hearsay, but it would be very helpful)?</li>
  <li>And also has anyone successfully taken action (say getting user barred)?</li>
  </ul>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-11-20T23:55:41.603Z
Comments.Text: when you say "this behavior", do you mean an ex-collaborator trying to rush a part of the collaborative project into print to get credit? that is very common. Are you referring more narrowly to this behavior on the GeneMatcher platform?
Comments.UserDisplayName: Maximilian Press
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-11-21T11:56:07.000Z
Comments.Text: I was not aware that is common in general for a collaboration to be formed only for the collaborator to drop out and rush to press with the intel. Turns out there are lots of collaboration agreements to protect against shenanigans in joint works which are similar to MTAs. Sickening as it sounds this is the solution.
Comments.UserDisplayName: Matteo Ferla
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-11-21T18:00:09.290Z
Comments.Text: I think that often collaborator starts with good intentions, but then the team falls apart and stop liking each other, and they still want to get something out of the work. There are a few ways it can happen. Never happened to me personally (at least not like this specifically). But anecdotally, I'd guess this is actually one of the most common paths to scooping.
Comments.UserDisplayName: Maximilian Press
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-11-21T18:11:17.740Z
Comments.Text: Ah, no, this is more malicious. The site matches geneticists and they exchange patient details in chain emails, discuss a path to publication (agreed by all) and make the clinicians request further analyses say MRIs or blood work (within 2-3 months). Then when follow-up lab tests are planned, the collaborator suddenly goes silent and half a year later there is a paper in a low tier journal with their sole patient but with strong emphasis on the key traits discussed on in the collaborations.
Comments.UserDisplayName: Matteo Ferla
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-11-21T18:17:03.890Z
Comments.Text: Ah, I see. that is a more specific and very bad behavior.
Comments.UserDisplayName: Maximilian Press
Tags: <gene><mutations><publishing>
Title: Scooping and GeneMatcher
ThreadText: # Scooping and GeneMatcher
  
  (Asked by: username_0 on 2020-03-02)
  
  A colleague has uploaded about a dozen candidate disease genes to GeneMatcher, described [here](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4833888/) and [here](https://www.nature.com/articles/s41436-018-0383-z) and located [here](https://genematcher.org/), with excellent success. However last year and again recently he has encountered the case wherein a case was uploaded and a cohort formed, but a few months down the line one of the dropped out collaborators published an n=1 paper in a low tier journal, basically using GeneMatcher to check whether the disease link of the gene was legitimate, to assess the phenotypic range and see what test are worth doing.
  
  * Is there documented precedence of this behaviour (preferably citable)? If not,
  * does anyone have personal experience of this and what is the ratio of incidences over total submissions (I know that is hearsay, but it would be very helpful)?
  * And also has anyone successfully taken action (say getting user barred)?
  
  **Tags:** gene, mutations, publishing
  
  > **Comments:**
  > **username_1**: when you say "this behavior", do you mean an ex-collaborator trying to rush a part of the collaborative project into print to get credit? that is very common. Are you referring more narrowly to this behavior on the GeneMatcher platform?  
  > **username_0**: I was not aware that is common in general for a collaboration to be formed only for the collaborator to drop out and rush to username_1 with the intel. Turns out there are lots of collaboration agreements to protect against shenanigans in joint works which are similar to MTAs. Sickening as it sounds this is the solution.  
  > **username_1**: I think that often collaborator starts with good intentions, but then the team falls apart and stop liking each other, and they still want to get something out of the work. There are a few ways it can happen. Never happened to me personally (at least not like this specifically). But anecdotally, I'd guess this is actually one of the most common paths to scooping.  
  > **username_0**: Ah, no, this is more malicious. The site matches geneticists and they exchange patient details in chain emails, discuss a path to publication (agreed by all) and make the clinicians request further analyses say MRIs or blood work (within 2-3 months). Then when follow-up lab tests are planned, the collaborator suddenly goes silent and half a year later there is a paper in a low tier journal with their sole patient but with strong emphasis on the key traits discussed on in the collaborations.  
  > **username_1**: Ah, I see. that is a more specific and very bad behavior.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-11-21. Score: 1 | Accepted answer
  
  I am having trouble finding anything that directly addresses the issue of failed collaborations leading to scooping, but here are some examples of similar behavior:
  
  * it is sort of implicit in the discussion [here](https://drugmonkey.scientopia.org/2016/04/07/the-girl-who-cried-scoop/).
  * This question on [academia SE](https://academia.stackexchange.com/questions/88219/how-do-i-address-my-research-publication-being-scooped) is related but not exactly right.
  * There are some related stories [here](https://www.immpressmagazine.com/avoiding-the-scoop/).
  * [Here is an article about plagiarism among collaborators](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3967854/), which is quite similar.
  * I feel like a lot of [the discourse around preprinting etc.](https://advances.sciencemag.org/content/4/5/eaar2133) is similar but again not quite there.
  
  As for punishment, that sounds hard. Scooping is sort of built into science; fighting over precedence is a big deal and has been for a long time. My solution would be to get rid of current academic publication and have everyone's open digital lab notebooks streaming results to publication feeds in real time; that way there's no ambiguity. Preprints and [micropublications](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5836261/) are sort of a poor man's version of this.
  
  This is not a very complete answer but there may be enough there to help.
  
  > **Comments:**
  > **username_0**: Thanks, excellent points. Just to add some extra in terms of GeneMatcher. Most collaborations flowered and only a few sour. Someone else has had a similar experience to my colleague, so it is not uncommon. The solution is to use `collaboration agreements` to safeguard against this —even if these are laughably enforceable.  
  
  ---
  
  