anchor.diff:  
   You don't need to worry about most of those links for now, we'll learn about them as we go.
   
  -== Pick a team
  +== Create a submission
  +
  +The submission system allows you to build up your submission over time and send it to the archives when you are ready.
  +The first step is to create a submission.
  +
  +=== Pick a team
   
   Every submission is owned by a _team_. A team is a group of people, working together on the same data. How you use this
  -is up to you. You could create a team for just yourself, everyone in a lab, or one for all collaborators on 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:
  +is up to you. You could create a team for just yourself, everyone in a lab, or one for all collaborators on a project.
  +
  +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 document is structured like this:
   
   `{"name" : "my-team"}`
   
   At present, you also need to provide a submitter object when creating a submission. In future versions this will be
  -taken from your log in information, but for now you need to provide a submitter object:
  +taken from your log in information, but for now you need to provide a submitter document:
   
   `{"email": "alice@example.com"}`
   
  -== Create a submission
  +=== POSTing a submission
   
   Using the link labelled `submissions:create`, `POST` a document containing a team and a submitter to create
   a submission:
  
positive.code: 
  include::{snippets}/create-submission/http-response.adoc[]
  
  The `location` header in the response has the URL for the created submission. You will need this when adding things to the submission.
  
  == Add samples
  
  Using the link from the submission labelled `samples:create`, `POST` a sample object:
  
  include::{snippets}/create-sample/curl-request.adoc[]
  
  
  Note that the submission field above contains the URL to the submission, this allows the records to be linked together.
  
  This will return a response to show that the sample record has been created:
  
  include::{snippets}/create-sample/http-response.adoc[]
  
  
  === Naming samples (and everything else)
  
  
negative.code: If you need to update the information of any of the records submitted, create an new submission and add a document,
  following the same process as before. Using the same team and alias will ensure that the archive records are updated.
  
  == When things go wrong
  
  Successful requests will return a HTTP status code in `20X` range
  (see the <<submission_api.adoc#_http_status_codes,reference docs>>). When something goes wrong, there will be an
  error message to explain the problem. There's an explanation of each error type in the <<submission_api.adoc#_errors,reference docs>>.
  
  Errors can normally be resolved by correcting the content or format of your request. Please get in touch if the cause
  of the problem isn't clear. *TODO* add helpdesk link
  
  == Where to go next?
  
  You can find more in-depth documentation on the API in the <<submission_api.adoc#,reference documentation>>.