anchor.diff:  
   TODO add example of getting validation results
   
  -== Updating a sample
  +=== Updating a sample
   
   If you want to change a sample record after you've created it, you should use a `PUT` request to replace the record:
   
   include::{snippets}/update-sample/curl-request.adoc[]
   
  -include::{snippets}/patch-sample/http-response.adoc[]
  +include::{snippets}/update-sample/http-response.adoc[]
   
   Updating a document will cause it to be re-validated, as described above.
   
  
positive.code: 
  == Pick a team
  
  Every submission is owned by a _team_. At this stage of development, the API doesn't restrict what team you use.
  A future update will add support for team membership and administration. Until then, you can use any team name you like.
  
  A team object is structured like this:
  
negative.code: 
  == Adding assays
  
  Assay documents describes the processes performed on the sample to produce data. For example, this could be library
  preparation and sequencing for an NGS study. If you are familiar with the ENA SRA submission system, an assay is equivalent to an Experiment.
  
  TODO add an assay
  
  == Adding assay data
  
  If you are familiar with the ENA SRA submission system, assay data is equivalent to a Run.
  
  TODO add assay data
  
  == Finalising your submission
  
  Update the submission status to 'Submitted'.
  
  == Tracking progress
  
  Access the status report to see how the submission
  
  
  == When things go wrong
  
  