anchor.diff:  include::{snippets}/create-sample/http-response.adoc[]
   
   
  -== Naming samples (and everything else)
  +=== Naming samples (and everything else)
   
   Samples, like all the documents that you add to a submission need to have an _alias_. This field is the name used for
   the record within the submission system. Each alias should be unique within the records of that type owned by a team.
   Using an alias for a second time in another submission will cause the record to be overwritten.
   
  -== Sample documents
  +=== Sample documents
   
   The description of a sample should normally include a taxonomic code to describe the species classification. This should
   be an entry from the taxonomy database curated at https://www.ncbi.nlm.nih.gov/taxonomy/[NCBI]. EMBL-EBI provide a
  
positive.code: 
  == Adding assays
  
  Assays
  
  If you are familiar with the ENA SRA submission system, an assay is equivalent to an Experiment.
  
  
  == Adding assay data
  
  If you are familiar with the ENA SRA submission system, assay data is equivalent to a Run.
  
  == When things go wrong
  
  
negative.code: 
  == Pick a team
  
  Every submission is owned by a _team_. A team is a group 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:
  